This diagram shows an architecture topology with two AWS regions (AWS Region 1 and AWS Region2) and two OCI regions (OCI Region 1 and OCI Region 2).

Each AWS region shows a single Availability Zone (AZ) that contains the application VPC and the Oracle Database@AWS ODB network components for that region.
Each AWS region connects to an OCI Hub VCN in the corresponding OCI region using Local Peering Gateways (LPG). The two OCI regions are linked through Dynamic Routing Gateways (DRG) with remote peering. Far Sync runs in each OCI region's Hub VCN.
Active Data Guard replicates from the primary database in AWS Region 1 to the standby database in AWS Region 2.
Hub VCNs and subnets are shown at the regional level.

AWS Region 1 hosts one AZ which includes:

An Application VPC with an Application subnet hosting the application.
ODB network for Oracle Database@AWS hosts OCI VCN with two subnets: Client subnet, CIDR 10.182.0.0/24 and a Backup subnet. The Primary Database is shared between the two subnets.
ODB peering connects the Application VPC to the ODB network.

AWS Region 2 hosts one AZ which includes:

An Application VPC with an Application subnet hosting the application.
ODB network for Oracle Database@AWS hosts OCI VCN with two subnets: Client subnet, CIDR 10.0.1.0/24 and a Backup subnet. The Standby Database is shared between the two subnets.
ODB peering connects the Application VPC to the ODB network.

OCI Region 1 hosts the following:

OCI Region 2 hosts the following:

Inter‑region connectivity and data flows are shown:

Each Hub VCN attaches to a DRG; the DRGs use remote peering between OCI Region 1 and 2.
Replication is done from the Primary Database in AWS Region 1 AZ to OCI Region 1 Far Sync via LPG to DRG remote peering to OCI Region 2 to Far Sync to Standby in AWS Region 2 AZ using LPG.
Each application in its AWS AZ connects to the local Oracle Database@AWS through ODB peering and connects to the Database.