Build Local Peering Gateway configurations for same-region VCN-to-VCN peering.
Last verified: May 2026
Build Local Peering Gateway configurations for same-region VCN-to-VCN peering with route rules.
Required Fields
compartmentIdvcnIddisplayNamepeerConfig.peerVcnIdOutput will appear here...Build Local Peering Gateway configurations for same-region VCN-to-VCN peering. 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.
The Local Peering Gateway options surface what is currently documented in the OCI reference for that service. When Oracle adds a new property or value, we add it here after verifying the schema in a real tenancy. If a recently-announced feature is not yet selectable, treat that as a 'not yet supported' signal rather than an opinion that it should not be used.
It produces structurally valid output for the OCI schemas it supports. We still recommend running provider validation locally before applying — schemas evolve and a recently-released property may not yet be reflected. When validation does fail, the error points at the exact attribute the schema rejected.
Your team has a 'shared services' VCN (Active Directory, monitoring, internal artifact repos) that 4 application VCNs need to access. The builder generates: 4 LPG pairs (one in shared-services VCN ↔ each app VCN), route rules pointing the shared-services CIDR to the LPG in each app VCN, security list updates allowing the necessary protocols. Inter-VCN traffic flows directly without traversing internet. Adding a 5th app VCN: just add another LPG pair (same pattern). Architecture scales linearly without needing a more complex DRG-based design until you exceed ~10 VCNs.
The builder constructs OCI Local Peering Gateway configurations: LPG resource per VCN side (compartment, VCN, name), peering relationship between two LPGs in different VCNs (one initiates, the other accepts), route rules in each VCN's route table directing traffic to the peer VCN's CIDR via the LPG, and security list/NSG rules allowing the inter-VCN traffic. Output is generated as oci network local-peering-gateway commands and Terraform oci_core_local_peering_gateway + oci_core_route_table_attachment resources.
Local Peering Gateway (LPG) is for SAME-region VCN-to-VCN connectivity. For cross-region, use Remote Peering Connection (RPC) or DRG. Mixing them up is a common source of 'why can't VCN-A talk to VCN-B' confusion. LPG = same region, RPC = cross region.
Each VCN needs its own LPG resource — they peer in pairs. For mesh connectivity across N VCNs, you'd need N×(N-1)/2 LPG pairs. For 5+ VCNs, use DRG with VCN attachments instead — one central hub, transitively routed.
LPG connectivity is FREE — no data transfer charges within the same region. This makes inter-VCN architectures dramatically cheaper than equivalent AWS VPC peering (which charges per cross-AZ data transfer). Take advantage when designing multi-VCN apps in OCI.
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.