[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADP5W6T0AHTPHDJ27P0D30":3,"skill-same:01M7ADP5W6T0AHTPHDJ27P0D30":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7ADP5W6T0AHTPHDJ27P0D30","vpc-peering-deployer",null,"Provisions Amazon VPC peering connections with production defaults: requester\u002Faccepter model (create-vpc-peering-connection, accept-vpc-peering-connection), same-account vs cross-account peering, same-region vs inter-region peering, DNS resolution (allowDnsResolutionFromPeeredVpc), route table updates on BOTH sides (required for traffic to flow), security group cross-VPC references (same account+region only), limitations (no transitive routing, no edge-to-edge routing), and IPv6 support. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a VPC peering connection, connecting two VPCs, setting up cross-account VPC peering, enabling inter-region VPC peering, or configuring DNS resolution across peered VPCs. Triggers: create vpc peering connection, cross-account vpc peering, inter-region vpc peering, vpc peering route table, vpc peering DNS resolution, vpc peering security group reference, accept vpc peering, vpc peering IPv6.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vpc-peering-deployer\ndescription: 'Provisions Amazon VPC peering connections with production defaults: requester\u002Faccepter model (create-vpc-peering-connection, accept-vpc-peering-connection), same-account vs cross-account peering, same-region vs inter-region peering, DNS resolution (allowDnsResolutionFromPeeredVpc), route table updates on BOTH sides (required for traffic to flow), security group cross-VPC references (same account+region only), limitations (no transitive routing, no edge-to-edge routing), and IPv6 support. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a VPC peering connection, connecting two VPCs, setting up cross-account VPC peering, enabling inter-region VPC peering, or configuring DNS resolution across peered VPCs. Triggers: create vpc peering connection, cross-account vpc peering, inter-region vpc peering, vpc peering route table, vpc peering DNS resolution, vpc peering security group reference, accept vpc peering, vpc peering IPv6.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ec2 access (and cross-account STS assume-role if cross-account peering). Works with Terraform aws_vpc_peering_connection \u002F aws_vpc_peering_connection_accepter \u002F aws_route resources and CloudFormation AWS::EC2::VPCPeeringConnection templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Networking\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, vpc, vpc-peering, cloudops, deploy, networking, provisioning, cross-account, inter-region, route-table, dns-resolution, security-group, ipv6\n  dependencies: aws-orchestrator\n  keywords: aws, vpc, vpc peering, peering connection, cloudops, deploy, provisioning, cross-account, inter-region, requester, accepter, route table, dns resolution, security group reference, ipv6, transitive routing, edge-to-edge\n  when_to_use: Invoke when the user wants to create a VPC peering connection between two VPCs (same-account or cross-account, same-region or inter-region), configure DNS resolution across peered VPCs, update route tables on both sides for traffic flow, reference security groups across peered VPCs, or understand VPC peering limitations (no transitive routing). Do NOT invoke for AWS Transit Gateway (use transit-gateway skills), VPC endpoints (PrivateLink), or VPN\u002FDirect Connect connectivity.\n---\n\n# VPC Peering Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon VPC peering\nconnections with correct defaults. The skill walks the operator through\nthe requester\u002Faccepter model, same-account vs cross-account decisions,\nsame-region vs inter-region constraints, route table updates, DNS\nresolution, security group cross-references, and peering limitations,\ncaptures topology and routing decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate VPC peering connection, cross-account VPC peering, inter-region\nVPC peering, VPC peering route table, VPC peering DNS resolution, VPC\npeering security group reference, accept VPC peering, VPC peering IPv6.\n\n## STRICT output contract\n\nWhen this skill is invoked with a VPC-peering-provisioning request\n(create a peering connection, connect two VPCs, cross-account or inter-\nregion peering, DNS resolution, route tables, security group cross-\nreferences, or a partial configuration), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section using\nthe literal all-caps labels `VPC_PEERING:`, `VERDICT:`, `CHECKLIST:`,\nand `VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels breaks\nautomation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Requester\u002Faccepter model | Core peering model |\n| Step 2 — Same-account vs cross-account | Account topology |\n| Step 3 — Same-region vs inter-region | Region topology |\n| Step 4 — Create and accept the peering connection | Provisioning step |\n| Step 5 — Route table updates (BOTH sides required) | Traffic flow |\n| Step 6 — DNS resolution (allowDnsResolutionFromPeeredVpc) | DNS across VPCs |\n| Step 7 — Security group cross-VPC references | SG cross-referencing |\n| Step 8 — Limitations (no transitive routing) | Topology constraints |\n| Step 9 — IPv6 support | IPv6 peering |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Frouting-and-dns.md | Route table + DNS detail |\n| references\u002Fcross-account-and-security.md | Cross-account + SG detail |\n| references\u002Fworked-examples.md | Create\u002Faccept CLI walkthroughs |\n| references\u002Ferror-handling.md | Failure triage |\n| references\u002Fadvanced-patterns.md | Recent features |\n\n## Mindset\n\n**One-line takeaway:** A VPC peering connection is a one-to-one network\nlink between two VPCs. The requester creates it; the accepter accepts\nit. Traffic flows ONLY if route tables on BOTH sides are updated to\ninclude the peered VPC's CIDR. Peering is NOT transitive — A peered to\nB and B peered to C does NOT let A talk to C.\n\nThree misconceptions dominate VPC peering misdesign at provisioning\ntime:\n\n- **\"Creating the peering connection is enough.\"** It is not. Creating\n  and accepting the peering connection establishes the link, but NO\n  traffic flows until route tables on BOTH the requester and accepter\n  sides are updated to route traffic to the peered VPC's CIDR via the\n  peering connection. This is the #1 cause of \"my peering doesn't work\"\n  tickets.\n\n- **\"VPC peering supports transitive routing.\"** It does NOT. If VPC-A\n  is peered to VPC-B, and VPC-B is peered to VPC-C, VPC-A CANNOT reach\n  VPC-C through VPC-B. Each pair needs its own direct peering\n  connection. For hub-and-spoke or transitive topologies, use AWS\n  Transit Gateway.\n\n- **\"Security groups can reference peered VPC security groups across\n  accounts.\"** Only partially true. Security group cross-VPC references\n  (referencing a SG by its ID from a peered VPC) work ONLY when the\n  peering is within the same account AND same region. Cross-account or\n  inter-region peering cannot use SG cross-references — use CIDR-based\n  rules instead.\n\n## Configuration dependency graph (novel heuristic)\n\nVPC peering configurations are NOT independent. The peering connection\nmust be accepted before route tables can reference it. DNS resolution\nmust be explicitly enabled. Security group cross-references have\naccount\u002Fregion constraints. Use this graph to sequence provisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Peering connection (requester) | requester VPC exists; accepter VPC ID known | connection is pending until accepted; accepter must be in the same region (same-region) or a different region (inter-region) | the peering link |\n| Peering acceptance | requester created the connection; accepter account has permission | acceptance CANNOT be automated across accounts without IAM role assumption (accepter must call accept-vpc-peering-connection) | active peering connection |\n| Route table (requester side) | peering connection ACTIVE; requester route table exists | route to peered CIDR via pcx-xxx MUST be added manually; without it NO traffic flows | requester → accepter traffic |\n| Route table (accepter side) | peering connection ACTIVE; accepter route table exists | route to requester CIDR via pcx-xxx MUST be added manually; the accepter side is the #1 forgotten step | accepter → requester traffic |\n| DNS resolution | peering connection ACTIVE | `AllowDnsResolutionFromPeeredVpc` must be set to true on BOTH VPCs (requester and accepter) for bidirectional DNS | DNS hostname resolution across VPCs |\n| Security group cross-reference | peering connection ACTIVE; SAME account + SAME region only | cross-account or inter-region peering CANNOT use SG cross-references | SG rules referencing peered VPC's SG by ID |\n| IPv6 routing | VPCs have IPv6 CIDR blocks assigned | IPv6 routes must be added separately (in addition to IPv4 routes) | IPv6 traffic across peering |\n\n**The route-table-both-sides row is the one a baseline model misses.**\nCreating and accepting the peering is necessary but NOT sufficient.\nBoth sides need explicit route table entries. The DNS resolution flag is\nanother commonly forgotten configuration. The procedure below forces an\nexplicit decision on each.\n\n**Cross-dependency gotchas:**\n- Route tables on BOTH sides must be updated. Adding a route on the\n  requester side only enables one-directional traffic (requester →\n  accepter). The return path (accepter → requester) needs its own route\n  entry.\n- DNS resolution requires the flag enabled on both VPCs. Enabling it on\n  one side only does NOT work for bidirectional resolution.\n- Security group cross-VPC references work ONLY within the same account\n  and same region. For cross-account or inter-region peering, use CIDR-\n  based security group rules.\n- IPv4 and IPv6 routing are independent. If both are needed, add routes\n  for both CIDR families.\n\n## Expert heuristic: the two-sided route table requirement\n\nA baseline model says \"create and accept the peering.\" The correct\nheuristic recognizes that the peering connection is a bidirectional\nlink, but route tables are per-VPC and per-direction.\n\n```text\nVPC-A (10.0.0.0\u002F16)  ←── peering (pcx-xxx) ──→  VPC-B (10.1.0.0\u002F16)\n\nFor VPC-A → VPC-B traffic:\n  VPC-A route table needs: Destination 10.1.0.0\u002F16 → Target pcx-xxx\n\nFor VPC-B → VPC-A traffic:\n  VPC-B route table needs: Destination 10.0.0.0\u002F16 → Target pcx-xxx\n\nMissing either route = traffic flows in ONE direction only (or not at all).\nBoth routes are needed for bidirectional communication.\n```\n\n**Key implication:** the #1 cause of \"my peering doesn't work\" is a\nmissing route table entry on the accepter side. Always verify BOTH\nsides have routes pointing to the peering connection.\n\n## Expert heuristic: when to use peering vs Transit Gateway\n\nVPC peering is one-to-one. Transit Gateway is hub-and-spoke (many-to-\nmany). The decision depends on topology.\n\n```text\nNumber of VPCs to connect:\n  ├── 2 VPCs → VPC peering (simplest, no additional cost beyond data transfer)\n  ├── 3-4 VPCs, full mesh → VPC peering (n*(n-1)\u002F2 connections; manageable)\n  │     3 VPCs = 3 peering connections\n  │     4 VPCs = 6 peering connections\n  ├── 5+ VPCs, or hub-and-spoke → Transit Gateway (avoids peering explosion)\n  │     5 VPCs full mesh = 10 peering connections; TGW = 1 attachment per VPC\n  ├── Need transitive routing (A→B→C) → Transit Gateway (peering is NOT transitive)\n  ├── Need VPN\u002FDirect Connect integration → Transit Gateway\n  └── Cost-sensitive, 2 VPCs → VPC peering (no hourly TGW charge)\n```\n\n**Key implication:** peering is free (no per-hour charge; you pay only\nfor data transfer). Transit Gateway charges per-hour per-attachment plus\ndata processing. For 2 VPCs, peering is almost always the right choice.\nFor 5+ VPCs or transitive routing, Transit Gateway is better.\n\n## Expert heuristic: cross-account acceptance automation\n\nIn cross-account peering, the accepter account must call\n`accept-vpc-peering-connection`. This requires either manual action in\nthe accepter account's console\u002FCLI, or automated role assumption.\n\n```text\nCross-account peering flow:\n  1. Requester account creates the peering connection (create-vpc-peering-connection)\n     → Connection status: pending-acceptance\n  2. Accepter account accepts (accept-vpc-peering-connection)\n     → Requires IAM permission in the accepter account\n     → Options:\n       ├── Manual: operator logs into accepter account, runs accept\n       ├── Automated: requester assumes a role in accepter account via STS\n       │   aws sts assume-role --role-arn arn:aws:iam::\u003Caccepter>:role\u002F...\n       │   → then call accept-vpc-peering-connection with accepter credentials\n       └── Lambda\u002FEventBridge: accepter account auto-accepts via EventBridge rule\n  3. Connection status: active\n  4. Both sides update route tables\n```\n\n**Key implication:** cross-account peering adds an acceptance step that\nsame-account peering does not. Plan for the IAM role or manual step.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Requester VPC exists | Peering requires an existing VPC | `aws ec2 describe-vpcs --vpc-ids \u003Cvpc-id>` |\n| Accepter VPC ID known | Must specify the peer VPC at creation | Confirm VPC ID in the accepter account |\n| CIDR blocks do NOT overlap | Overlapping CIDRs break routing; peering may create but traffic fails | Compare VPC CIDRs |\n| AWS account IDs (if cross-account) | Cross-account peering needs both account IDs | `aws sts get-caller-identity` |\n| Regions identified (if inter-region) | Inter-region peering specifies peer region | Confirm both regions |\n| IAM permission in accepter account | Accepter must accept the connection | Verify `ec2:AcceptVpcPeeringConnection` |\n| Route table IDs identified | Routes must be added to specific route tables | `aws ec2 describe-route-tables` |\n| DNS resolution decision | Must be explicitly enabled on both sides | Assess DNS requirements |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Requester\u002Faccepter model\n\nVPC peering uses a requester\u002Faccepter model. The requester creates the\npeering connection; the accepter accepts it.\n\n| Role | Action | API call |\n|---|---|---|\n| Requester | Creates the peering connection | `create-vpc-peering-connection` |\n| Accepter | Accepts the peering connection | `accept-vpc-peering-connection` |\n| Both | Update route tables | `create-route` (each side) |\n\n**Same-account peering:** the requester can auto-accept if it has\npermission. The accepter role is the same account.\n\n**Cross-account peering:** the accepter is a DIFFERENT account. The\naccepter must explicitly accept (manually or via role assumption).\n\n## Step 2 — Same-account vs cross-account\n\n| Feature | Same-account | Cross-account |\n|---|---|---|\n| Acceptance | Can be auto-accepted (if IAM permits) | Must be explicitly accepted by accepter account |\n| Security group cross-references | Supported (same account) | NOT supported (use CIDR rules) |\n| IAM complexity | Single account | Need role assumption or manual acceptance |\n| Peering limit | 125 active peering connections per VPC (soft limit) | Same |\n\n**Cross-account requires:** the accepter account's VPC ID AND account\nID at creation time. The requester specifies `--peer-owner-id`.\n\n## Step 3 — Same-region vs inter-region\n\n| Feature | Same-region | Inter-region |\n|---|---|---|\n| Latency | Minimal (within-region) | Slightly higher (cross-region backbone) |\n| Data transfer cost | Standard intra-region | Cross-region data transfer charges apply |\n| Security group cross-references | Supported (same region) | NOT supported (use CIDR rules) |\n| DNS resolution | Supported | Supported (with flag on both sides) |\n| `--peer-region` | Not needed (same region) | REQUIRED (must specify peer region) |\n| Max inter-region peerings | N\u002FA | 125 per VPC (soft limit) |\n\n**Inter-region data transfer cost** is the primary trade-off. Inter-\nregion traffic incurs cross-region data transfer charges (~$0.01-$0.02\nper GB depending on regions). Same-region peering has standard intra-\nregion data transfer rates.\n\n## Step 4 — Create and accept the peering connection\n\nStep 4 — create\u002Faccept CLI walkthroughs (same-account, cross-account, inter-region) — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Common mistake:** trying to update route tables before the connection\nis ACTIVE. Route creation fails if the peering is still\n`pending-acceptance`.\n\n## Step 5 — Route table updates (BOTH sides required)\n\nRoute tables on BOTH the requester and accepter sides must be updated\nto route traffic to the peered VPC's CIDR via the peering connection.\nThis is the most commonly forgotten step.\n\nStep 5 — route table update commands (both sides required) — moved verbatim.\nFull detail: [Routing and DNS](references\u002Frouting-and-dns.md).\n\n**Critical:** BOTH routes are needed for bidirectional traffic. Missing\nthe accepter-side route is the #1 cause of \"peering doesn't work.\"\n\nFor multiple route tables per VPC (e.g., public and private subnets),\nupdate EACH route table that needs to route to the peered VPC.\n\n## Step 6 — DNS resolution (allowDnsResolutionFromPeeredVpc)\n\nBy default, DNS hostnames from one VPC are NOT resolvable from the\npeered VPC. To enable cross-VPC DNS resolution, set\n`AllowDnsResolutionFromPeeredVpc` to true on the peering connection.\n\nStep 6 — DNS resolution enablement commands (both sides) — moved verbatim.\nFull detail: [Routing and DNS](references\u002Frouting-and-dns.md).\n\n**Critical:** BOTH sides must enable the flag for bidirectional DNS\nresolution. Enabling it on one side only does NOT work.\n\n**Prerequisites for DNS resolution:**\n- Both VPCs must have `enableDnsHostnames` and `enableDnsSupport` set\n  to true.\n- The peering connection must be ACTIVE.\n\n## Step 7 — Security group cross-VPC references\n\nSecurity group cross-VPC references allow a SG rule to reference a\nsecurity group in the peered VPC by its ID (e.g., `sg-xxx` from the\npeer VPC). This is more precise than CIDR-based rules.\n\n**Constraint: only works within the SAME account AND SAME region.**\nCross-account or inter-region peering CANNOT use SG cross-references.\nUse CIDR-based rules instead.\n\nStep 7 — SG cross-reference vs CIDR-based rule commands — moved verbatim.\nFull detail: [Cross-account and security](references\u002Fcross-account-and-security.md).\n\n## Step 8 — Limitations (no transitive routing)\n\nVPC peering has hard limitations. A baseline model may not surface\nthese; they are critical for topology design.\n\n| Limitation | Description | Workaround |\n|---|---|---|\n| No transitive routing | A→B and B→C does NOT allow A→C | Create direct A→C peering, or use Transit Gateway |\n| No edge-to-edge routing | Traffic cannot traverse a peering to reach a VPN\u002FDirect Connect\u002FIGW on the peer side | Use Transit Gateway for VPN\u002FDX integration |\n| Overlapping CIDRs | Peering with overlapping CIDRs breaks routing (may create but traffic fails) | Re-design CIDR allocation; use non-overlapping ranges |\n| Max peering connections | 125 active peerings per VPC (soft limit) | Request limit increase, or use Transit Gateway |\n| SG cross-references | Same account + same region only | Use CIDR-based rules for cross-account\u002Finter-region |\n\n**The no-transitive-routing limitation is the most impactful.** Many\noperators assume that peering VPC-A to VPC-B and VPC-B to VPC-C allows\nVPC-A to reach VPC-C. It does NOT. Each pair needs a direct peering\nconnection. For transitive topologies, use AWS Transit Gateway.\n\n## Step 9 — IPv6 support\n\nVPC peering supports IPv6 traffic if both VPCs have IPv6 CIDR blocks\nassigned. IPv6 routes must be added separately (in addition to IPv4\nroutes).\n\nStep 9 — IPv6 route commands (both sides) — moved verbatim.\nFull detail: [Routing and DNS](references\u002Frouting-and-dns.md).\n\nIPv4 and IPv6 routing are independent. Both must be configured if both\nprotocols are needed.\n\n## Step 10 — Recent features\n\nStep 10 — recent AWS features (2023-2026) — moved verbatim.\nFull detail: [Advanced Patterns](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER assume creating and accepting the peering is enough.** Route\n   tables on BOTH sides must be updated. Without routes, NO traffic\n   flows. The accepter-side route is the #1 forgotten step.\n\n2. **NEVER assume VPC peering supports transitive routing.** A→B and\n   B→C does NOT allow A→C. Each pair needs a direct peering connection.\n   For transitive topologies, use Transit Gateway.\n\n3. **NEVER peer VPCs with overlapping CIDR blocks.** The peering may\n   create, but routing fails because the destination CIDR is ambiguous.\n   Always verify non-overlapping CIDRs before creating the peering.\n\n4. **NEVER use security group cross-VPC references for cross-account or\n   inter-region peering.** SG cross-references work ONLY within the same\n   account AND same region. For cross-account or inter-region, use\n   CIDR-based SG rules.\n\n5. **NEVER enable DNS resolution on only one side.**\n   `AllowDnsResolutionFromPeeredVpc` must be true on BOTH the requester\n   AND accepter for bidirectional DNS resolution. One-sided enablement\n   does not work.\n\n6. **NEVER forget IPv6 routes if using IPv6.** IPv4 and IPv6 routing\n   are independent. Add IPv6 routes separately (using\n   `--destination-ipv6-cidr-block`) if IPv6 traffic is needed.\n\n7. **NEVER assume route table updates propagate automatically.** Each\n   route table in each VPC must be explicitly updated. If a VPC has\n   multiple route tables (e.g., public\u002Fprivate subnets), update EACH\n   one that needs to route to the peered VPC.\n\n8. **NEVER use VPC peering for edge-to-edge routing.** Traffic cannot\n   traverse a peering to reach a VPN, Direct Connect, or Internet\n   Gateway on the peer side. Use Transit Gateway for these patterns.\n\n9. **NEVER create peering connections without a CIDR overlap check.**\n   Always compare VPC CIDR blocks before creating the peering.\n   Overlapping CIDRs are a silent failure (peering creates, traffic\n   fails).\n\n10. **NEVER assume cross-account acceptance is automatic.** The\n    accepter account must explicitly accept the peering connection\n    (manually or via IAM role assumption). Plan for the acceptance\n    step.\n\n## Output format\n\n```text\nVPC_PEERING: \u003Crequester-vpc-id> ↔ \u003Caccepter-vpc-id> (\u003Cpcx-id>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Requester VPC: \u003Cvpc-id> (\u003Ccidr>)\n  [✓|✗] Accepter VPC: \u003Cvpc-id> (\u003Ccidr>)\n  [✓|✗] CIDR overlap check: PASS (non-overlapping) | FAIL (overlapping)\n  [✓|✗] Account topology: Same-account | Cross-account (requester \u003Cacct>, accepter \u003Cacct>)\n  [✓|✗] Region topology: Same-region (\u003Cregion>) | Inter-region (requester \u003Cregion>, accepter \u003Cregion>)\n  [✓|✗] Peering connection: \u003Cpcx-id> — ACTIVE\n  [✓|✗] Route table (requester): \u003Crtb-id> → \u003Cpeer-cidr> via \u003Cpcx-id>\n  [✓|✗] Route table (accepter): \u003Crtb-id> → \u003Cpeer-cidr> via \u003Cpcx-id>\n  [✓|✗] DNS resolution: AllowDnsResolutionFromPeeredVpc=true (both sides) | Disabled\n  [✓|✗] Security group: cross-VPC reference (same acct+region) | CIDR-based (cross-account\u002Finter-region)\n  [✓|✗] IPv6 routing: enabled (IPv6 routes added both sides) | IPv4 only\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ec2 describe-vpc-peering-connections --vpc-peering-connection-ids \u003Cpcx-id> --region \u003Cregion>\n  aws ec2 describe-route-tables --route-table-ids \u003Crequester-rtb> --region \u003Cregion>\n  aws ec2 describe-route-tables --route-table-ids \u003Caccepter-rtb> --region \u003Cregion>\n```\n\n### Worked example — same-account, same-region peering with DNS resolution\n\n```text\nVPC_PEERING: vpc-aaa11122 ↔ vpc-bbb22233 (pcx-111222333)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Requester VPC: vpc-aaa11122 (10.0.0.0\u002F16)\n  [✓] Accepter VPC: vpc-bbb22233 (10.1.0.0\u002F16)\n  [✓] CIDR overlap check: PASS (10.0.0.0\u002F16 and 10.1.0.0\u002F16 do not overlap)\n  [✓] Account topology: Same-account (123456789012)\n  [✓] Region topology: Same-region (us-east-1)\n  [✓] Peering connection: pcx-111222333 — ACTIVE\n  [✓] Route table (requester): rtb-app111 → 10.1.0.0\u002F16 via pcx-111222333\n  [✓] Route table (accepter): rtb-data222 → 10.0.0.0\u002F16 via pcx-111222333\n  [✓] DNS resolution: AllowDnsResolutionFromPeeredVpc=true (both sides)\n  [✓] Security group: cross-VPC reference (sg-app → sg-data via peering)\n  [✓] IPv6 routing: IPv4 only\n  [✓] Tags: Environment=production, Topology=app-to-data\nVERIFICATION_COMMANDS:\n  aws ec2 describe-vpc-peering-connections --vpc-peering-connection-ids pcx-111222333 --region us-east-1\n  aws ec2 describe-route-tables --route-table-ids rtb-app111 --region us-east-1\n  aws ec2 describe-route-tables --route-table-ids rtb-data222 --region us-east-1\n```\n\n## Error handling\n\nError handling deep dives — moved verbatim.\nFull detail: [Error handling](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [Routing and DNS](references\u002Frouting-and-dns.md) — route table update commands (both sides), DNS resolution commands, IPv6 routes\n- [Cross-account and security](references\u002Fcross-account-and-security.md) — acceptance automation, SG cross-reference vs CIDR-based rule commands\n- [Worked examples](references\u002Fworked-examples.md) — create\u002Faccept CLI walkthroughs (same-account, cross-account, inter-region)\n- [Error handling](references\u002Ferror-handling.md) — pending-acceptance, no-traffic, DNS, SG-reference, CIDR-overlap fixes\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — recent features 2023-2026\n\n## Domain\n\nAWS CloudOps \u002F Amazon VPC Peering Connection Provisioning & Network\nConnectivity.\n\n## AWS documentation\n\n- **VPC Peering Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fwhat-is-vpc-peering.html\n- **Create peering connection** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fcreate-vpc-peering-connection.html\n- **Accept peering connection** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Faccept-vpc-peering-connection.html\n- **Route tables for peering** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fvpc-peering-routing.html\n- **DNS resolution** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fmodify-peering-connection-options.html\n- **Security group references** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fsecurity-group-references.html\n- **Inter-region peering** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Finter-region-peering.html\n- **VPC peering limits** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fvpc-peering-limitations.html\n- **IPv6 in VPCs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fvpc-ip-addressing.html#vpc-ipv6\n","# VPC Peering Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon VPC peering\nconnections with correct defaults. The skill walks the operator through\nthe requester\u002Faccepter model, same-account vs cross-account decisions,\nsame-region vs inter-region constraints, route table updates, DNS\nresolution, security group cross-references, and peering limitations,\ncaptures topology and routing decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate VPC peering connection, cross-account VPC peering, inter-region\nVPC peering, VPC peering route table, VPC peering DNS resolution, VPC\npeering security group reference, accept VPC peering, VPC peering IPv6.\n\n## STRICT output contract\n\nWhen this skill is invoked with a VPC-peering-provisioning request\n(create a peering connection, connect two VPCs, cross-account or inter-\nregion peering, DNS resolution, route tables, security group cross-\nreferences, or a partial configuration), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section using\nthe literal all-caps labels `VPC_PEERING:`, `VERDICT:`, `CHECKLIST:`,\nand `VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels breaks\nautomation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Requester\u002Faccepter model | Core peering model |\n| Step 2 — Same-account vs cross-account | Account topology |\n| Step 3 — Same-region vs inter-region | Region topology |\n| Step 4 — Create and accept the peering connection | Provisioning step |\n| Step 5 — Route table updates (BOTH sides required) | Traffic flow |\n| Step 6 — DNS resolution (allowDnsResolutionFromPeeredVpc) | DNS across VPCs |\n| Step 7 — Security group cross-VPC references | SG cross-referencing |\n| Step 8 — Limitations (no transitive routing) | Topology constraints |\n| Step 9 — IPv6 support | IPv6 peering |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Frouting-and-dns.md | Route table + DNS detail |\n| references\u002Fcross-account-and-security.md | Cross-account + SG detail |\n| references\u002Fworked-examples.md | Create\u002Faccept CLI walkthroughs |\n| references\u002Ferror-handling.md | Failure triage |\n| references\u002Fadvanced-patterns.md | Recent features |\n\n## Mindset\n\n**One-line takeaway:** A VPC peering connection is a one-to-one network\nlink between two VPCs. The requester creates it; the accepter accepts\nit. Traffic flows ONLY if route tables on BOTH sides are updated to\ninclude the peered VPC's CIDR. Peering is NOT transitive — A peered to\nB and B peered to C does NOT let A talk to C.\n\nThree misconceptions dominate VPC peering misdesign at provisioning\ntime:\n\n- **\"Creating the peering connection is enough.\"** It is not. Creating\n  and accepting the peering connection establishes the link, but NO\n  traffic flows until route tables on BOTH the requester and accepter\n  sides are updated to route traffic to the peered VPC's CIDR via the\n  peering connection. This is the #1 cause of \"my peering doesn't work\"\n  tickets.\n\n- **\"VPC peering supports transitive routing.\"** It does NOT. If VPC-A\n  is peered to VPC-B, and VPC-B is peered to VPC-C, VPC-A CANNOT reach\n  VPC-C through VPC-B. Each pair needs its own direct peering\n  connection. For hub-and-spoke or transitive topologies, use AWS\n  Transit Gateway.\n\n- **\"Security groups can reference peered VPC security groups across\n  accounts.\"** Only partially true. Security group cross-VPC references\n  (referencing a SG by its ID from a peered VPC) work ONLY when the\n  peering is within the same account AND same region. Cross-account or\n  inter-region peering cannot use SG cross-references — use CIDR-based\n  rules instead.\n\n## Configuration dependency graph (novel heuristic)\n\nVPC peering configurations are NOT independent. The peering connection\nmust be accepted before route tables can reference it. DNS resolution\nmust be explicitly enabled. Security group cross-references have\naccount\u002Fregion constraints. Use this graph to sequence provisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Peering connection (requester) | requester VPC exists; accepter VPC ID known | connection is pending until accepted; accepter must be in the same region (same-region) or a different region (inter-region) | the peering link |\n| Peering acceptance | requester created the connection; accepter account has permission | acceptance CANNOT be automated across accounts without IAM role assumption (accepter must call accept-vpc-peering-connection) | active peering connection |\n| Route table (requester side) | peering connection ACTIVE; requester route table exists | route to peered CIDR via pcx-xxx MUST be added manually; without it NO traffic flows | requester → accepter traffic |\n| Route table (accepter side) | peering connection ACTIVE; accepter route table exists | route to requester CIDR via pcx-xxx MUST be added manually; the accepter side is the #1 forgotten step | accepter → requester traffic |\n| DNS resolution | peering connection ACTIVE | `AllowDnsResolutionFromPeeredVpc` must be set to true on BOTH VPCs (requester and accepter) for bidirectional DNS | DNS hostname resolution across VPCs |\n| Security group cross-reference | peering connection ACTIVE; SAME account + SAME region only | cross-account or inter-region peering CANNOT use SG cross-references | SG rules referencing peered VPC's SG by ID |\n| IPv6 routing | VPCs have IPv6 CIDR blocks assigned | IPv6 routes must be added separately (in addition to IPv4 routes) | IPv6 traffic across peering |\n\n**The route-table-both-sides row is the one a baseline model misses.**\nCreating and accepting the peering is necessary but NOT sufficient.\nBoth sides need explicit route table entries. The DNS resolution flag is\nanother commonly forgotten configuration. The procedure below forces an\nexplicit decision on each.\n\n**Cross-dependency gotchas:**\n- Route tables on BOTH sides must be updated. Adding a route on the\n  requester side only enables one-directional traffic (requester →\n  accepter). The return path (accepter → requester) needs its own route\n  entry.\n- DNS resolution requires the flag enabled on both VPCs. Enabling it on\n  one side only does NOT work for bidirectional resolution.\n- Security group cross-VPC references work ONLY within the same account\n  and same region. For cross-account or inter-region peering, use CIDR-\n  based security group rules.\n- IPv4 and IPv6 routing are independent. If both are needed, add routes\n  for both CIDR families.\n\n## Expert heuristic: the two-sided route table requirement\n\nA baseline model says \"create and accept the peering.\" The correct\nheuristic recognizes that the peering connection is a bidirectional\nlink, but route tables are per-VPC and per-direction.\n\n```text\nVPC-A (10.0.0.0\u002F16)  ←── peering (pcx-xxx) ──→  VPC-B (10.1.0.0\u002F16)\n\nFor VPC-A → VPC-B traffic:\n  VPC-A route table needs: Destination 10.1.0.0\u002F16 → Target pcx-xxx\n\nFor VPC-B → VPC-A traffic:\n  VPC-B route table needs: Destination 10.0.0.0\u002F16 → Target pcx-xxx\n\nMissing either route = traffic flows in ONE direction only (or not at all).\nBoth routes are needed for bidirectional communication.\n```\n\n**Key implication:** the #1 cause of \"my peering doesn't work\" is a\nmissing route table entry on the accepter side. Always verify BOTH\nsides have routes pointing to the peering connection.\n\n## Expert heuristic: when to use peering vs Transit Gateway\n\nVPC peering is one-to-one. Transit Gateway is hub-and-spoke (many-to-\nmany). The decision depends on topology.\n\n```text\nNumber of VPCs to connect:\n  ├── 2 VPCs → VPC peering (simplest, no additional cost beyond data transfer)\n  ├── 3-4 VPCs, full mesh → VPC peering (n*(n-1)\u002F2 connections; manageable)\n  │     3 VPCs = 3 peering connections\n  │     4 VPCs = 6 peering connections\n  ├── 5+ VPCs, or hub-and-spoke → Transit Gateway (avoids peering explosion)\n  │     5 VPCs full mesh = 10 peering connections; TGW = 1 attachment per VPC\n  ├── Need transitive routing (A→B→C) → Transit Gateway (peering is NOT transitive)\n  ├── Need VPN\u002FDirect Connect integration → Transit Gateway\n  └── Cost-sensitive, 2 VPCs → VPC peering (no hourly TGW charge)\n```\n\n**Key implication:** peering is free (no per-hour charge; you pay only\nfor data transfer). Transit Gateway charges per-hour per-attachment plus\ndata processing. For 2 VPCs, peering is almost always the right choice.\nFor 5+ VPCs or transitive routing, Transit Gateway is better.\n\n## Expert heuristic: cross-account acceptance automation\n\nIn cross-account peering, the accepter account must call\n`accept-vpc-peering-connection`. This requires either manual action in\nthe accepter account's console\u002FCLI, or automated role assumption.\n\n```text\nCross-account peering flow:\n  1. Requester account creates the peering connection (create-vpc-peering-connection)\n     → Connection status: pending-acceptance\n  2. Accepter account accepts (accept-vpc-peering-connection)\n     → Requires IAM permission in the accepter account\n     → Options:\n       ├── Manual: operator logs into accepter account, runs accept\n       ├── Automated: requester assumes a role in accepter account via STS\n       │   aws sts assume-role --role-arn arn:aws:iam::\u003Caccepter>:role\u002F...\n       │   → then call accept-vpc-peering-connection with accepter credentials\n       └── Lambda\u002FEventBridge: accepter account auto-accepts via EventBridge rule\n  3. Connection status: active\n  4. Both sides update route tables\n```\n\n**Key implication:** cross-account peering adds an acceptance step that\nsame-account peering does not. Plan for the IAM role or manual step.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Requester VPC exists | Peering requires an existing VPC | `aws ec2 describe-vpcs --vpc-ids \u003Cvpc-id>` |\n| Accepter VPC ID known | Must specify the peer VPC at creation | Confirm VPC ID in the accepter account |\n| CIDR blocks do NOT overlap | Overlapping CIDRs break routing; peering may create but traffic fails | Compare VPC CIDRs |\n| AWS account IDs (if cross-account) | Cross-account peering needs both account IDs | `aws sts get-caller-identity` |\n| Regions identified (if inter-region) | Inter-region peering specifies peer region | Confirm both regions |\n| IAM permission in accepter account | Accepter must accept the connection | Verify `ec2:AcceptVpcPeeringConnection` |\n| Route table IDs identified | Routes must be added to specific route tables | `aws ec2 describe-route-tables` |\n| DNS resolution decision | Must be explicitly enabled on both sides | Assess DNS requirements |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Requester\u002Faccepter model\n\nVPC peering uses a requester\u002Faccepter model. The requester creates the\npeering connection; the accepter accepts it.\n\n| Role | Action | API call |\n|---|---|---|\n| Requester | Creates the peering connection | `create-vpc-peering-connection` |\n| Accepter | Accepts the peering connection | `accept-vpc-peering-connection` |\n| Both | Update route tables | `create-route` (each side) |\n\n**Same-account peering:** the requester can auto-accept if it has\npermission. The accepter role is the same account.\n\n**Cross-account peering:** the accepter is a DIFFERENT account. The\naccepter must explicitly accept (manually or via role assumption).\n\n## Step 2 — Same-account vs cross-account\n\n| Feature | Same-account | Cross-account |\n|---|---|---|\n| Acceptance | Can be auto-accepted (if IAM permits) | Must be explicitly accepted by accepter account |\n| Security group cross-references | Supported (same account) | NOT supported (use CIDR rules) |\n| IAM complexity | Single account | Need role assumption or manual acceptance |\n| Peering limit | 125 active peering connections per VPC (soft limit) | Same |\n\n**Cross-account requires:** the accepter account's VPC ID AND account\nID at creation time. The requester specifies `--peer-owner-id`.\n\n## Step 3 — Same-region vs inter-region\n\n| Feature | Same-region | Inter-region |\n|---|---|---|\n| Latency | Minimal (within-region) | Slightly higher (cross-region backbone) |\n| Data transfer cost | Standard intra-region | Cross-region data transfer charges apply |\n| Security group cross-references | Supported (same region) | NOT supported (use CIDR rules) |\n| DNS resolution | Supported | Supported (with flag on both sides) |\n| `--peer-region` | Not needed (same region) | REQUIRED (must specify peer region) |\n| Max inter-region peerings | N\u002FA | 125 per VPC (soft limit) |\n\n**Inter-region data transfer cost** is the primary trade-off. Inter-\nregion traffic incurs cross-region data transfer charges (~$0.01-$0.02\nper GB depending on regions). Same-region peering has standard intra-\nregion data transfer rates.\n\n## Step 4 — Create and accept the peering connection\n\nStep 4 — create\u002Faccept CLI walkthroughs (same-account, cross-account, inter-region) — moved verbatim.\nFull detail: [Worked examples](references\u002Fworked-examples.md).\n\n**Common mistake:** trying to update route tables before the connection\nis ACTIVE. Route creation fails if the peering is still\n`pending-acceptance`.\n\n## Step 5 — Route table updates (BOTH sides required)\n\nRoute tables on BOTH the requester and accepter sides must be updated\nto route traffic to the peered VPC's CIDR via the peering connection.\nThis is the most commonly forgotten step.\n\nStep 5 — route table update commands (both sides required) — moved verbatim.\nFull detail: [Routing and DNS](references\u002Frouting-and-dns.md).\n\n**Critical:** BOTH routes are needed for bidirectional traffic. Missing\nthe accepter-side route is the #1 cause of \"peering doesn't work.\"\n\nFor multiple route tables per VPC (e.g., public and private subnets),\nupdate EACH route table that needs to route to the peered VPC.\n\n## Step 6 — DNS resolution (allowDnsResolutionFromPeeredVpc)\n\nBy default, DNS hostnames from one VPC are NOT resolvable from the\npeered VPC. To enable cross-VPC DNS resolution, set\n`AllowDnsResolutionFromPeeredVpc` to true on the peering connection.\n\nStep 6 — DNS resolution enablement commands (both sides) — moved verbatim.\nFull detail: [Routing and DNS](references\u002Frouting-and-dns.md).\n\n**Critical:** BOTH sides must enable the flag for bidirectional DNS\nresolution. Enabling it on one side only does NOT work.\n\n**Prerequisites for DNS resolution:**\n- Both VPCs must have `enableDnsHostnames` and `enableDnsSupport` set\n  to true.\n- The peering connection must be ACTIVE.\n\n## Step 7 — Security group cross-VPC references\n\nSecurity group cross-VPC references allow a SG rule to reference a\nsecurity group in the peered VPC by its ID (e.g., `sg-xxx` from the\npeer VPC). This is more precise than CIDR-based rules.\n\n**Constraint: only works within the SAME account AND SAME region.**\nCross-account or inter-region peering CANNOT use SG cross-references.\nUse CIDR-based rules instead.\n\nStep 7 — SG cross-reference vs CIDR-based rule commands — moved verbatim.\nFull detail: [Cross-account and security](references\u002Fcross-account-and-security.md).\n\n## Step 8 — Limitations (no transitive routing)\n\nVPC peering has hard limitations. A baseline model may not surface\nthese; they are critical for topology design.\n\n| Limitation | Description | Workaround |\n|---|---|---|\n| No transitive routing | A→B and B→C does NOT allow A→C | Create direct A→C peering, or use Transit Gateway |\n| No edge-to-edge routing | Traffic cannot traverse a peering to reach a VPN\u002FDirect Connect\u002FIGW on the peer side | Use Transit Gateway for VPN\u002FDX integration |\n| Overlapping CIDRs | Peering with overlapping CIDRs breaks routing (may create but traffic fails) | Re-design CIDR allocation; use non-overlapping ranges |\n| Max peering connections | 125 active peerings per VPC (soft limit) | Request limit increase, or use Transit Gateway |\n| SG cross-references | Same account + same region only | Use CIDR-based rules for cross-account\u002Finter-region |\n\n**The no-transitive-routing limitation is the most impactful.** Many\noperators assume that peering VPC-A to VPC-B and VPC-B to VPC-C allows\nVPC-A to reach VPC-C. It does NOT. Each pair needs a direct peering\nconnection. For transitive topologies, use AWS Transit Gateway.\n\n## Step 9 — IPv6 support\n\nVPC peering supports IPv6 traffic if both VPCs have IPv6 CIDR blocks\nassigned. IPv6 routes must be added separately (in addition to IPv4\nroutes).\n\nStep 9 — IPv6 route commands (both sides) — moved verbatim.\nFull detail: [Routing and DNS](references\u002Frouting-and-dns.md).\n\nIPv4 and IPv6 routing are independent. Both must be configured if both\nprotocols are needed.\n\n## Step 10 — Recent features\n\nStep 10 — recent AWS features (2023-2026) — moved verbatim.\nFull detail: [Advanced Patterns](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER assume creating and accepting the peering is enough.** Route\n   tables on BOTH sides must be updated. Without routes, NO traffic\n   flows. The accepter-side route is the #1 forgotten step.\n\n2. **NEVER assume VPC peering supports transitive routing.** A→B and\n   B→C does NOT allow A→C. Each pair needs a direct peering connection.\n   For transitive topologies, use Transit Gateway.\n\n3. **NEVER peer VPCs with overlapping CIDR blocks.** The peering may\n   create, but routing fails because the destination CIDR is ambiguous.\n   Always verify non-overlapping CIDRs before creating the peering.\n\n4. **NEVER use security group cross-VPC references for cross-account or\n   inter-region peering.** SG cross-references work ONLY within the same\n   account AND same region. For cross-account or inter-region, use\n   CIDR-based SG rules.\n\n5. **NEVER enable DNS resolution on only one side.**\n   `AllowDnsResolutionFromPeeredVpc` must be true on BOTH the requester\n   AND accepter for bidirectional DNS resolution. One-sided enablement\n   does not work.\n\n6. **NEVER forget IPv6 routes if using IPv6.** IPv4 and IPv6 routing\n   are independent. Add IPv6 routes separately (using\n   `--destination-ipv6-cidr-block`) if IPv6 traffic is needed.\n\n7. **NEVER assume route table updates propagate automatically.** Each\n   route table in each VPC must be explicitly updated. If a VPC has\n   multiple route tables (e.g., public\u002Fprivate subnets), update EACH\n   one that needs to route to the peered VPC.\n\n8. **NEVER use VPC peering for edge-to-edge routing.** Traffic cannot\n   traverse a peering to reach a VPN, Direct Connect, or Internet\n   Gateway on the peer side. Use Transit Gateway for these patterns.\n\n9. **NEVER create peering connections without a CIDR overlap check.**\n   Always compare VPC CIDR blocks before creating the peering.\n   Overlapping CIDRs are a silent failure (peering creates, traffic\n   fails).\n\n10. **NEVER assume cross-account acceptance is automatic.** The\n    accepter account must explicitly accept the peering connection\n    (manually or via IAM role assumption). Plan for the acceptance\n    step.\n\n## Output format\n\n```text\nVPC_PEERING: \u003Crequester-vpc-id> ↔ \u003Caccepter-vpc-id> (\u003Cpcx-id>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Requester VPC: \u003Cvpc-id> (\u003Ccidr>)\n  [✓|✗] Accepter VPC: \u003Cvpc-id> (\u003Ccidr>)\n  [✓|✗] CIDR overlap check: PASS (non-overlapping) | FAIL (overlapping)\n  [✓|✗] Account topology: Same-account | Cross-account (requester \u003Cacct>, accepter \u003Cacct>)\n  [✓|✗] Region topology: Same-region (\u003Cregion>) | Inter-region (requester \u003Cregion>, accepter \u003Cregion>)\n  [✓|✗] Peering connection: \u003Cpcx-id> — ACTIVE\n  [✓|✗] Route table (requester): \u003Crtb-id> → \u003Cpeer-cidr> via \u003Cpcx-id>\n  [✓|✗] Route table (accepter): \u003Crtb-id> → \u003Cpeer-cidr> via \u003Cpcx-id>\n  [✓|✗] DNS resolution: AllowDnsResolutionFromPeeredVpc=true (both sides) | Disabled\n  [✓|✗] Security group: cross-VPC reference (same acct+region) | CIDR-based (cross-account\u002Finter-region)\n  [✓|✗] IPv6 routing: enabled (IPv6 routes added both sides) | IPv4 only\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ec2 describe-vpc-peering-connections --vpc-peering-connection-ids \u003Cpcx-id> --region \u003Cregion>\n  aws ec2 describe-route-tables --route-table-ids \u003Crequester-rtb> --region \u003Cregion>\n  aws ec2 describe-route-tables --route-table-ids \u003Caccepter-rtb> --region \u003Cregion>\n```\n\n### Worked example — same-account, same-region peering with DNS resolution\n\n```text\nVPC_PEERING: vpc-aaa11122 ↔ vpc-bbb22233 (pcx-111222333)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Requester VPC: vpc-aaa11122 (10.0.0.0\u002F16)\n  [✓] Accepter VPC: vpc-bbb22233 (10.1.0.0\u002F16)\n  [✓] CIDR overlap check: PASS (10.0.0.0\u002F16 and 10.1.0.0\u002F16 do not overlap)\n  [✓] Account topology: Same-account (123456789012)\n  [✓] Region topology: Same-region (us-east-1)\n  [✓] Peering connection: pcx-111222333 — ACTIVE\n  [✓] Route table (requester): rtb-app111 → 10.1.0.0\u002F16 via pcx-111222333\n  [✓] Route table (accepter): rtb-data222 → 10.0.0.0\u002F16 via pcx-111222333\n  [✓] DNS resolution: AllowDnsResolutionFromPeeredVpc=true (both sides)\n  [✓] Security group: cross-VPC reference (sg-app → sg-data via peering)\n  [✓] IPv6 routing: IPv4 only\n  [✓] Tags: Environment=production, Topology=app-to-data\nVERIFICATION_COMMANDS:\n  aws ec2 describe-vpc-peering-connections --vpc-peering-connection-ids pcx-111222333 --region us-east-1\n  aws ec2 describe-route-tables --route-table-ids rtb-app111 --region us-east-1\n  aws ec2 describe-route-tables --route-table-ids rtb-data222 --region us-east-1\n```\n\n## Error handling\n\nError handling deep dives — moved verbatim.\nFull detail: [Error handling](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [Routing and DNS](references\u002Frouting-and-dns.md) — route table update commands (both sides), DNS resolution commands, IPv6 routes\n- [Cross-account and security](references\u002Fcross-account-and-security.md) — acceptance automation, SG cross-reference vs CIDR-based rule commands\n- [Worked examples](references\u002Fworked-examples.md) — create\u002Faccept CLI walkthroughs (same-account, cross-account, inter-region)\n- [Error handling](references\u002Ferror-handling.md) — pending-acceptance, no-traffic, DNS, SG-reference, CIDR-overlap fixes\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — recent features 2023-2026\n\n## Domain\n\nAWS CloudOps \u002F Amazon VPC Peering Connection Provisioning & Network\nConnectivity.\n\n## AWS documentation\n\n- **VPC Peering Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fwhat-is-vpc-peering.html\n- **Create peering connection** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fcreate-vpc-peering-connection.html\n- **Accept peering connection** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Faccept-vpc-peering-connection.html\n- **Route tables for peering** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fvpc-peering-routing.html\n- **DNS resolution** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fmodify-peering-connection-options.html\n- **Security group references** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fsecurity-group-references.html\n- **Inter-region peering** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Finter-region-peering.html\n- **VPC peering limits** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002Fvpc-peering-limitations.html\n- **IPv6 in VPCs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fvpc-ip-addressing.html#vpc-ipv6\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, vpc, vpc-peering, cloudops, deploy, networking, provisioning, cross-account, inter-region, route-table, dns-resolution, security-group, ipv6","1","Jacky Chan — AWS Community Builder","aws-cloudops","Networking","0.1.0","aws, vpc, vpc peering, peering connection, cloudops, deploy, provisioning, cross-account, inter-region, requester, accepter, route table, dns resolution, security group reference, ipv6, transitive routing, edge-to-edge","deploy","high","false","capability","Invoke when the user wants to create a VPC peering connection between two VPCs (same-account or cross-account, same-region or inter-region), configure DNS resolution across peered VPCs, update route tables on both sides for traffic flow, reference security groups across peered VPCs, or understand VPC peering limitations (no transitive routing). Do NOT invoke for AWS Transit Gateway (use transit-gateway skills), VPC endpoints (PrivateLink), or VPN\u002FDirect Connect connectivity.","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ec2 access (and cross-account STS assume-role if cross-account peering). Works with Terraform aws_vpc_peering_connection \u002F aws_vpc_peering_connection_accepter \u002F aws_route resources and CloudFormation AWS::EC2::VPCPeeringConnection templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fvpc-peering-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill vpc-peering-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill vpc-peering-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill vpc-peering-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5623,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcross-account-same-region.md",658,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fbaselines\u002Fcross-account-same-region.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Finter-region-peering.md",610,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fbaselines\u002Finter-region-peering.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fipv6-peering.md",589,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fbaselines\u002Fipv6-peering.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fmissing-cidr-overlap-check.md",523,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fbaselines\u002Fmissing-cidr-overlap-check.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fsame-account-same-region-dns.md",701,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fbaselines\u002Fsame-account-same-region-dns.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1746,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9960,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcross-account-same-region.md",582,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fprompts\u002Fcross-account-same-region.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Finter-region-peering.md",596,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fprompts\u002Finter-region-peering.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fipv6-peering.md",522,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fprompts\u002Fipv6-peering.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fmissing-cidr-overlap-check.md",380,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fprompts\u002Fmissing-cidr-overlap-check.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fsame-account-same-region-dns.md",627,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fevals\u002Fprompts\u002Fsame-account-same-region-dns.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6055,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",1543,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fcross-account-and-security.md",10182,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Freferences\u002Fcross-account-and-security.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Ferror-handling.md",1368,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Freferences\u002Ferror-handling.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Frouting-and-dns.md",10216,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Freferences\u002Frouting-and-dns.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",2175,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4397,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-peering-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]