Limitations

• If your VPC has a broad IP range (e.g., greater than /16), direct peering may not be feasible due to a high risk of IP conflicts.
• CIDR range 10.0.0.0/16 and overlapping ranges are not available for peering in our multi-tenant cloud. Dedicated Enterprise instances do not have this restriction.

Before Peering

Each cloud provider has specific requirements for setting up peering:

• AWS:
  • Region of the VPC
  • VPC ID
  • Account ID
• Azure:
  • Region of the VNet (sanity check to confirm intent—cross-region peering may introduce network charges)
  • Resource ID of the Virtual Network
• GCP:
  • Region of the VPC (sanity check to confirm intent—GCP VPCs are global, but peering is regional and may incur network charges)
  • Project ID
  • Network Name of the VPC

Additionally, please provide the CIDR range of your VPC/VNet.

Peering Process

Once we have all required details, we’ll initiate peering and notify you. If any issues arise, we’ll reach out for clarification.

After Peering

We’ll update routing tables to ensure proper connectivity and advise on any necessary configurations on your end. For AWS we’ll provide a CLI command to associate the private hosted zone.

Frequently Asked Questions

Q: What if I already have existing networks? How do we ensure CIDR ranges don’t overlap? A: Before deployment, review your existing VPC CIDR ranges to confirm there are no conflicts with the proposed range (e.g., 10.0.0.0/16). Inform us in advance so we can plan accordingly.

Q: What happens if I select the wrong CIDR range? A: Overlapping CIDR ranges can prevent VPC peering and create routing conflicts, leading to connectivity issues or delays. To avoid this, confirm your existing network allocations, reserve space for future expansion, and consult your networking team. If unsure, reach out to us for assistance.