--- name: connecting-vpcs-with-peering description: 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. version: 1 metadata: service: [ec2, vpc] task: [configure, deploy] persona: [developer, devops] workload: [networking] --- # 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](references/vpc-peering-connection.md). 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. --- Source attribution: mashharuki Original project: https://github.com/mashharuki/AWS-SummitHackathon-2026/blob/5f2b67fd174e65b5eca533128877f7d97699007d/.github/skills/connecting-vpcs-with-peering/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2026 SABOROU Team Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: mashharuki Original project: https://github.com/mashharuki/AWS-SummitHackathon-2026/blob/5f2b67fd174e65b5eca533128877f7d97699007d/.github/skills/connecting-vpcs-with-peering/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Operations Roles: Backend Developer, DevOps / SRE, IT Operations Specialties: Backend, DevOps Tools: AWS, Ec2, Vpc Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: afb3a904b0ff6ca99b216c0f5cd3f67f1c6a3c72a65465e0d168955936f7fcc9