Oracle Database@AWS Network Configuration Guide

Oracle Database@AWS (ODB@AWS) is a service that runs Oracle Database natively on Oracle Exadata infrastructure within AWS data centers, delivering 165μs ultra-low latency performance.

ODB@AWS uses the ODB Network, a private isolated network that hosts OCI infrastructure within an AWS Availability Zone (AZ). Its key characteristics are as follows.

• Private isolation: By default, not connected to AWS VPC, on-premises, or the internet
• Single-AZ operation: Each VM cluster is associated with a single ODB Network within a single AZ
• Multi-VPC peering: A single ODB Network supports up to 45 VPC peerings (updated February 2026)

Network connectivity methods can be chosen based on the environment. Direct Multi-VPC peering has a simple structure and the lowest latency, but makes on-premises connectivity difficult. On the other hand, the Transit Gateway (TGW) hub-and-spoke approach is suitable for enterprise environments that require on-premises connectivity along with centralized routing and security inspection.

When designing CIDR, avoiding IP overlap is critical. CIDR blocks cannot be changed after creation, so sufficient ranges must be planned in advance; the client subnet requires a minimum of /27, while Oracle's recommendation is /24.