Connecting Vpcs With Peering

This handles the full VPC peering workflow so you don't have to remember all the steps. It validates CIDR overlap before creating the connection, updates route tables in both VPCs automatically, and configures DNS resolution options. The real value is that it covers same-region, cross-region, and cross-account scenarios with a single procedure instead of making you hunt through AWS docs for each case. One catch: cross-account peering still needs manual acceptance from the other side, but it'll handle the auto-accept for same-account setups. Saves you from the common mistake of forgetting to enable DNS hostnames at the VPC level.

skills.sh installs: 6.5K
GitHub stars: 3.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aws/agent-toolkit-for-aws --skill connecting-vpcs-with-peering --agent claude-code

Installs into .claude/skills of the current project.

Files

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.