connecting-vpcs-with-peering

Establishes VPC peering connections with route table updates and DNS configuration.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill connecting-vpcs-with-peering-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connecting-vpcs-with-peering
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/connecting-vpcs-with-peering
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill connecting-vpcs-with-peering-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up private network connectivity between two VPCs requires many coordinated steps—creating and accepting the peering connection, updating every route table in both VPCs, enabling DNS resolution, and adjusting security groups—and missing any one of them results in broken connectivity. ## Core Features & Use Cases - End-to-End Peering Setup: Creates and accepts the VPC peering connection, validates CIDR overlap, and waits for the connection to reach active state. - Route and DNS Configuration: Updates all route tables in both VPCs and enables DNS resolution and hostnames across the peering connection. - Multi-Scenario Support: Handles same-region, cross-region, and cross-account peering, including guidance on security group rules for cross-VPC traffic. - Use Case: Connect a production VPC in us-east-1 to an analytics VPC in us-west-2 so instances can communicate over private IPs without traversing the public internet. ## Quick Start Set up a VPC peering connection between vpc-12345678 and vpc-87654321 with DNS resolution enabled and all route tables updated.

Frequently Asked Questions about connecting-vpcs-with-peering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a VPC peering connection between two VPCs?

Provide the requester and accepter VPC IDs, then the procedure creates the peering connection with aws ec2 create-vpc-peering-connection, accepts it, updates all route tables in both VPCs, and configures DNS resolution. It validates that both VPCs exist and checks for CIDR overlap first.

How to set up cross-region VPC peering in AWS?

Specify different requester_region and accepter_region parameters when creating the peering connection. The procedure switches regions as needed to accept the connection, configure DNS options, and add routes in both regions.

Does VPC peering work across different AWS accounts?

Yes, cross-account peering is supported by providing the accepter_account_id parameter. However, auto-accept only works for same-account connections, so cross-account peering requires manual acceptance from the accepter account.

Why is my VPC peering connection stuck in pending-acceptance state?

A pending-acceptance state usually means it is a cross-account connection requiring manual acceptance from the accepter account. Same-account connections with auto_accept enabled should transition to active automatically.

Why is DNS resolution not working over VPC peering?

Both VPCs must have DNS resolution and DNS hostnames enabled in their VPC settings, not just in the peering connection options. Verify these VPC-level attributes are enabled on both the requester and accepter sides.

What are the limitations of VPC peering with overlapping CIDR blocks?

VPCs with overlapping CIDR blocks cannot be peered properly because routing becomes ambiguous. The procedure checks for overlap and warns you; alternatives include VPC sharing or AWS Transit Gateway.