This image shows an Oracle AI Database@AWS topology in an Amazon Web Services (AWS) Region that connects multiple application virtual private clouds (VPCs) in separate AWS accounts to one ODB network through transit networking for low-latency application access. The architecture has the following components:

• AWS Region includes an Application virtual private cloud (VPC), a transit gateway path, a Transit VPC, and an Oracle AI Database@AWS ODB network.
• Application VPC contains App-A Subnet and App-B Subnet, and each subnet hosts an application workload.
• Transit gateway (TGW) receives traffic from the Application VPC and forwards traffic through a TGW attachment.
• TGW attachment is in the same availability zone (AZ) as the ODB network, and the TGW uses one attachment with a single subnet in that AZ.
• Transit VPC contains one subnet that receives routed traffic from the TGW attachment and sends traffic to ODB peering.
• ODB peering connects the Transit VPC and the ODB network and carries bidirectional traffic between those networks.
• ODB network hosts Oracle AI Database@AWS and exchanges application traffic with the Transit VPC through ODB peering.
• Transit VPC is in the same AWS account as the ODB network for this routing design.