Create private connections between your VPCs with VPC Peering, enabling secure, low-latency communication across your cloud infrastructure.
Connect multiple VPCs within the same region and simplify complex infrastructure layouts. VPC Peering enables distributed workloads across projects or environments to communicate as part of a unified private network.
Avoid deploying transit instances or managing complex VPN meshes to connect isolated networks. VPC Peering provides native connectivity between VPCs, simplifying network operations and reducing unnecessary infrastructure.
Route traffic between VPCs entirely through Scaleway’s private network without exposing data to the public internet. This built-in isolation improves security and helps meet strict compliance and sovereignty requirements.
VPC-to-VPC connectivity
Private connectivity between 2 VPCs within the same region, across projects or organizations.
Transitive peering
Transitive routing across up to 4 chained VPCs, enabling hub-and-spoke network architectures.
Custom route control
Define which IP ranges are routed across the peering connection using custom routes (IPv4 and/or IPv6).
Integration with VPC networking
Works seamlessly with Scaleway networking features including VPC Routing, Private Networks, and Network ACLs.
Connect VPCs across Projects within your Organization to enable secure communication between teams or business units.
Extend connectivity to trusted partners in other Organizations through VPC peering.
Distribute application components across Projects while maintaining low-latency private connectivity. Teams remain autonomous and manage their own infrastructure.
Connect spoke VPCs to a central hub VPC providing shared services and connectivity.
Each spoke VPC remains isolated while benefiting from centralized network control and private communication.
Understand the cost of connecting your VPCs and scaling your network architecture.
Private networking for cloud resources
Create secure, isolated cloud environments with VPC and regional Private Networks.
Control traffic and resources for your applications and data.
Secure internet gateway for VPC resources
Securely connect your private network resources to the public internet.
Manage inbound and outbound traffic with built-in NAT.
Flexible compute instances for cloud workloads
Deploy high-performance virtual machines for your applications.
Choose flexible compute options optimized for your workloads.
VPC Peering allows you to connect two Scaleway Virtual Private Clouds (VPCs) within the same region so that resources in each network can communicate privately. Traffic flows through Scaleway’s private infrastructure rather than the public internet.
Without native peering, connecting isolated VPCs often requires deploying VPN gateways or transit virtual machines. VPC Peering provides a simpler, provider-managed connection that reduces infrastructure overhead and improves performance.
Yes. VPC Peering can connect VPCs that belong to the same Project, different projects within the same organization, or even across organizations, as long as they are located in the same region.
No. Traffic exchanged between peered VPCs stays entirely within Scaleway’s private network backbone, ensuring secure communication between workloads.
Transitive peering allows traffic to pass through an intermediate VPC to reach other connected networks. This makes it possible to design hub-and-spoke architectures where a central VPC connects multiple environments such as production, staging, or shared services.
Scaleway VPC Peering supports transitive routing across up to four chained VPCs, enabling flexible multi-network architectures.
Yes. You can define custom routes to control which IP ranges are allowed to traverse the peering connection. This supports both IPv4 and IPv6 traffic and gives you fine-grained control over connectivity.
Yes. VPC Peering integrates with the Scaleway VPC ecosystem, including:
No. VPC Peering currently supports connections within the same region only. For cross-region connectivity or hybrid networking, other solutions such as VPN or dedicated connectivity may be required.
Common use cases include:
