This image shows a highly available, multi-zone deployment that integrates components across AWS and Oracle Cloud Infrastructure (OCI).

There are two environments depicted: the AWS Primary Availability Zone and a Standby AWS Availability Zone, each within the same AWS Region and an associated OCI Region. Each environment deployed across AWS and OCI has equivalent components and configurations.

In each AWS Availability Zone:

• There is an Application deployed in an Application Virtual Private Cloud (VPC) in AWS. The Application VPC is connected to an ODB network using ODB Peering.
• Within the each ODB network, the Oracle Database@AWS deployment resides in its own Virtual Cloud Network (VCN). Within each VCN are client and backup subnets.
  • In the Primary Availability Zone, the Oracle Database@AWS VCN is named VCN1 (10.10.0.0/16) with a Client Subnet (10.10.1.0/24) and a Backup Subnet (10.10.0.0/24).
  • In the Standby Availability Zone, the Oracle Database@AWS VCN is named VCN2 (10.20.0.0/16) with a Client Subnet (10.20.1.0/24) and a Backup Subnet (10.20.0.0/24).
• Each subnet has its own route table and security list. The primary Oracle Database is deployed across the Client and Backup subnets in each VCN.
• Each AWS Availability Zone's Oracle VCN client subnet is connected to the other using a local peering connection between Local Peering Gateways (LPGs).

In the OCI region:

• Hub VCNs in different availability zones are connected over their LPGs using local peering.
• Oracle Data Guard enables replication between the Primary and Standby Availability Zones, ensuring the Primary Database and Standby Database are synchronized for failover and data protection purposes.