mcpField
C
connecting-vpcs-with-peering

connecting-vpcs-with-peering

github.com/awsCloud & DevOps3.3k6.2k installsUpdated 1d ago
Repository

About connecting-vpcs-with-peering

A domain skill for cloud operators establishing private connectivity between two VPCs through VPC peering. It covers same-region, cross-region, and cross-account setups, including routes, DNS, and security groups.

Key features

  1. 01Create and accept peering connections
  2. 02Update route tables on both sides
  3. 03Configure DNS resolution
  4. 04Adjust cross-VPC security group rules
  5. 05Check CIDR overlap and connection status

Use cases

  1. 01Connect two VPCs in one region
  2. 02Set up cross-region VPC communication
  3. 03Configure cross-account VPC peering
  4. 04Troubleshoot routing or DNS connectivity

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering

After installing, type/connecting-vpcs-with-peeringin Claude Code to confirm it loaded.

Bundled filesreferences/vpc-peering-connection.md

Details

From the project README

Connecting VPCs with Peering

Overview

Domain expertise for establishing private network connectivity between two VPCs using VPC peering. Covers the full lifecycle: creating the peering connection, accepting it, updating route tables in both VPCs, configuring DNS resolution, and adjusting security groups for cross-VPC traffic. Supports same-region, cross-region, and cross-account peering scenarios.

Create a VPC peering connection

To establish a VPC peering connection between two VPCs, follow the procedure exactly. See VPC peering connection procedure.

The procedure requires the requester and accepter VPC IDs at minimum. It validates both VPCs exist, checks for CIDR overlap, creates and accepts the peering, updates all route tables, and configures DNS resolution.

Troubleshooting

Peering stuck in pending state

Cross-account connections require manual acceptance from the accepter account. Same-account connections with auto_accept: true should transition automatically.

Route creation fails

Check for existing routes with the same destination CIDR. Replace existing routes instead of creating new ones.

DNS resolution not working

Both VPCs must have DNS resolution and DNS hostnames enabled in their VPC settings, not just the peering connection options.

Cross-region connectivity issues

Verify routes are added in both regions and security groups allow traffic from the peer VPC's CIDR blocks.

Comments

Markdown supported