This image shows an Oracle AI Database@AWS topology in an Amazon Web Services (AWS) Region where one application virtual private cloud (VPC) connects to multiple ODB network across separate Availability Zones (AZs) for low-latency access.

The architecture has the following components:

• AWS Region contains one Application VPC, transit connectivity, and multiple ODB networks that host Oracle AI Database@AWS instances.
• Application VPC hosts application subnets and application workloads that initiate database traffic.
• Application subnets host separated applications that connect to database instances in multiple ODB network.
• Transit gateway (TGW) receives traffic from the Application VPC and forwards traffic through TGW attachment paths.
• TGW attachments connect the Application VPC path to multiple ODB network paths.
• ODB peering links the transit path to each ODB network and carries bidirectional traffic.
• Multiple ODB network host Oracle AI Database@AWS instances in separate AZs.
• Each ODB network receives application traffic from the single Application VPC through the defined peering path.
• This topology supports one VPC to multiple ODB networks to provide low latency between the Application VPC and Oracle AI Database instances.
• Oracle recommends this topology for latency-sensitive applications between ODB network.
• VPC subnet CIDR ranges don't overlap, and each CIDR range is added in the ODB peering connection configuration.