Home > Storage > PowerFlex > White Papers > Dell APEX Block Storage for AWS: Oracle Database Deployment and Performance > Architecture using Amazon EBS volumes
Figure 7 shows the architecture of the two-layer Dell APEX Block Storage for AWS using Amazon Elastic Block Storage (EBS) volumes.
This example uses Dell APEX Block Storage for AWS deployed on the US East (North Virginia) region with three AZs. The PowerFlex SDS instance type of c5n.9xlarge running on each AZ with Red Hat Enterprise Linux 8.4 AMI. The PowerFlex SDS instances are backed by general purpose SSD based EBS (gp3) volumes. EBS volumes are attached to the network and handled by AWS. EBS volumes are persistent storage. The data persists even if the PowerFlex SDS instances are powered off. A single VPC with public and private subnets is created on each AZ. There are six PowerFlex SDS instances that are configured into a single protection domain. There is a single Fault Set assigned per AZ to maintain equal numbers of PowerFlex SDS instances in each Fault Set. A single storage pool is created using all the storage devices in a protection domain.
The PowerFlex SDC service is installed onto Amazon EC2 instance type c5n.9xlarge running on different AZs. The Oracle databases are running on c5n.9xlarge instance types within a private subnet.
The PowerFlex volumes that are created from the storage pool powered by the Amazon EBS volumes are mapped to PowerFlex SDC instances where the SDC service is running. The new PowerFlex volumes in the SDC instances can be used to create a file system or can be managed by Oracle Automatic Storage Management (ASM) as desired by the database administrators.
The following Figure 8 and Figure 9 shows the Dell APEX Block Storage for AWS using the c5n.9xlarge instance type for both SDS and SDC instances.
Figure 10 shows the SDS instance attached with Amazon EBS volumes.