The architecture has the following components:

• AWS Region groups multiple application environments, transit gateway connectivity, a Transit VPC, and an ODB network that hosts Oracle AI Database.
• Separate AWS accounts for applications each contain an Application VPC with application subnets and application workloads.
• Application VPCs and subnets host application instances in labeled subnets, and each Application VPC sends traffic to a local transit gateway (TGW).
• TGW receives traffic from each Application VPC and participates in TGW peering to pass traffic toward the ODB network path.
• TGW peering links the TGWs so multiple Application VPCs can reach the shared ODB network path.
• TGW attachment in the same availability zone (AZ) as the ODB network connects TGW traffic to the Transit VPC.
• Transit VPC contains the subnet used by the TGW attachment and forwards traffic to ODB peering.
• ODB peering connects the Transit VPC and the ODB network and carries bidirectional traffic between those networks.
• ODB network serves application traffic from multiple Application VPCs to Oracle AI Database.
• The topology supports multiple VPCs to one ODB network to provide low latency between applications and Oracle AI Database, and Oracle recommends this topology for latency-sensitive applications.
• VPC and subnet CIDR ranges don't overlap, and each CIDR range is added in the ODB peering connection configuration.