connecting-vpcs-with-peering

Create AWS VPC peering connections with route and DNS configuration.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill connecting-vpcs-with-peering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connecting-vpcs-with-peering
Source: https://github.com/mreferre/aws-agent-toolkit-skills/tree/main/.kiro/skills/connecting-vpcs-with-peering
Command: npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill connecting-vpcs-with-peering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of enabling private network connectivity between two AWS VPCs by correctly creating and configuring VPC peering, including routes, DNS resolution, and cross-VPC security group guidance.

Core Features & Use Cases

  • Peering lifecycle management: Creates the VPC peering connection, waits for it to become active, and handles same-account auto-accept vs cross-account manual acceptance.
  • Route table updates across both VPCs: Validates CIDR overlap, then updates all route tables in both VPCs so traffic can flow to the peer CIDRs through the peering connection.
  • DNS resolution and hostname enablement: Configures peering DNS options on both sides to ensure name resolution works as expected across VPC boundaries.
  • Security group recommendations: Provides actionable guidance to permit cross-VPC traffic safely (without overly permissive rules).

Quick Start

Use the connecting-vpcs-with-peering skill to establish peering between requester_vpc_id vpc-12345678 and accepter_vpc_id vpc-87654321 by updating routes, enabling DNS resolution across the peering, and providing security group rules for cross-VPC connectivity.

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 set up VPC peering between two AWS VPCs?

To set up VPC peering, create a peering connection between a requester and accepter VPC, wait for activation, update route tables in both VPCs to direct traffic to peer CIDRs, and enable DNS resolution across the connection.

Can I use VPC peering for cross-account and cross-region AWS connectivity?

Yes, VPC peering supports same-region, cross-region, and cross-account scenarios. For cross-account peering, the accepter side must manually accept the connection request before routing and DNS configuration can be applied.

Why does my VPC peering connection fail due to CIDR overlap?

VPC peering requires non-overlapping CIDR ranges. The peering process validates CIDR overlap before updating route tables, and overlapping ranges will prevent traffic from flowing reliably between the two VPCs.

How do I configure DNS resolution across an AWS VPC peering connection?

Configuring DNS across a VPC peering connection requires enabling peering DNS resolution options on both the requester and accepter sides, ensuring that private hostname resolution works across VPC boundaries.

What security group rules do I need for cross-VPC traffic over a peering connection?

Cross-VPC traffic over a peering connection requires security group rules that permit traffic between the VPC CIDRs. The configuration provides actionable guidance to allow cross-VPC traffic safely without overly permissive rules.

What is the best way to connect VPCs privately without a transit gateway?

VPC peering establishes private network connectivity between two VPCs by creating a direct peering connection, updating all route tables to point to peer CIDRs, and configuring DNS options for reliable traffic flow without overlapping ranges.