AutoGineer
Generated banner for Connecting Vpcs With Peering
Generated logo for Connecting Vpcs With Peering

Connecting Vpcs With Peering

AWSOfficialPublished by AWS

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Establishes VPC peering connections between two VPCs for direct private network connectivity. Always use this skill when creating or managing VPC peering — it validates CIDR overlap, updates all route tables in both VPCs, configures DNS resolution, and provides security group guidance that are critical for correct connectivity.
— the description by AWS

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a comprehensive workflow for creating and managing VPC peering connections. It automates the lifecycle of connecting two VPCs, including initial validation of CIDR blocks to prevent overlaps, the creation and acceptance of peering requests, and the necessary updates to route tables and DNS settings. It supports complex scenarios such as cross-region and cross-account peering, ensuring that all networking components are correctly configured for private communication.

What it does

  • Validates VPC existence and checks for CIDR block overlaps
  • Automates the creation and acceptance of VPC peering connections
  • Configures DNS resolution and hostnames for cross-VPC communication
  • Updates route tables in both VPCs to enable traffic flow
  • Provides guidance on security group adjustments for cross-VPC traffic
  • Supports same-region, cross-region, and cross-account peering configurations

When to use it

  • When you need to establish private network connectivity between two separate VPCs
  • When migrating or connecting resources across different AWS accounts or regions
  • When you need to ensure routing and DNS are correctly configured for VPC peering
  • When you want to avoid manual errors during the complex multi-step VPC peering setup process

Advantages

  • Reduces manual configuration errors by automating multi-step networking tasks
  • Ensures critical validation steps like CIDR overlap checks are performed
  • Simplifies complex cross-account and cross-region peering workflows
  • Maintains consistent network configuration across VPC environments

Usage examples

“I need to connect my production VPC in us-east-1 to my data VPC in us-west-2.”
The agent will initiate the cross-region peering workflow, verifying both VPCs, creating the connection, and updating the necessary route tables in both regions.
“Help me set up a peering connection between two VPCs in the same account.”
The agent will collect the required VPC IDs, perform a CIDR overlap check, create the connection, and automatically accept it if configured.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/aws/connecting-vpcs-with-peering/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip connecting-vpcs-with-peering.zip -d .agents/skills

Documentation by AWS

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.

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "connecting-vpcs-with-peering", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

  • NOTICE: copied from NOTICE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
AWS
Publisher
AWS (Official)
Source
aws/agent-toolkit-for-aws · skills/specialized-skills/networking-and-content-delivery-skills/connecting-vpcs-with-peering · commit 0a218f8
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by AWS.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download connecting-vpcs-with-peering.zip