[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADJH4AHM07F7P05HTD5DRR":3,"skill-same:01M7ADJH4AHM07F7P05HTD5DRR":149},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7ADJH4AHM07F7P05HTD5DRR","vpc-connectivity-troubleshooter",null,"Diagnoses AWS VPC network connectivity issues through a systematic OSI-layered diagnostic tree: Layer 3 routing (missing route, wrong target IGW\u002FNAT\u002FTGW\u002Fpeering\u002FVPN, overlapping CIDRs on peered VPCs), Layer 4 security groups (stateful inbound, outbound return path, SG references that silently fail cross-VPC), Layer 4 NACLs (stateless both directions, ephemeral range 1024-65535), Layer 7 DNS (Route 53 private hosted zones, VPC DNS resolution settings), VPC endpoint policies, and application-level auth\u002FSSL. Cross-VPC coverage: VPC peering (DNS flag, SG references), Transit Gateway (route table associations, propagation), and PrivateLink (interface endpoint NLB). Uses Reachability Analyzer and VPC Flow Logs. Emits ROOT_CAUSE_FOUND, NEED_MORE_INFO, or ESCALATE.","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-connectivity-troubleshooter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vpc-connectivity-troubleshooter\ndescription: 'Diagnoses AWS VPC network connectivity issues through a systematic OSI-layered diagnostic tree: Layer 3 routing (missing route, wrong target IGW\u002FNAT\u002FTGW\u002Fpeering\u002FVPN, overlapping CIDRs on peered VPCs), Layer 4 security groups (stateful inbound, outbound return path, SG references that silently fail cross-VPC), Layer 4 NACLs (stateless both directions, ephemeral range 1024-65535), Layer 7 DNS (Route 53 private hosted zones, VPC DNS resolution settings), VPC endpoint policies, and application-level auth\u002FSSL. Cross-VPC coverage: VPC peering (DNS flag, SG references), Transit Gateway (route table associations, propagation), and PrivateLink (interface endpoint NLB). Uses Reachability Analyzer and VPC Flow Logs. Emits ROOT_CAUSE_FOUND, NEED_MORE_INFO, or ESCALATE.'\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). Offline symptom classification works from pasted error messages and topology descriptions. Live-account diagnosis uses aws ec2 describe-route-tables, aws ec2 describe-security-groups, aws ec2 describe-network-acls, aws ec2 describe-vpc-endpoints, aws ec2 describe-vpc-peering-connections, aws ec2 describe-transit- gateway-attachments, aws ec2 describe-transit-gateway-route-tables, aws ec2...\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '2'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Networking\n  task_type: troubleshoot\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: ROOT_CAUSE_FOUND | NEED_MORE_INFO | ESCALATE\n  when_to_use: Diagnosing a VPC network connectivity issue (cannot reach an endpoint, intermittent connectivity, port blocked, DNS resolution failure, cross-VPC traffic failure, VPC endpoint policy block, peering asymmetry, TGW route propagation gap), walking a symptom to the failed layer with verify and fix commands, validating why an EC2 instance \u002F Lambda \u002F ECS task \u002F on-prem host cannot reach a destination, or triaging a \"the network is down\" page where the root cause may be routing, security groups, NACLs, DNS, endpoint policy, or cross-VPC plumbing — not necessarily the destination service itself.\n  when_not_to_use: Internet egress cost audits (use vpc-flow-logs-auditor or cost- anomaly detectors), RDS-specific auth and TLS issues (use rds- connectivity-troubleshooter which specialises the L7 layer for database engines), IAM execution-role diagnostics (use iam- permission-troubleshooter), or Direct Connect \u002F Site-to-Site VPN hardware configuration (use the carrier \u002F device-side tooling). This skill diagnoses packet-path connectivity; it does not audit configuration posture or replace dedicated per-service troubleshooters.\n  activation_triggers: VPC connection timeout, cannot reach EC2 instance, EC2 port unreachable, Lambda VPC timeout, ECS task cannot reach, security group blocking traffic, NACL dropping packets, route table missing, VPC peering not working, Transit Gateway routing, TGW routes not propagating, VPC endpoint policy blocked, DNS not resolving in VPC, Route 53 private hosted zone, cross-VPC connectivity, PrivateLink endpoint service, Reachability Analyzer, VPC Flow Logs analysis, overlapping CIDR peering, troubleshoot VPC connectivity\n  invocation_schema: 'Input: either (a) a symptom description (error message, observed behaviour, \"host cannot reach destination on port X\", intermittent vs persistent pattern), optionally paired with the source and destination context (instance\u002Fsubnet\u002FVPC IDs, ports, protocol), OR (b) a source-destination pair plus caller context (region, AZ, observed error) for live-account diagnosis. Output: a deterministic TARGET\u002FVERDICT\u002FREASON\u002FLAYER\u002FEVIDENCE\u002FREMEDIATION block where VERDICT ∈ {ROOT_CAUSE_FOUND, NEED_MORE_INFO, ESCALATE} and LAYER ∈ {ROUTE_TABLE_MISSING, ROUTE_TABLE_WRONG_TARGET, ROUTE_OVERLAPPING_CIDR, SG_INBOUND, SG_OUTBOUND, SG_REFERENCE_CROSS_VPC, NACL_STATELESS, DNS_RESOLUTION, DNS_PHZ_ASSOCIATION, ENDPOINT_POLICY, PEERING_INACTIVE, PEERING_DNS_RESOLUTION, PEERING_SG_REFERENCE, TGW_ROUTE_PROPAGATION, TGW_ASSOCIATION_MISSING, PRIVATELINK_ENDPOINT_SERVICE, PRIVATELINK_SG, APP_AUTH, UNKNOWN}.'\n  invocation_example: \"# Minimal valid input (offline symptom classification):\\nSymptom: \\\"application on EC2 instance i-app (subnet subnet-aaa,\\nSG sg-app, AZ us-east-1a, VPC vpc-source) cannot reach EC2\\ninstance i-db (subnet subnet-bbb, SG sg-db, AZ us-east-1b, VPC\\nvpc-target) on tcp\u002F5432. nc -vz returns 'Connection timed out'.\\nThe two VPCs are peered (pcx-aaa) and the peering status is\\nActive.\\\"\\nSource: i-app, subnet-aaa (CIDR 10.0.1.0\u002F24 in vpc-source\\n  10.0.0.0\u002F16), SG sg-app\\nDestination: i-db, subnet-bbb (CIDR 172.16.1.0\u002F24 in vpc-target\\n  172.16.0.0\u002F16), SG sg-db\\nPath: same region (us-east-1), VPC peering pcx-aaa (Active)\\nObserved error: nc -vz 172.16.1.10 5432 → \\\"Connection timed out\\\"\"\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: VPC, connectivity, routing, route table, security group, NACL, network ACL, ephemeral port, DNS, Route 53, private hosted zone, resolver, VPC endpoint, endpoint policy, VPC peering, Transit Gateway, TGW, PrivateLink, Reachability Analyzer, VPC Flow Logs, overlapping CIDR, troubleshooting\n  tags: vpc, networking, troubleshooting, routing, security-groups, nacl, dns, vpc-peering, transit-gateway, privatelink\n---\n\n# VPC Connectivity Troubleshooter\n\n## Quick start\n\n- **Symptom → layer map (first plausible match drives the first probe):**\n  timeout \u002F SYN no SYN-ACK → ROUTE_TABLE_MISSING \u002F\n  ROUTE_TABLE_WRONG_TARGET \u002F ROUTE_OVERLAPPING_CIDR \u002F SG_INBOUND \u002F\n  SG_OUTBOUND \u002F NACL_STATELESS \u002F PEERING_INACTIVE \u002F TGW_ROUTE_PROPAGATION\n  \u002F PRIVATELINK_ENDPOINT_SERVICE; connection refused \u002F TCP RST →\n  destination port closed (instance-level, outside this skill's VPC\n  scope — surface it); DNS NXDOMAIN \u002F \"server can't find\" →\n  DNS_RESOLUTION \u002F DNS_PHZ_ASSOCIATION; HTTP 403 from AWS service →\n  ENDPOINT_POLICY; cross-VPC success on IP but failure on hostname →\n  PEERING_DNS_RESOLUTION.\n- **Always verify with a probe, never guess.** Each layer has a single\n  command that proves or disproves it. A ROOT_CAUSE_FOUND verdict\n  requires positive evidence — a failing probe that matches the\n  symptom — not a process of elimination that \"must be the SG.\"\n- **OSI ordering is non-negotiable.** DNS (L7) → routing (L3) → SG\n  (stateful L3-L4) → NACL (stateless L4) → cross-VPC plumbing → port\n  reachability (L4) → application (L7). Skipping layers produces false\n  root causes.\n- **Security groups are stateful; NACLs are stateless.** A SG inbound\n  allow on 443 implicitly allows the return SYN-ACK. A NACL inbound\n  allow on 443 ALSO requires an outbound allow on the ephemeral range\n  (1024-65535) for the return packet, because NACLs evaluate each\n  direction independently. Operators who \"fixed the SG and still\n  cannot connect\" usually have a NACL denying the return path.\n- **SG references (`sg-xxx`) only work within the same VPC or a peered\n  VPC.** A SG rule referencing `sg-xxx` from an unrelated VPC is\n  silently ignored — the rule appears valid in the console but never\n  matches traffic. Use CIDR blocks or a referenced SG in the peered\n  VPC (with peering in the route table).\n- **ESCALATE for AWS-side incidents.** AZ-wide degradation, region-\n  wide service events, and underlying host failures are not customer-\n  fixable — escalate to AWS Support and surface the event ARN.\n\n## Mindset\n\nMindset detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for the incident-framing model.\n\n## Philosophy\n\nThe four senior-engineer behaviours (OSI ordering, SG stateful vs NACL stateless, overlapping-CIDR silent failure, SG-reference scope) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for the reasoning behind each probe-order rule.\n\n## Quick reference — symptom triage table\n\n| Symptom phrase \u002F error | Most likely layer | First probe |\n|---|---|---|\n| `Connection timed out`, `Operation timed out`, SYN no SYN-ACK | ROUTE_TABLE_MISSING \u002F ROUTE_TABLE_WRONG_TARGET \u002F ROUTE_OVERLAPPING_CIDR \u002F SG_INBOUND \u002F NACL_STATELESS \u002F PEERING_INACTIVE \u002F TGW_ROUTE_PROPAGATION | `describe-route-tables` + `describe-security-groups` + `describe-network-acls` for the source subnet |\n| `Connection refused`, `ECONNREFUSED`, TCP RST after SYN | Destination port closed (instance-level — outside this skill's VPC scope) | Confirm destination instance is running and listener is bound |\n| `Name or service not known`, `NXDOMAIN`, `server can't find` | DNS_RESOLUTION \u002F DNS_PHZ_ASSOCIATION | `dig`\u002F`nslookup` from source; `list-hosted-zones-by-vpc`; VPC DNS resolution\u002Fsupport settings |\n| HTTP 403 \u002F AccessDenied from an AWS service via VPC endpoint | ENDPOINT_POLICY | `describe-vpc-endpoints` (Policy, State) |\n| Cross-VPC success on IP but failure on hostname | PEERING_DNS_RESOLUTION | VPC peering `AllowDnsResolutionFromRemoteVpcDomainName` flag |\n| VPC peering Active but traffic times out | ROUTE_OVERLAPPING_CIDR \u002F PEERING_SG_REFERENCE \u002F route table missing pcx route | Compare VPC CIDRs; `describe-route-tables` for pcx route; `describe-security-groups` for SG reference scope |\n| TGW attachment Active but traffic times out | TGW_ROUTE_PROPAGATION \u002F TGW_ASSOCIATION_MISSING | `describe-transit-gateway-route-tables` for propagation; `describe-transit-gateway-attachments` for association |\n| PrivateLink endpoint accepted but service unreachable | PRIVATELINK_ENDPOINT_SERVICE \u002F PRIVATELINK_SG | `describe-vpc-endpoints` (ServiceName, State); NLB and endpoint SG allow |\n| Application reaches TCP layer but auth\u002FSSL fails | APP_AUTH | Application logs; SSL\u002FTLS handshake details |\n| None of the above, region-wide event | ESCALATE | `aws health describe-events` + AWS Service Health Dashboard |\n\n## Pre-flight: source \u002F destination context and AWS Health gate\n\nBefore running symptom-specific probes, gather the canonical source and\ndestination context and short-circuit on AWS-side events that mimic\nconnectivity failures. Misclassifying these produces hours of network\ndebugging for a problem that is not a network problem.\n\n### Pre-flight commands\n\nSource\u002Fdestination context + AWS Health pre-flight command listing moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand before the first probe.\n\n### Pre-flight short-circuits\n\n| Signal | Effect |\n|---|---|\n| AWS Health open event for `AWS_EC2`, `AWS_VPC`, `AWS_DIRECTCONNECT` in the region | Likely AWS-side degradation. Surface in REMEDIATION; consider ESCALATE. |\n| Source instance `State: stopped` or `terminated` | Not a connectivity issue; the source is gone. |\n| Destination instance `State: stopped` or `terminated` | Not a connectivity issue; the destination is gone. Surface as ROOT_CAUSE_FOUND with `LAYER: APP_AUTH` (no listener) or `UNKNOWN`. |\n| Destination AZ has a known AWS Health event | Traffic to that AZ may fail while cross-AZ paths succeed. Note the AZ-specific signal. |\n| Source subnet `AvailableIpAddressCount: 0` | Subnet is exhausted; new ENIs cannot be created. Symptom is on ENI-creating workloads (Lambda VPC attach, ECS tasks). |\n\nIf the input is malformed (missing source or destination identifier,\nabsent symptom, no port\u002Fprotocol for reachability diagnosis), emit:\n\nThe NEED_MORE_INFO malformed-input output template moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nEmit it whenever required context is missing.\n\n## Process — Diagnostic decision tree (apply in symptom order)\n\nThe diagnostic tree is symptom-driven. Pick the entry point based on the\nobserved symptom, then walk the layer-specific probes in OSI order. Each\nlayer ends with either a positive root-cause confirmation (failing probe\nthat matches the symptom) or a pass that moves to the next layer. **Never\nemit ROOT_CAUSE_FOUND without a failing probe that matches the symptom.**\n\n### Step 0: Non-obvious behaviours that change diagnosis\n\nThe full Step-0 gotcha catalog (cross-VPC SG references, NACL statelessness, overlapping CIDRs, peering non-transitivity, DNS flags, PHZ association, endpoint policy vs IAM, TGW propagation, PrivateLink handshake, nc ground truth, Reachability Analyzer, Flow Logs, Lambda\u002FIGW asymmetry, cross-AZ cost) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand before diagnosing any non-trivial symptom.\n\n### Step 1: Symptom entry — pick the diagnostic branch\n\nMap the symptom to a branch and jump to that branch's section. If the\nsymptom matches none of the categories, route to Step 9 (ESCALATE or\nNEED_MORE_INFO).\n\n| Symptom | Branch |\n|---|---|\n| `Connection timed out`, SYN no SYN-ACK, `nc -vz` hangs | Step 2 — Timeout (OSI walk) |\n| `Name or service not known`, `NXDOMAIN`, hostname does not resolve | Step 3 — DNS |\n| HTTP 403 from AWS service via VPC endpoint | Step 4 — VPC endpoint policy |\n| Cross-VPC via peering: peering Active but traffic times out | Step 5 — VPC peering |\n| Cross-VPC via TGW: attachments Active but traffic times out | Step 6 — Transit Gateway |\n| Cross-VPC via PrivateLink: endpoint accepted but service unreachable | Step 7 — PrivateLink |\n| TCP reaches but TLS \u002F auth fails | Step 8 — Application |\n| None of the above | Step 9 — Escalate \u002F NEED_MORE_INFO |\n\n### Step 2: Connection timeout — OSI-aligned diagnostic tree\n\nSub-steps 2a-2j — the full OSI walk (source\u002Fdest context, route tables both sides, overlapping CIDRs, SG inbound\u002Foutbound + cross-VPC SG references, NACLs in both directions on both subnets, nc\u002Ftelnet probe, VPC Flow Logs, Reachability Analyzer) with every probe command and verdict condition moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when diagnosing a timeout symptom.\n\n### Step 3: DNS resolution failure\n\nDNS probes (resolver\u002FDHCP options, enableDnsSupport + enableDnsHostnames, Route 53 PHZ association, Resolver endpoints and rules) with DNS_RESOLUTION \u002F DNS_PHZ_ASSOCIATION verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when a hostname does not resolve.\n\n### Step 4: VPC endpoint policy\n\nEndpoint-policy probes (describe-vpc-endpoints policy read, endpoint bypass test) with ENDPOINT_POLICY verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand on AccessDenied that clears outside the VPC.\n\n### Step 5: VPC peering — Active but traffic times out\n\nPeering probes (status table, both-side pcx routes, overlapping CIDRs, cross-VPC SG references, remote DNS resolution flag) with PEERING_* verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when peering is Active but traffic times out.\n\n### Step 6: Transit Gateway — attachments Active but traffic times out\n\nTGW probes (attachment state, TGW route-table association vs propagation, both-side tgw routes) with TGW_ASSOCIATION_MISSING \u002F TGW_ROUTE_PROPAGATION verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when attachments are Active but traffic times out.\n\n### Step 7: PrivateLink — endpoint accepted but service unreachable\n\nPrivateLink probes (endpoint state, endpoint-SG ENI, provider endpoint service + NLB health, private DNS) with PRIVATELINK_* verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when an endpoint is accepted but the service is unreachable.\n\n### Step 8: Application layer — TLS \u002F auth\n\nAPP_AUTH routing guidance (TLS\u002Fauth symptoms route to the application-specific troubleshooters) moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when TCP succeeds but TLS or auth fails.\n\n### Step 9: Escalate or NEED_MORE_INFO\n\nESCALATE \u002F NEED_MORE_INFO exit rules (AWS-side incidents, missing operator input) moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when no layer produced a positive match.\n\n## Output format\n\n```text\nTARGET: \u003Csource → destination pair>\nVERDICT: ROOT_CAUSE_FOUND | NEED_MORE_INFO | ESCALATE\nREASON: \u003C1-2 sentences naming the failed layer and the failing probe>\nLAYER: \u003CROUTE_TABLE_MISSING | ROUTE_TABLE_WRONG_TARGET |\n        ROUTE_OVERLAPPING_CIDR | SG_INBOUND | SG_OUTBOUND |\n        SG_REFERENCE_CROSS_VPC | NACL_STATELESS | DNS_RESOLUTION |\n        DNS_PHZ_ASSOCIATION | ENDPOINT_POLICY | PEERING_INACTIVE |\n        PEERING_DNS_RESOLUTION | PEERING_SG_REFERENCE |\n        TGW_ROUTE_PROPAGATION | TGW_ASSOCIATION_MISSING |\n        PRIVATELINK_ENDPOINT_SERVICE | PRIVATELINK_SG | APP_AUTH |\n        UNKNOWN>\nEVIDENCE:\n  - \u003Cobserved symptom — error string or behaviour>\n  - \u003Cfailing probe — command and its output that confirms the cause>\n  - \u003Cpassing probes — layers ruled out>\nREMEDIATION:\n  1. \u003Cspecific action with CLI command>\n  2. \u003Cverification command after the fix>\nCONFIRM: Before executing any state-changing CLI, emit and await operator\n  approval: \"CONFIRM: About to \u003Caction> on \u003Cid> in \u003Cregion>. Proceed?\n  (yes\u002Fno)\"\n```\n\n### Worked example — SG inbound missing rule\n\n```text\nTARGET: i-app (10.0.1.10, subnet-aaa, vpc-source) → i-db\n  (172.16.1.10, subnet-bbb, vpc-target) on tcp\u002F5432\nVERDICT: ROOT_CAUSE_FOUND\nREASON: The destination SG sg-db has no inbound rule matching the\n  source's CIDR 10.0.1.0\u002F24 on port 5432 — the SYN is dropped at the\n  instance's security group (Step 2e).\nLAYER: SG_INBOUND\nEVIDENCE:\n  - Symptom: application on i-app (10.0.1.10) reports \"Operation\n    timed out\" when connecting to i-db (172.16.1.10:5432). nc -vz\n    hangs.\n  - Probe: aws ec2 describe-security-groups --group-ids sg-db returns\n    inbound rules allowing 172.16.0.0\u002F16 (local VPC) on 5432. No\n    rule matches 10.0.1.0\u002F24 (source VPC CIDR).\n  - Passing: route table for subnet-aaa has a pcx-aaa route to\n    172.16.0.0\u002F16; route table for subnet-bbb has a pcx-aaa route\n    back to 10.0.0.0\u002F16; peering pcx-aaa is Active; VPC CIDRs do not\n    overlap; NACL on both subnets is the default (allow all).\nREMEDIATION:\n  1. Add an inbound rule to sg-db allowing the source CIDR on tcp\u002F5432:\n     aws ec2 authorize-security-group-ingress --group-id sg-db\n       --protocol tcp --port 5432 --cidr 10.0.1.0\u002F24 --profile \u003Cp>\n  2. Verify from the source: nc -vz 172.16.1.10 5432 (should succeed\n     within 1s).\nCONFIRM: Before authorizing the SG ingress, emit and await:\n  \"CONFIRM: About to authorize-security-group-ingress on sg-db in\n   us-east-1 for 10.0.1.0\u002F24 on tcp\u002F5432. Proceed? (yes\u002Fno)\"\n```\n\n### Worked example — NACL missing ephemeral outbound\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a NACL_STATELESS verdict.\n\n### Worked example — overlapping CIDR (silent peering failure)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a ROUTE_OVERLAPPING_CIDR verdict.\n\n### Worked example — VPC endpoint policy blocking S3 PutObject\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting an ENDPOINT_POLICY verdict.\n\n## STRICT output contract\n\nThis contract is mandatory. The Output format template above is the\nauthoritative structure; the rules below disambiguate the failure\nmodes that score D8=13 on this skill. Violating any rule is a\nmisdiagnosis.\n\n### Required output structure\n\nEvery diagnosis MUST emit this exact block, with all fields populated\n(no empty fields, no omitted sections, no reordering):\n\nThe literal block template is the one in ## Output format above; this annotated duplicate moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when the contract wording is unclear.\n\nVerdict-specific rules:\n- `ROOT_CAUSE_FOUND` → LAYER is one of the 18 enum values; EVIDENCE\n  includes a failing probe whose output positively confirms the cause\n  (not a process of elimination); REMEDIATION is actionable CLI.\n- `NEED_MORE_INFO` → LAYER is `UNKNOWN` or the best candidate; EVIDENCE\n  lists the missing input (source ID, destination ID, port, protocol,\n  region) and the next probe to run once it is supplied.\n- `ESCALATE` → LAYER is the suspected AWS-side category; REASON cites\n  the AWS Health event ARN or the carrier\u002Fout-of-band signal.\n\n### FORBIDDEN output patterns\n\n1. NEVER skip the NACL check — NACLs are stateless, both inbound AND\n   outbound rules needed for ephemeral ports 1024-65535. A diagnosis\n   that omits `describe-network-acls` for both source and destination\n   subnets is incomplete, even if a SG rule matches.\n2. NEVER assume a Security Group reference works cross-VPC — SG\n   references (`sg-xxx`) only resolve within the same VPC or a peered\n   VPC with peering in the route table, not via Transit Gateway. A\n   cross-VPC SG reference via TGW is silently ignored.\n3. NEVER declare ROOT_CAUSE_FOUND without a failing probe that matches\n   the symptom. \"It must be the SG\" by process of elimination is\n   forbidden — cite the `describe-security-groups` or `nc -vz` output\n   that positively confirms the drop.\n4. NEVER skip the OSI order for timeout symptoms. The probe order is\n   DNS (L7) → routing (L3) → SG (L4) → NACL (L4) → cross-VPC plumbing\n   → port reachability → application. A diagnosis that checks the SG\n   before the route table and concludes \"SG is fine\" missed that the\n   SYN never reached the SG evaluation.\n5. NEVER treat VPC peering as transitive. Peering between A-B and B-C\n   does NOT allow A to reach C via B — transit requires Transit\n   Gateway. A diagnosis that suggests \"add a peering route through\n   VPC-B\" is wrong.\n6. NEVER assume overlapping VPC CIDRs will route via peering. They are\n   a silent failure: the `pcx-xxx` route appears in the table but\n   packets do not deliver. A diagnosis that lists peering Active +\n   route present as \"passing\" without comparing the two VPC CIDRs is\n   incomplete.\n7. NEVER assume the VPC endpoint policy matches the IAM policy. The\n   endpoint policy is an independent layer that can deny actions IAM\n   allows. A diagnosis that clears IAM without bypassing the endpoint\n   to verify has not ruled out `ENDPOINT_POLICY`.\n\n### Perfect example output\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a complete ROOT_CAUSE_FOUND verdict.\n\n## Anti-Patterns — NEVER\n\n- NEVER declare ROOT_CAUSE_FOUND without a failing probe that matches\n  the symptom. A \"process of elimination\" diagnosis erodes operator\n  trust when the real cause is elsewhere.\n\n- NEVER skip the OSI order for timeout symptoms. If you check the\n  security group before the route table and conclude \"the SG is fine,\n  must be the destination,\" you missed that the route table has no\n  route for the destination CIDR — the SYN never reached the SG\n  evaluation.\n\n- NEVER evaluate NACLs in only one direction. NACLs are stateless;\n  the return SYN-ACK is a separate evaluation. The most common NACL\n  mistake is an inbound rule on 443 with no outbound rule on the\n  ephemeral range (1024-65535).\n\n- NEVER assume a security-group reference (`sg-xxx`) works cross-VPC.\n  Cross-VPC SG references are silently ignored unless the VPCs are\n  peered AND the peering is in the route table. Use CIDR blocks or a\n  referenced SG in the peered VPC.\n\n- NEVER treat VPC peering as transitive. Peering between A-B and B-C\n  does NOT allow A to reach C via B. Transit requires Transit Gateway.\n\n- NEVER assume overlapping VPC CIDRs will route via peering. They are\n  a silent failure — the route appears but packets do not deliver.\n\n- NEVER assume the VPC DNS settings are correct because \"DNS works\n  for some queries.\" Route 53 private hosted zones require BOTH\n  `enableDnsSupport` AND `enableDnsHostnames` to be true. Cross-\n  account PHZs require explicit association with the consumer VPC.\n\n- NEVER assume the VPC endpoint policy matches the IAM policy. The\n  endpoint policy is an independent layer; it can deny actions that\n  IAM allows. Bypass the endpoint to verify.\n\n- NEVER assume `PrivateDnsEnabled: true` on an interface endpoint is\n  cosmetic. Without it, the service's DNS name resolves to the public\n  IP and traffic routes over the internet instead of the endpoint.\n\n- NEVER conclude \"the network is flaky\" without running `nc -vz` or\n  equivalent from the source host at least three times. Intermittent\n  packet loss is rare in VPC; intermittent failures are usually\n  stateful (DNS cache, connection pool, failover) not packet-loss.\n\n- NEVER assume Transit Gateway route propagation is automatic. Each\n  attachment must be associated with a TGW route table AND propagate\n  its routes. Association alone does not propagate.\n\n- NEVER assume PrivateLink endpoint service availability implies NLB\n  health. The endpoint can be `available` while the NLB has no\n  healthy targets in the consumer's AZ. Always check NLB target\n  health.\n\n- NEVER recommend modifying a NACL to deny specific traffic as a\n  security fix without checking the existing rule order. NACLs\n  evaluate lowest-to-highest rule number; first match wins. A new\n  deny at rule 200 is shadowed by an existing allow at rule 100.\n\n- NEVER recommend expanding a CIDR to `0.0.0.0\u002F0` to \"fix\" a SG\n  issue. This exposes the listener to the entire internet. Use the\n  narrowest scope that covers the legitimate source.\n\n- NEVER rely on Reachability Analyzer as the sole evidence. It models\n  the configured state; it does not test the live packet. Pair it\n  with `nc -vz` from the source host.\n\n- NEVER skip VPC Flow Logs when diagnosing intermittent issues. Flow\n  Logs with `action: REJECT` confirm the packet was dropped by SG or\n  NACL; `action: ACCEPT` confirms the packet reached the ENI.\n\n## Pre-flight safety checks (run before any state-changing CLI)\n\nPre-flight safety checks (confirmation gate, read-only-first, SG\u002FNACL\u002Froute\u002Fpeering\u002FTGW\u002Fendpoint blast-radius rules, bulk batch limit) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand before any state-changing CLI.\n\n## Remediation guidance\n\nPer-LAYER remediation commands for all 17 layer values (create-route, replace-route, SG ingress\u002Fegress, NACL ephemeral entries, DNS attributes, PHZ association, endpoint policy, peering accept\u002FDNS options, TGW propagation\u002Fassociation, PrivateLink NLB\u002FSG) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when writing the REMEDIATION block.\n\n## Deep reference: VPC connectivity layer model\n\nLayer model, SG-vs-NACL comparison, VPC peering vs Transit Gateway, and VPC endpoint type tables moved verbatim to [references\u002Fconnectivity-layer-reference.md](references\u002Fconnectivity-layer-reference.md).\nLoad on demand for the comparison tables.\n\n## Recent AWS features (2024-2026)\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand to check what changed in the last 24 months.\n\n## References (load on demand)\n\n- [Diagnostic commands](references\u002Fdiagnostic-commands.md) — pre-flight context commands and the full Step 2-9 diagnostic walk with every probe command and verdict condition\n- [Worked examples](references\u002Fworked-examples.md) — secondary worked examples (NACL ephemeral outbound, overlapping CIDR, endpoint policy), the NEED_MORE_INFO re-prompt template, and annotated output-contract templates\n- [Error handling](references\u002Ferror-handling.md) — pre-flight safety checks before state-changing CLIs and per-LAYER remediation guidance with fix and verify commands\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — mindset, philosophy, Step-0 non-obvious behaviours, and recent AWS features (2024-2026)\n- [Connectivity layer reference](references\u002Fconnectivity-layer-reference.md) — ports and protocol semantics, SG\u002FNACL evaluation, peering\u002FTGW\u002FPrivateLink specifics, plus the moved layer-model comparison tables\n\n## Domain\n\nAWS CloudOps \u002F VPC Networking, Routing, Security Groups, NACLs, DNS,\nCross-VPC Connectivity (Peering, Transit Gateway, PrivateLink), and\nPacket-Path Diagnostics.\n\n## AWS documentation\n\n- **Amazon VPC User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002F\n- **VPC route tables** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002FVPC_Route_Tables.html\n- **Security groups** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002FVPC_SecurityGroups.html\n- **Network ACLs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fvpc-network-acls.html\n- **VPC peering** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002FWelcome.html\n- **Transit Gateway** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Ftgw\u002FWhat_is_TGW.html\n- **AWS PrivateLink** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fprivatelink\u002Fconcepts.html\n- **VPC endpoints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fvpc-endpoints.html\n- **Reachability Analyzer** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Freachability\u002FWhat-is-Reachability-Analyzer.html\n- **VPC Flow Logs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fflow-logs.html\n- **Route 53 Resolver** — https:\u002F\u002Fdocs.aws.amazon.com\u002FRoute53\u002Flatest\u002FDeveloperGuide\u002Fresolver.html\n- **AWS Health** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fhealth\u002Flatest\u002Fug\u002F\n","# VPC Connectivity Troubleshooter\n\n## Quick start\n\n- **Symptom → layer map (first plausible match drives the first probe):**\n  timeout \u002F SYN no SYN-ACK → ROUTE_TABLE_MISSING \u002F\n  ROUTE_TABLE_WRONG_TARGET \u002F ROUTE_OVERLAPPING_CIDR \u002F SG_INBOUND \u002F\n  SG_OUTBOUND \u002F NACL_STATELESS \u002F PEERING_INACTIVE \u002F TGW_ROUTE_PROPAGATION\n  \u002F PRIVATELINK_ENDPOINT_SERVICE; connection refused \u002F TCP RST →\n  destination port closed (instance-level, outside this skill's VPC\n  scope — surface it); DNS NXDOMAIN \u002F \"server can't find\" →\n  DNS_RESOLUTION \u002F DNS_PHZ_ASSOCIATION; HTTP 403 from AWS service →\n  ENDPOINT_POLICY; cross-VPC success on IP but failure on hostname →\n  PEERING_DNS_RESOLUTION.\n- **Always verify with a probe, never guess.** Each layer has a single\n  command that proves or disproves it. A ROOT_CAUSE_FOUND verdict\n  requires positive evidence — a failing probe that matches the\n  symptom — not a process of elimination that \"must be the SG.\"\n- **OSI ordering is non-negotiable.** DNS (L7) → routing (L3) → SG\n  (stateful L3-L4) → NACL (stateless L4) → cross-VPC plumbing → port\n  reachability (L4) → application (L7). Skipping layers produces false\n  root causes.\n- **Security groups are stateful; NACLs are stateless.** A SG inbound\n  allow on 443 implicitly allows the return SYN-ACK. A NACL inbound\n  allow on 443 ALSO requires an outbound allow on the ephemeral range\n  (1024-65535) for the return packet, because NACLs evaluate each\n  direction independently. Operators who \"fixed the SG and still\n  cannot connect\" usually have a NACL denying the return path.\n- **SG references (`sg-xxx`) only work within the same VPC or a peered\n  VPC.** A SG rule referencing `sg-xxx` from an unrelated VPC is\n  silently ignored — the rule appears valid in the console but never\n  matches traffic. Use CIDR blocks or a referenced SG in the peered\n  VPC (with peering in the route table).\n- **ESCALATE for AWS-side incidents.** AZ-wide degradation, region-\n  wide service events, and underlying host failures are not customer-\n  fixable — escalate to AWS Support and surface the event ARN.\n\n## Mindset\n\nMindset detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for the incident-framing model.\n\n## Philosophy\n\nThe four senior-engineer behaviours (OSI ordering, SG stateful vs NACL stateless, overlapping-CIDR silent failure, SG-reference scope) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand for the reasoning behind each probe-order rule.\n\n## Quick reference — symptom triage table\n\n| Symptom phrase \u002F error | Most likely layer | First probe |\n|---|---|---|\n| `Connection timed out`, `Operation timed out`, SYN no SYN-ACK | ROUTE_TABLE_MISSING \u002F ROUTE_TABLE_WRONG_TARGET \u002F ROUTE_OVERLAPPING_CIDR \u002F SG_INBOUND \u002F NACL_STATELESS \u002F PEERING_INACTIVE \u002F TGW_ROUTE_PROPAGATION | `describe-route-tables` + `describe-security-groups` + `describe-network-acls` for the source subnet |\n| `Connection refused`, `ECONNREFUSED`, TCP RST after SYN | Destination port closed (instance-level — outside this skill's VPC scope) | Confirm destination instance is running and listener is bound |\n| `Name or service not known`, `NXDOMAIN`, `server can't find` | DNS_RESOLUTION \u002F DNS_PHZ_ASSOCIATION | `dig`\u002F`nslookup` from source; `list-hosted-zones-by-vpc`; VPC DNS resolution\u002Fsupport settings |\n| HTTP 403 \u002F AccessDenied from an AWS service via VPC endpoint | ENDPOINT_POLICY | `describe-vpc-endpoints` (Policy, State) |\n| Cross-VPC success on IP but failure on hostname | PEERING_DNS_RESOLUTION | VPC peering `AllowDnsResolutionFromRemoteVpcDomainName` flag |\n| VPC peering Active but traffic times out | ROUTE_OVERLAPPING_CIDR \u002F PEERING_SG_REFERENCE \u002F route table missing pcx route | Compare VPC CIDRs; `describe-route-tables` for pcx route; `describe-security-groups` for SG reference scope |\n| TGW attachment Active but traffic times out | TGW_ROUTE_PROPAGATION \u002F TGW_ASSOCIATION_MISSING | `describe-transit-gateway-route-tables` for propagation; `describe-transit-gateway-attachments` for association |\n| PrivateLink endpoint accepted but service unreachable | PRIVATELINK_ENDPOINT_SERVICE \u002F PRIVATELINK_SG | `describe-vpc-endpoints` (ServiceName, State); NLB and endpoint SG allow |\n| Application reaches TCP layer but auth\u002FSSL fails | APP_AUTH | Application logs; SSL\u002FTLS handshake details |\n| None of the above, region-wide event | ESCALATE | `aws health describe-events` + AWS Service Health Dashboard |\n\n## Pre-flight: source \u002F destination context and AWS Health gate\n\nBefore running symptom-specific probes, gather the canonical source and\ndestination context and short-circuit on AWS-side events that mimic\nconnectivity failures. Misclassifying these produces hours of network\ndebugging for a problem that is not a network problem.\n\n### Pre-flight commands\n\nSource\u002Fdestination context + AWS Health pre-flight command listing moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand before the first probe.\n\n### Pre-flight short-circuits\n\n| Signal | Effect |\n|---|---|\n| AWS Health open event for `AWS_EC2`, `AWS_VPC`, `AWS_DIRECTCONNECT` in the region | Likely AWS-side degradation. Surface in REMEDIATION; consider ESCALATE. |\n| Source instance `State: stopped` or `terminated` | Not a connectivity issue; the source is gone. |\n| Destination instance `State: stopped` or `terminated` | Not a connectivity issue; the destination is gone. Surface as ROOT_CAUSE_FOUND with `LAYER: APP_AUTH` (no listener) or `UNKNOWN`. |\n| Destination AZ has a known AWS Health event | Traffic to that AZ may fail while cross-AZ paths succeed. Note the AZ-specific signal. |\n| Source subnet `AvailableIpAddressCount: 0` | Subnet is exhausted; new ENIs cannot be created. Symptom is on ENI-creating workloads (Lambda VPC attach, ECS tasks). |\n\nIf the input is malformed (missing source or destination identifier,\nabsent symptom, no port\u002Fprotocol for reachability diagnosis), emit:\n\nThe NEED_MORE_INFO malformed-input output template moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nEmit it whenever required context is missing.\n\n## Process — Diagnostic decision tree (apply in symptom order)\n\nThe diagnostic tree is symptom-driven. Pick the entry point based on the\nobserved symptom, then walk the layer-specific probes in OSI order. Each\nlayer ends with either a positive root-cause confirmation (failing probe\nthat matches the symptom) or a pass that moves to the next layer. **Never\nemit ROOT_CAUSE_FOUND without a failing probe that matches the symptom.**\n\n### Step 0: Non-obvious behaviours that change diagnosis\n\nThe full Step-0 gotcha catalog (cross-VPC SG references, NACL statelessness, overlapping CIDRs, peering non-transitivity, DNS flags, PHZ association, endpoint policy vs IAM, TGW propagation, PrivateLink handshake, nc ground truth, Reachability Analyzer, Flow Logs, Lambda\u002FIGW asymmetry, cross-AZ cost) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand before diagnosing any non-trivial symptom.\n\n### Step 1: Symptom entry — pick the diagnostic branch\n\nMap the symptom to a branch and jump to that branch's section. If the\nsymptom matches none of the categories, route to Step 9 (ESCALATE or\nNEED_MORE_INFO).\n\n| Symptom | Branch |\n|---|---|\n| `Connection timed out`, SYN no SYN-ACK, `nc -vz` hangs | Step 2 — Timeout (OSI walk) |\n| `Name or service not known`, `NXDOMAIN`, hostname does not resolve | Step 3 — DNS |\n| HTTP 403 from AWS service via VPC endpoint | Step 4 — VPC endpoint policy |\n| Cross-VPC via peering: peering Active but traffic times out | Step 5 — VPC peering |\n| Cross-VPC via TGW: attachments Active but traffic times out | Step 6 — Transit Gateway |\n| Cross-VPC via PrivateLink: endpoint accepted but service unreachable | Step 7 — PrivateLink |\n| TCP reaches but TLS \u002F auth fails | Step 8 — Application |\n| None of the above | Step 9 — Escalate \u002F NEED_MORE_INFO |\n\n### Step 2: Connection timeout — OSI-aligned diagnostic tree\n\nSub-steps 2a-2j — the full OSI walk (source\u002Fdest context, route tables both sides, overlapping CIDRs, SG inbound\u002Foutbound + cross-VPC SG references, NACLs in both directions on both subnets, nc\u002Ftelnet probe, VPC Flow Logs, Reachability Analyzer) with every probe command and verdict condition moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when diagnosing a timeout symptom.\n\n### Step 3: DNS resolution failure\n\nDNS probes (resolver\u002FDHCP options, enableDnsSupport + enableDnsHostnames, Route 53 PHZ association, Resolver endpoints and rules) with DNS_RESOLUTION \u002F DNS_PHZ_ASSOCIATION verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when a hostname does not resolve.\n\n### Step 4: VPC endpoint policy\n\nEndpoint-policy probes (describe-vpc-endpoints policy read, endpoint bypass test) with ENDPOINT_POLICY verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand on AccessDenied that clears outside the VPC.\n\n### Step 5: VPC peering — Active but traffic times out\n\nPeering probes (status table, both-side pcx routes, overlapping CIDRs, cross-VPC SG references, remote DNS resolution flag) with PEERING_* verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when peering is Active but traffic times out.\n\n### Step 6: Transit Gateway — attachments Active but traffic times out\n\nTGW probes (attachment state, TGW route-table association vs propagation, both-side tgw routes) with TGW_ASSOCIATION_MISSING \u002F TGW_ROUTE_PROPAGATION verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when attachments are Active but traffic times out.\n\n### Step 7: PrivateLink — endpoint accepted but service unreachable\n\nPrivateLink probes (endpoint state, endpoint-SG ENI, provider endpoint service + NLB health, private DNS) with PRIVATELINK_* verdict conditions moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when an endpoint is accepted but the service is unreachable.\n\n### Step 8: Application layer — TLS \u002F auth\n\nAPP_AUTH routing guidance (TLS\u002Fauth symptoms route to the application-specific troubleshooters) moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when TCP succeeds but TLS or auth fails.\n\n### Step 9: Escalate or NEED_MORE_INFO\n\nESCALATE \u002F NEED_MORE_INFO exit rules (AWS-side incidents, missing operator input) moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\nLoad on demand when no layer produced a positive match.\n\n## Output format\n\n```text\nTARGET: \u003Csource → destination pair>\nVERDICT: ROOT_CAUSE_FOUND | NEED_MORE_INFO | ESCALATE\nREASON: \u003C1-2 sentences naming the failed layer and the failing probe>\nLAYER: \u003CROUTE_TABLE_MISSING | ROUTE_TABLE_WRONG_TARGET |\n        ROUTE_OVERLAPPING_CIDR | SG_INBOUND | SG_OUTBOUND |\n        SG_REFERENCE_CROSS_VPC | NACL_STATELESS | DNS_RESOLUTION |\n        DNS_PHZ_ASSOCIATION | ENDPOINT_POLICY | PEERING_INACTIVE |\n        PEERING_DNS_RESOLUTION | PEERING_SG_REFERENCE |\n        TGW_ROUTE_PROPAGATION | TGW_ASSOCIATION_MISSING |\n        PRIVATELINK_ENDPOINT_SERVICE | PRIVATELINK_SG | APP_AUTH |\n        UNKNOWN>\nEVIDENCE:\n  - \u003Cobserved symptom — error string or behaviour>\n  - \u003Cfailing probe — command and its output that confirms the cause>\n  - \u003Cpassing probes — layers ruled out>\nREMEDIATION:\n  1. \u003Cspecific action with CLI command>\n  2. \u003Cverification command after the fix>\nCONFIRM: Before executing any state-changing CLI, emit and await operator\n  approval: \"CONFIRM: About to \u003Caction> on \u003Cid> in \u003Cregion>. Proceed?\n  (yes\u002Fno)\"\n```\n\n### Worked example — SG inbound missing rule\n\n```text\nTARGET: i-app (10.0.1.10, subnet-aaa, vpc-source) → i-db\n  (172.16.1.10, subnet-bbb, vpc-target) on tcp\u002F5432\nVERDICT: ROOT_CAUSE_FOUND\nREASON: The destination SG sg-db has no inbound rule matching the\n  source's CIDR 10.0.1.0\u002F24 on port 5432 — the SYN is dropped at the\n  instance's security group (Step 2e).\nLAYER: SG_INBOUND\nEVIDENCE:\n  - Symptom: application on i-app (10.0.1.10) reports \"Operation\n    timed out\" when connecting to i-db (172.16.1.10:5432). nc -vz\n    hangs.\n  - Probe: aws ec2 describe-security-groups --group-ids sg-db returns\n    inbound rules allowing 172.16.0.0\u002F16 (local VPC) on 5432. No\n    rule matches 10.0.1.0\u002F24 (source VPC CIDR).\n  - Passing: route table for subnet-aaa has a pcx-aaa route to\n    172.16.0.0\u002F16; route table for subnet-bbb has a pcx-aaa route\n    back to 10.0.0.0\u002F16; peering pcx-aaa is Active; VPC CIDRs do not\n    overlap; NACL on both subnets is the default (allow all).\nREMEDIATION:\n  1. Add an inbound rule to sg-db allowing the source CIDR on tcp\u002F5432:\n     aws ec2 authorize-security-group-ingress --group-id sg-db\n       --protocol tcp --port 5432 --cidr 10.0.1.0\u002F24 --profile \u003Cp>\n  2. Verify from the source: nc -vz 172.16.1.10 5432 (should succeed\n     within 1s).\nCONFIRM: Before authorizing the SG ingress, emit and await:\n  \"CONFIRM: About to authorize-security-group-ingress on sg-db in\n   us-east-1 for 10.0.1.0\u002F24 on tcp\u002F5432. Proceed? (yes\u002Fno)\"\n```\n\n### Worked example — NACL missing ephemeral outbound\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a NACL_STATELESS verdict.\n\n### Worked example — overlapping CIDR (silent peering failure)\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a ROUTE_OVERLAPPING_CIDR verdict.\n\n### Worked example — VPC endpoint policy blocking S3 PutObject\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting an ENDPOINT_POLICY verdict.\n\n## STRICT output contract\n\nThis contract is mandatory. The Output format template above is the\nauthoritative structure; the rules below disambiguate the failure\nmodes that score D8=13 on this skill. Violating any rule is a\nmisdiagnosis.\n\n### Required output structure\n\nEvery diagnosis MUST emit this exact block, with all fields populated\n(no empty fields, no omitted sections, no reordering):\n\nThe literal block template is the one in ## Output format above; this annotated duplicate moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when the contract wording is unclear.\n\nVerdict-specific rules:\n- `ROOT_CAUSE_FOUND` → LAYER is one of the 18 enum values; EVIDENCE\n  includes a failing probe whose output positively confirms the cause\n  (not a process of elimination); REMEDIATION is actionable CLI.\n- `NEED_MORE_INFO` → LAYER is `UNKNOWN` or the best candidate; EVIDENCE\n  lists the missing input (source ID, destination ID, port, protocol,\n  region) and the next probe to run once it is supplied.\n- `ESCALATE` → LAYER is the suspected AWS-side category; REASON cites\n  the AWS Health event ARN or the carrier\u002Fout-of-band signal.\n\n### FORBIDDEN output patterns\n\n1. NEVER skip the NACL check — NACLs are stateless, both inbound AND\n   outbound rules needed for ephemeral ports 1024-65535. A diagnosis\n   that omits `describe-network-acls` for both source and destination\n   subnets is incomplete, even if a SG rule matches.\n2. NEVER assume a Security Group reference works cross-VPC — SG\n   references (`sg-xxx`) only resolve within the same VPC or a peered\n   VPC with peering in the route table, not via Transit Gateway. A\n   cross-VPC SG reference via TGW is silently ignored.\n3. NEVER declare ROOT_CAUSE_FOUND without a failing probe that matches\n   the symptom. \"It must be the SG\" by process of elimination is\n   forbidden — cite the `describe-security-groups` or `nc -vz` output\n   that positively confirms the drop.\n4. NEVER skip the OSI order for timeout symptoms. The probe order is\n   DNS (L7) → routing (L3) → SG (L4) → NACL (L4) → cross-VPC plumbing\n   → port reachability → application. A diagnosis that checks the SG\n   before the route table and concludes \"SG is fine\" missed that the\n   SYN never reached the SG evaluation.\n5. NEVER treat VPC peering as transitive. Peering between A-B and B-C\n   does NOT allow A to reach C via B — transit requires Transit\n   Gateway. A diagnosis that suggests \"add a peering route through\n   VPC-B\" is wrong.\n6. NEVER assume overlapping VPC CIDRs will route via peering. They are\n   a silent failure: the `pcx-xxx` route appears in the table but\n   packets do not deliver. A diagnosis that lists peering Active +\n   route present as \"passing\" without comparing the two VPC CIDRs is\n   incomplete.\n7. NEVER assume the VPC endpoint policy matches the IAM policy. The\n   endpoint policy is an independent layer that can deny actions IAM\n   allows. A diagnosis that clears IAM without bypassing the endpoint\n   to verify has not ruled out `ENDPOINT_POLICY`.\n\n### Perfect example output\n\nMoved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\nLoad on demand when formatting a complete ROOT_CAUSE_FOUND verdict.\n\n## Anti-Patterns — NEVER\n\n- NEVER declare ROOT_CAUSE_FOUND without a failing probe that matches\n  the symptom. A \"process of elimination\" diagnosis erodes operator\n  trust when the real cause is elsewhere.\n\n- NEVER skip the OSI order for timeout symptoms. If you check the\n  security group before the route table and conclude \"the SG is fine,\n  must be the destination,\" you missed that the route table has no\n  route for the destination CIDR — the SYN never reached the SG\n  evaluation.\n\n- NEVER evaluate NACLs in only one direction. NACLs are stateless;\n  the return SYN-ACK is a separate evaluation. The most common NACL\n  mistake is an inbound rule on 443 with no outbound rule on the\n  ephemeral range (1024-65535).\n\n- NEVER assume a security-group reference (`sg-xxx`) works cross-VPC.\n  Cross-VPC SG references are silently ignored unless the VPCs are\n  peered AND the peering is in the route table. Use CIDR blocks or a\n  referenced SG in the peered VPC.\n\n- NEVER treat VPC peering as transitive. Peering between A-B and B-C\n  does NOT allow A to reach C via B. Transit requires Transit Gateway.\n\n- NEVER assume overlapping VPC CIDRs will route via peering. They are\n  a silent failure — the route appears but packets do not deliver.\n\n- NEVER assume the VPC DNS settings are correct because \"DNS works\n  for some queries.\" Route 53 private hosted zones require BOTH\n  `enableDnsSupport` AND `enableDnsHostnames` to be true. Cross-\n  account PHZs require explicit association with the consumer VPC.\n\n- NEVER assume the VPC endpoint policy matches the IAM policy. The\n  endpoint policy is an independent layer; it can deny actions that\n  IAM allows. Bypass the endpoint to verify.\n\n- NEVER assume `PrivateDnsEnabled: true` on an interface endpoint is\n  cosmetic. Without it, the service's DNS name resolves to the public\n  IP and traffic routes over the internet instead of the endpoint.\n\n- NEVER conclude \"the network is flaky\" without running `nc -vz` or\n  equivalent from the source host at least three times. Intermittent\n  packet loss is rare in VPC; intermittent failures are usually\n  stateful (DNS cache, connection pool, failover) not packet-loss.\n\n- NEVER assume Transit Gateway route propagation is automatic. Each\n  attachment must be associated with a TGW route table AND propagate\n  its routes. Association alone does not propagate.\n\n- NEVER assume PrivateLink endpoint service availability implies NLB\n  health. The endpoint can be `available` while the NLB has no\n  healthy targets in the consumer's AZ. Always check NLB target\n  health.\n\n- NEVER recommend modifying a NACL to deny specific traffic as a\n  security fix without checking the existing rule order. NACLs\n  evaluate lowest-to-highest rule number; first match wins. A new\n  deny at rule 200 is shadowed by an existing allow at rule 100.\n\n- NEVER recommend expanding a CIDR to `0.0.0.0\u002F0` to \"fix\" a SG\n  issue. This exposes the listener to the entire internet. Use the\n  narrowest scope that covers the legitimate source.\n\n- NEVER rely on Reachability Analyzer as the sole evidence. It models\n  the configured state; it does not test the live packet. Pair it\n  with `nc -vz` from the source host.\n\n- NEVER skip VPC Flow Logs when diagnosing intermittent issues. Flow\n  Logs with `action: REJECT` confirm the packet was dropped by SG or\n  NACL; `action: ACCEPT` confirms the packet reached the ENI.\n\n## Pre-flight safety checks (run before any state-changing CLI)\n\nPre-flight safety checks (confirmation gate, read-only-first, SG\u002FNACL\u002Froute\u002Fpeering\u002FTGW\u002Fendpoint blast-radius rules, bulk batch limit) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand before any state-changing CLI.\n\n## Remediation guidance\n\nPer-LAYER remediation commands for all 17 layer values (create-route, replace-route, SG ingress\u002Fegress, NACL ephemeral entries, DNS attributes, PHZ association, endpoint policy, peering accept\u002FDNS options, TGW propagation\u002Fassociation, PrivateLink NLB\u002FSG) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when writing the REMEDIATION block.\n\n## Deep reference: VPC connectivity layer model\n\nLayer model, SG-vs-NACL comparison, VPC peering vs Transit Gateway, and VPC endpoint type tables moved verbatim to [references\u002Fconnectivity-layer-reference.md](references\u002Fconnectivity-layer-reference.md).\nLoad on demand for the comparison tables.\n\n## Recent AWS features (2024-2026)\n\nMoved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand to check what changed in the last 24 months.\n\n## References (load on demand)\n\n- [Diagnostic commands](references\u002Fdiagnostic-commands.md) — pre-flight context commands and the full Step 2-9 diagnostic walk with every probe command and verdict condition\n- [Worked examples](references\u002Fworked-examples.md) — secondary worked examples (NACL ephemeral outbound, overlapping CIDR, endpoint policy), the NEED_MORE_INFO re-prompt template, and annotated output-contract templates\n- [Error handling](references\u002Ferror-handling.md) — pre-flight safety checks before state-changing CLIs and per-LAYER remediation guidance with fix and verify commands\n- [Advanced patterns](references\u002Fadvanced-patterns.md) — mindset, philosophy, Step-0 non-obvious behaviours, and recent AWS features (2024-2026)\n- [Connectivity layer reference](references\u002Fconnectivity-layer-reference.md) — ports and protocol semantics, SG\u002FNACL evaluation, peering\u002FTGW\u002FPrivateLink specifics, plus the moved layer-model comparison tables\n\n## Domain\n\nAWS CloudOps \u002F VPC Networking, Routing, Security Groups, NACLs, DNS,\nCross-VPC Connectivity (Peering, Transit Gateway, PrivateLink), and\nPacket-Path Diagnostics.\n\n## AWS documentation\n\n- **Amazon VPC User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002F\n- **VPC route tables** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002FVPC_Route_Tables.html\n- **Security groups** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002FVPC_SecurityGroups.html\n- **Network ACLs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fvpc-network-acls.html\n- **VPC peering** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fpeering\u002FWelcome.html\n- **Transit Gateway** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Ftgw\u002FWhat_is_TGW.html\n- **AWS PrivateLink** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fprivatelink\u002Fconcepts.html\n- **VPC endpoints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fvpc-endpoints.html\n- **Reachability Analyzer** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Freachability\u002FWhat-is-Reachability-Analyzer.html\n- **VPC Flow Logs** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fvpc\u002Flatest\u002Fuserguide\u002Fflow-logs.html\n- **Route 53 Resolver** — https:\u002F\u002Fdocs.aws.amazon.com\u002FRoute53\u002Flatest\u002FDeveloperGuide\u002Fresolver.html\n- **AWS Health** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fhealth\u002Flatest\u002Fug\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":44},{"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,"requires_llm":37,"verdict_shape":38,"when_not_to_use":39,"lifecycle_status":40,"invocation_schema":41,"supports_pipeline":37,"invocation_example":42,"activation_triggers":43},"vpc, networking, troubleshooting, routing, security-groups, nacl, dns, vpc-peering, transit-gateway, privatelink","2","Jacky Chan — AWS Community Builder","aws-cloudops","Networking","0.1.0","VPC, connectivity, routing, route table, security group, NACL, network ACL, ephemeral port, DNS, Route 53, private hosted zone, resolver, VPC endpoint, endpoint policy, VPC peering, Transit Gateway, TGW, PrivateLink, Reachability Analyzer, VPC Flow Logs, overlapping CIDR, troubleshooting","troubleshoot","high","false","capability","Diagnosing a VPC network connectivity issue (cannot reach an endpoint, intermittent connectivity, port blocked, DNS resolution failure, cross-VPC traffic failure, VPC endpoint policy block, peering asymmetry, TGW route propagation gap), walking a symptom to the failed layer with verify and fix commands, validating why an EC2 instance \u002F Lambda \u002F ECS task \u002F on-prem host cannot reach a destination, or triaging a \"the network is down\" page where the root cause may be routing, security groups, NACLs, DNS, endpoint policy, or cross-VPC plumbing — not necessarily the destination service itself.","true","ROOT_CAUSE_FOUND | NEED_MORE_INFO | ESCALATE","Internet egress cost audits (use vpc-flow-logs-auditor or cost- anomaly detectors), RDS-specific auth and TLS issues (use rds- connectivity-troubleshooter which specialises the L7 layer for database engines), IAM execution-role diagnostics (use iam- permission-troubleshooter), or Direct Connect \u002F Site-to-Site VPN hardware configuration (use the carrier \u002F device-side tooling). This skill diagnoses packet-path connectivity; it does not audit configuration posture or replace dedicated per-service troubleshooters.","active","Input: either (a) a symptom description (error message, observed behaviour, \"host cannot reach destination on port X\", intermittent vs persistent pattern), optionally paired with the source and destination context (instance\u002Fsubnet\u002FVPC IDs, ports, protocol), OR (b) a source-destination pair plus caller context (region, AZ, observed error) for live-account diagnosis. Output: a deterministic TARGET\u002FVERDICT\u002FREASON\u002FLAYER\u002FEVIDENCE\u002FREMEDIATION block where VERDICT ∈ {ROOT_CAUSE_FOUND, NEED_MORE_INFO, ESCALATE} and LAYER ∈ {ROUTE_TABLE_MISSING, ROUTE_TABLE_WRONG_TARGET, ROUTE_OVERLAPPING_CIDR, SG_INBOUND, SG_OUTBOUND, SG_REFERENCE_CROSS_VPC, NACL_STATELESS, DNS_RESOLUTION, DNS_PHZ_ASSOCIATION, ENDPOINT_POLICY, PEERING_INACTIVE, PEERING_DNS_RESOLUTION, PEERING_SG_REFERENCE, TGW_ROUTE_PROPAGATION, TGW_ASSOCIATION_MISSING, PRIVATELINK_ENDPOINT_SERVICE, PRIVATELINK_SG, APP_AUTH, UNKNOWN}.","# Minimal valid input (offline symptom classification):\nSymptom: \"application on EC2 instance i-app (subnet subnet-aaa,\nSG sg-app, AZ us-east-1a, VPC vpc-source) cannot reach EC2\ninstance i-db (subnet subnet-bbb, SG sg-db, AZ us-east-1b, VPC\nvpc-target) on tcp\u002F5432. nc -vz returns 'Connection timed out'.\nThe two VPCs are peered (pcx-aaa) and the peering status is\nActive.\"\nSource: i-app, subnet-aaa (CIDR 10.0.1.0\u002F24 in vpc-source\n  10.0.0.0\u002F16), SG sg-app\nDestination: i-db, subnet-bbb (CIDR 172.16.1.0\u002F24 in vpc-target\n  172.16.0.0\u002F16), SG sg-db\nPath: same region (us-east-1), VPC peering pcx-aaa (Active)\nObserved error: nc -vz 172.16.1.10 5432 → \"Connection timed out\"","VPC connection timeout, cannot reach EC2 instance, EC2 port unreachable, Lambda VPC timeout, ECS task cannot reach, security group blocking traffic, NACL dropping packets, route table missing, VPC peering not working, Transit Gateway routing, TGW routes not propagating, VPC endpoint policy blocked, DNS not resolving in VPC, Route 53 private hosted zone, cross-VPC connectivity, PrivateLink endpoint service, Reachability Analyzer, VPC Flow Logs analysis, overlapping CIDR peering, troubleshoot VPC connectivity","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). Offline symptom classification works from pasted error messages and topology descriptions. Live-account diagnosis uses aws ec2 describe-route-tables, aws ec2 describe-security-groups, aws ec2 describe-network-acls, aws ec2 describe-vpc-endpoints, aws ec2 describe-vpc-peering-connections, aws ec2 describe-transit- gateway-attachments, aws ec2 describe-transit-gateway-route-tables, aws ec2...","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fvpc-connectivity-troubleshooter",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill vpc-connectivity-troubleshooter",{"tool":59,"command":60},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill vpc-connectivity-troubleshooter",{"tool":62,"command":63},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill vpc-connectivity-troubleshooter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002FSKILL.md",true,[67,73,77,81,85,89,93,97,101,105,109,113,117,121,125,129,133,137,141,145],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",10216,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Feval\u002Ftest-cases.yaml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"evals\u002Fbaselines\u002Fnacl-missing-ephemeral-outbound.md",530,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fbaselines\u002Fnacl-missing-ephemeral-outbound.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"evals\u002Fbaselines\u002Fphz-cross-account-no-association.md",575,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fbaselines\u002Fphz-cross-account-no-association.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fbaselines\u002Froute-overlapping-cidr-silent.md",449,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fbaselines\u002Froute-overlapping-cidr-silent.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbaselines\u002Fsg-inbound-dead-cross-vpc-ref.md",706,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fbaselines\u002Fsg-inbound-dead-cross-vpc-ref.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002Fbaselines\u002Ftgw-route-propagation-missing.md",526,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fbaselines\u002Ftgw-route-propagation-missing.md",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"evals\u002Feval_config.yaml",2029,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Feval_config.yaml",{"path":98,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":99,"sourceHtmlUrl":100},"evals\u002Fevals.json",4946,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fevals.json",{"path":102,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":103,"sourceHtmlUrl":104},"evals\u002Fprompts\u002Fnacl-missing-ephemeral-outbound.md",1411,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fprompts\u002Fnacl-missing-ephemeral-outbound.md",{"path":106,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":107,"sourceHtmlUrl":108},"evals\u002Fprompts\u002Fphz-cross-account-no-association.md",1551,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fprompts\u002Fphz-cross-account-no-association.md",{"path":110,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":111,"sourceHtmlUrl":112},"evals\u002Fprompts\u002Froute-overlapping-cidr-silent.md",1279,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fprompts\u002Froute-overlapping-cidr-silent.md",{"path":114,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":115,"sourceHtmlUrl":116},"evals\u002Fprompts\u002Fsg-inbound-dead-cross-vpc-ref.md",1287,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fprompts\u002Fsg-inbound-dead-cross-vpc-ref.md",{"path":118,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":119,"sourceHtmlUrl":120},"evals\u002Fprompts\u002Ftgw-route-propagation-missing.md",1672,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fevals\u002Fprompts\u002Ftgw-route-propagation-missing.md",{"path":122,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":123,"sourceHtmlUrl":124},"examples\u002FREADME.md",8127,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fexamples\u002FREADME.md",{"path":126,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fadvanced-patterns.md",10299,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Freferences\u002Fadvanced-patterns.md",{"path":130,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fconnectivity-layer-reference.md",16722,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Freferences\u002Fconnectivity-layer-reference.md",{"path":134,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fdiagnostic-commands.md",21293,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Freferences\u002Fdiagnostic-commands.md",{"path":138,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Ferror-handling.md",6168,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Freferences\u002Ferror-handling.md",{"path":142,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Fworked-examples.md",7693,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Freferences\u002Fworked-examples.md",{"path":146,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":147,"sourceHtmlUrl":148},"skill.usf.yaml",4592,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvpc-connectivity-troubleshooter\u002Fskill.usf.yaml",[150,157,164,171,178,185],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"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":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"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":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"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":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"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":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"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":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"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",[],[]]