Learn About Oracle Database@AWS

You can deploy Oracle Database on Oracle Exadata Database Service on Dedicated Infrastructure colocated in AWS data centers and managed by Oracle. Oracle Database@AWS integrates into AWS networking and AWS Virtual Private Cloud (VPC).

Oracle Database@AWS brings Oracle technologies, such as Oracle Exadata Database Service and Oracle Real Application Clusters (Oracle RAC) to AWS customers.

You can provision and manage Oracle Database@AWS using the AWS console. AWS IAM provides identity and access management for Oracle Database@AWS.

In this solution, you learn about the network topologies and considerations for selecting each topology.

Note:

Oracle Database@AWS is currently available in Limited Preview. To request more information, see Learn about Oracle Database@AWS.

Architecture

Oracle Database@AWS extends Oracle Database capabilities into AWS Availability Zones as a native service. The following architecture diagram shows the main topology for Oracle Database@AWS with application resources within a VPC of an AWS region.


db-aws-main-arch-oracle.zip

The Oracle Exadata Database Service resides within the OCI-managed child site inside the ODB network created exclusively for Oracle Database@AWS. A customer application hosted on AWS and deployed within an application Virtual Private Cloud (VPC) communicates with Oracle Database@AWS by using the database connection options available.

Considerations for Oracle Exadata Database Service Networking

When selecting a network topology, consider the following Oracle Exadata Database Service VM cluster networking:

  • Select or create a new ODB network for your Oracle Exadata Database Service on Dedicated Infrastructure VM cluster.
  • Locate Application VPCs in the same Availability Zone as the ODB network and Exadata infrastructure hosting the VM cluster.
  • Peer only a single Application VPC to a single ODB network.
  • Carve out two non-overlapping CIDR ranges for the Oracle Exadata Database Service on Dedicated Infrastructure VM cluster:

    • Define one CIDR range for the Client subnet with a minimum /27. Oracle recommends that you use /24 for the Client subnet CIDR to accommodate future expansion.

    • Define one CIDR for the Backup subnet with a minimum of /28.

  • IPs are automatically assigned to VM clusters from the CIDR range in the Client subnet.