Build Remote Peering Connection configurations for cross-region VCN connectivity through DRG.
Last verified: May 2026
Build Remote Peering Connection configurations for cross-region VCN connectivity through DRG.
Required Fields
compartmentIddrgIddisplayNamepeerConfig.peerRegionNameOutput will appear here...Build Remote Peering Connection configurations for cross-region VCN connectivity through DRG. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
Your team is building a multi-region production architecture across us-ashburn-1 and uk-london-1 for global users. The builder generates: a DRG in each region, RPC pairing the two DRGs, VCN attachments to each DRG, route distributions sharing routes bidirectionally. Cross-region traffic between application VCNs in different regions flows over Oracle's private backbone (low-latency, no internet path). Cost: only the bandwidth shape on each DRG attachment. No per-GB charges for cross-region traffic between OCI regions — significant cost advantage vs equivalent multi-region AWS VPC peering.
Remote Peering Connection (RPC) requires a DRG in EACH region — you don't peer VCNs directly across regions, you peer their DRGs. Plan your DRG topology before setting up RPCs; afterward, each region's DRG can transitively route to the other region's VCNs.
Cross-region traffic via RPC is dramatically cheaper than VPN tunnels — no encryption overhead, no negotiation costs, just direct routing on Oracle's backbone. For multi-region active-active architectures, RPCs are the right answer.
Two regions, multiple VCNs: connect via RPC between DRGs, then attach individual VCNs to their local DRG. Adding a new VCN means adding a DRG attachment in its region — automatically reachable from the other region via the existing RPC.
The builder constructs OCI Remote Peering Connection configurations: DRG resources in each region (must exist before RPC), RPC attachments on each DRG (paired with the remote DRG OCID), RPC connection (the linking resource). DRG route tables in each region distribute routes through the RPC. Output is generated as oci network drg + oci network remote-peering-connection commands and Terraform oci_core_drg_attachment + oci_core_remote_peering_connection resources.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.