[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-aws-vpc-dns-investigation":3,"mdc--xwnyul-key":52,"related-repo-aws-aws-vpc-dns-investigation":822,"related-org-aws-aws-vpc-dns-investigation":925},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":47,"sourceUrl":50,"mdContent":51},"aws-vpc-dns-investigation","investigate VPC DNS resolution issues","Use this skill when a name is not resolving as expected inside a VPC, or before applying a DNS control-plane change. Activate on symptoms such as NXDOMAIN or SERVFAIL from an EC2 instance, a hostname resolving to a public address when a private endpoint was expected, an AWS service endpoint that stopped resolving after a VPC endpoint or Route 53 change, an application reaching the wrong IP, resolution that works from one instance but not another, IPv6 or dualstack resolution differences, a suspected on-premises forwarding or hybrid DNS problem, or a request to check whether enabling private DNS, adding a Resolver rule, associating a private hosted zone, attaching DNS Firewall, or associating a Route 53 Profile would break anything. It drives the aws-vpc-dns-diagnostics MCP server to observe live resolution from inside the subnet and to simulate a proposed change before it is applied.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"aws","AWS (Amazon)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Faws.png",[12,16,19,21],{"name":13,"slug":14,"type":15},"Networking","networking","tag",{"name":17,"slug":18,"type":15},"DNS","dns",{"name":20,"slug":8,"type":15},"AWS",{"name":22,"slug":23,"type":15},"Debugging","debugging",35,"https:\u002F\u002Fgithub.com\u002Faws\u002Ftools-for-devops-agent","2026-08-20T03:53:46.027593",null,30,[30,31,32,33,34,8,35,36,37,38,39,40,41,42,43,44,45,46],"agent-skills","agentic-ai","agents","ai-agents","aiops","aws-devops-agent","cloud-operations","custom-agents","devops","devops-agent-skills","frontier-agent","incident-response","operational-excellence","root-cause-analysis","skills","sre","support",{"repoUrl":25,"stars":24,"forks":28,"topics":48,"description":49},[30,31,32,33,34,8,35,36,37,38,39,40,41,42,43,44,45,46],"Open-source tools for AWS DevOps Agent - extend DevOps Agent with ready-to-use skills, custom agents, and other tools, for incident response, root cause analysis, and operational troubleshooting","https:\u002F\u002Fgithub.com\u002Faws\u002Ftools-for-devops-agent\u002Ftree\u002FHEAD\u002Fskills\u002Faws-vpc-dns-investigation","---\nname: aws-vpc-dns-investigation\ndescription: Use this skill when a name is not resolving as expected inside a VPC, or before applying a DNS control-plane change. Activate on symptoms such as NXDOMAIN or SERVFAIL from an EC2 instance, a hostname resolving to a public address when a private endpoint was expected, an AWS service endpoint that stopped resolving after a VPC endpoint or Route 53 change, an application reaching the wrong IP, resolution that works from one instance but not another, IPv6 or dualstack resolution differences, a suspected on-premises forwarding or hybrid DNS problem, or a request to check whether enabling private DNS, adding a Resolver rule, associating a private hosted zone, attaching DNS Firewall, or associating a Route 53 Profile would break anything. It drives the aws-vpc-dns-diagnostics MCP server to observe live resolution from inside the subnet and to simulate a proposed change before it is applied.\nmetadata:\n  author: ddericco\n  version: \"1.0.0\"\n  aws-devops-agent-skills.agent-types: \"Chat tasks, Incident RCA\"\n  aws-devops-agent-skills.aws-services: \"Amazon VPC, Amazon Route 53, Amazon EC2, AWS Systems Manager\"\n  aws-devops-agent-skills.technical-domains: \"Networking\"\n---\n\n# Investigate VPC DNS Resolution\n\nUse the tools on the connected `aws-vpc-dns-diagnostics` MCP server.\n\n## Step 1: Classify the request as Mode A or Mode B\n\nBefore calling any tool, determine which mode applies:\n\n- **Mode A (live diagnosis):** The operator reports a resolution symptom from a\n  running instance. They provide an instance ID (or you can identify one). The\n  goal is to observe what actually resolves and compare resolvers.\n- **Mode B (pre-change validation):** The operator asks whether a proposed DNS\n  change is safe. They provide account, region, VPC, and a change descriptor.\n  No instance is required.\n\nIf the request is ambiguous, ask the operator to clarify. Do not default to\nMode A when the input lacks an instance ID, and do not default to Mode B when\nthe operator describes a live symptom.\n\n## Step 2: Load safety rules\n\nRegardless of mode, call `get_sop` with slug `A-critical-safety-rules` and\nfollow every rule it contains. These are non-negotiable constraints on how you\ninterpret results, handle opaque constructs, and report findings.\n\n---\n\n## Mode A route: live diagnosis\n\n### Required inputs\n\naccount_id, region, instance_id, and the failing DNS name.\n\n### Tool sequence (in order)\n\n1. `dns_probe_context` — establishes VPC-attribute preconditions: enableDnsSupport,\n   enableDnsHostnames, address family, DHCP option set. A resolution result means\n   nothing until you know whether the VPC resolver is answering.\n2. `dns_probe_compare` — runs the allowlisted probe set inside the instance via\n   SSM. Returns each resolver's answer and the resolver's own identity from\n   `hostname.bind`. The VPC DHCP resolver is auto-added for comparison.\n3. `get_sop` — load the pattern runbook matching the observed signature\n   (see trap-to-SOP mapping below).\n\n### Interpretation rules\n\n- If `enableDnsSupport` is false: load `A-resolver-disabled-precondition`. The\n  VPC resolver is intentionally dark and every probe failure follows from that.\n- Compare the instance's `\u002Fetc\u002Fresolv.conf` (from the probe output) against the\n  DHCP option set. A mismatch means the instance is not using the VPC-intended\n  resolver.\n- Judge answers by name category (load `A-name-category-classification`), not by\n  whether resolvers agree. Two resolvers returning the same wrong answer is still\n  a failure.\n\n### Mode A trap-to-SOP mapping\n\n| Observed signature | SOP slug |\n| --- | --- |\n| Custom resolver answers differently from VPC .2 | `A-custom-resolver-divergence` |\n| FORWARD rule and PHZ both match the name | `A-forward-vs-phz-precedence-collision` |\n| A record works, AAAA fails (or vice versa) | `A-address-family-divergence` |\n| enableDnsSupport is false | `A-resolver-disabled-precondition` |\n| General live comparison procedure | `A-mode-a-live-resolver-comparison` |\n\n### Reporting format for Mode A\n\nLabel every finding as **Observed** (ground truth from the probe). State which\nresolver answered and what it returned. When Mode A and Mode B produce different\nconclusions for the same name, **Mode A wins** because it is ground truth from\ninside the subnet.\n\n---\n\n## Mode B route: pre-change validation\n\n### Required inputs\n\naccount_id, region, vpc_id, and a change descriptor (structured dict with `type`\nand type-specific fields). No instance required.\n\n### Tool sequence (in order)\n\n1. `dns_simulate_effective_config` — returns the VPC's effective DNS config: the\n   union of directly attached resources and anything inherited through an\n   associated Route 53 Profile, each construct tagged by source.\n2. `dns_simulate_change` — applies the proposed change symbolically and returns a\n   per-name impact report (before\u002Fafter, delta, traps, severity, volume).\n3. `get_sop` — load runbooks for any traps reported in the impact table\n   (see trap-to-SOP mapping below).\n\n### Interpretation rules\n\n- Never recommend applying a change without simulating it first. A broad FORWARD\n  rule, enabling private DNS on an interface endpoint, or a Profile association\n  can silently redirect names that currently resolve correctly.\n- The candidate set is limited to API-derived names (PHZ records, rule domains,\n  VPCE apexes, Firewall domain lists) or operator-supplied names. It is not\n  exhaustive. State the coverage boundary.\n- If the operator supplies `volumes` (from Resolver Query Logs), names are ranked\n  by traffic. This is enrichment; absence does not invalidate the simulation.\n\n### Mode B trap-to-SOP mapping\n\n| Trap label in impact report | SOP slug |\n| --- | --- |\n| VPCE-shadow-NXDOMAIN | `B-vpce-shadow-nxdomain` |\n| broad-FORWARD-sweep | `B-broad-forward-sweep` |\n| flag-AND-mismatch | `B-flag-and-mismatch` |\n| DNS-Firewall-block | `B-dns-firewall-block` |\n| profile-union-shift | `B-profile-propagation-timing` |\n| General pre-change procedure | `B-mode-b-pre-change-validation` |\n\n### Reporting format for Mode B\n\nLabel every finding as **Predicted** (symbolic, not ground truth). State the\ncandidate-set size, its source (API-derived or operator-supplied), and that names\noutside this set were not evaluated. Include the propagation timing caveat for\nProfile changes.\n\n---\n\n## Cross-account opacity\n\nCall `get_sop` with slug `C-cross-account-opaque-constructs` when the effective\nconfig or impact report contains opaque markers. Cross-account constructs shared\nvia RAM or a Route 53 Profile may be enumerable but their contents are not\nreadable from the consumer account. Report them as \"present but unknown content\"\nrather than treating them as absent or inferring past them.\n\n## Limitations\n\nCall `get_sop` with slug `C-limitations-and-boundaries` and state the relevant\nboundaries to the operator. Key constraints:\n\n- All tools are read-only. Do not modify, delete, or create DNS resources.\n- Mode A requires SSM reachability (ssm, ssmmessages, ec2messages VPC endpoints\n  and an instance role with AmazonSSMManagedInstanceCore).\n- Mode B candidate sets are not exhaustive. The \"no impacts\" conclusion applies\n  only within the tested set.\n- Opaque constructs cannot be resolved from this account.\n- Resolver Query Log ingestion is not implemented; volumes must be supplied by\n  the operator.\n\n## Final response requirements\n\nEvery response produced by this skill must include:\n\n1. Each finding labelled **Observed** (Mode A) or **Predicted** (Mode B).\n2. When both modes were used, state \"Mode A wins\" for any conflict.\n3. The candidate-set coverage: how many names, what source, what was not tested.\n4. Any opaque constructs and their impact on the conclusion.\n5. Recommended next steps or the specific change to apply (never apply it).\n\n## Prerequisites\n\nRequires the aws-vpc-dns-diagnostics MCP server registered in the Agent Space\nwith its tools allowlisted. The server is at `mcp\u002Faws-vpc-dns-diagnostics-mcp\u002F`.\nIf the server is not registered or SSM is unreachable, report that as the blocker\nrather than guessing at the resolution path.\n",{"data":53,"body":60},{"name":4,"description":6,"metadata":54},{"author":55,"version":56,"aws-devops-agent-skills":57},"ddericco","1.0.0",{"agent-types":58,"aws-services":59,"technical-domains":13},"Chat tasks, Incident RCA","Amazon VPC, Amazon Route 53, Amazon EC2, AWS Systems Manager",{"type":61,"children":62},"root",[63,72,87,94,99,125,130,136,157,161,167,174,179,185,229,235,285,291,403,409,428,431,437,442,455,460,495,500,526,532,655,661,672,675,681,700,706,724,752,758,763,803,809],{"type":64,"tag":65,"props":66,"children":68},"element","h1",{"id":67},"investigate-vpc-dns-resolution",[69],{"type":70,"value":71},"text","Investigate VPC DNS Resolution",{"type":64,"tag":73,"props":74,"children":75},"p",{},[76,78,85],{"type":70,"value":77},"Use the tools on the connected ",{"type":64,"tag":79,"props":80,"children":82},"code",{"className":81},[],[83],{"type":70,"value":84},"aws-vpc-dns-diagnostics",{"type":70,"value":86}," MCP server.",{"type":64,"tag":88,"props":89,"children":91},"h2",{"id":90},"step-1-classify-the-request-as-mode-a-or-mode-b",[92],{"type":70,"value":93},"Step 1: Classify the request as Mode A or Mode B",{"type":64,"tag":73,"props":95,"children":96},{},[97],{"type":70,"value":98},"Before calling any tool, determine which mode applies:",{"type":64,"tag":100,"props":101,"children":102},"ul",{},[103,115],{"type":64,"tag":104,"props":105,"children":106},"li",{},[107,113],{"type":64,"tag":108,"props":109,"children":110},"strong",{},[111],{"type":70,"value":112},"Mode A (live diagnosis):",{"type":70,"value":114}," The operator reports a resolution symptom from a\nrunning instance. They provide an instance ID (or you can identify one). The\ngoal is to observe what actually resolves and compare resolvers.",{"type":64,"tag":104,"props":116,"children":117},{},[118,123],{"type":64,"tag":108,"props":119,"children":120},{},[121],{"type":70,"value":122},"Mode B (pre-change validation):",{"type":70,"value":124}," The operator asks whether a proposed DNS\nchange is safe. They provide account, region, VPC, and a change descriptor.\nNo instance is required.",{"type":64,"tag":73,"props":126,"children":127},{},[128],{"type":70,"value":129},"If the request is ambiguous, ask the operator to clarify. Do not default to\nMode A when the input lacks an instance ID, and do not default to Mode B when\nthe operator describes a live symptom.",{"type":64,"tag":88,"props":131,"children":133},{"id":132},"step-2-load-safety-rules",[134],{"type":70,"value":135},"Step 2: Load safety rules",{"type":64,"tag":73,"props":137,"children":138},{},[139,141,147,149,155],{"type":70,"value":140},"Regardless of mode, call ",{"type":64,"tag":79,"props":142,"children":144},{"className":143},[],[145],{"type":70,"value":146},"get_sop",{"type":70,"value":148}," with slug ",{"type":64,"tag":79,"props":150,"children":152},{"className":151},[],[153],{"type":70,"value":154},"A-critical-safety-rules",{"type":70,"value":156}," and\nfollow every rule it contains. These are non-negotiable constraints on how you\ninterpret results, handle opaque constructs, and report findings.",{"type":64,"tag":158,"props":159,"children":160},"hr",{},[],{"type":64,"tag":88,"props":162,"children":164},{"id":163},"mode-a-route-live-diagnosis",[165],{"type":70,"value":166},"Mode A route: live diagnosis",{"type":64,"tag":168,"props":169,"children":171},"h3",{"id":170},"required-inputs",[172],{"type":70,"value":173},"Required inputs",{"type":64,"tag":73,"props":175,"children":176},{},[177],{"type":70,"value":178},"account_id, region, instance_id, and the failing DNS name.",{"type":64,"tag":168,"props":180,"children":182},{"id":181},"tool-sequence-in-order",[183],{"type":70,"value":184},"Tool sequence (in order)",{"type":64,"tag":186,"props":187,"children":188},"ol",{},[189,200,219],{"type":64,"tag":104,"props":190,"children":191},{},[192,198],{"type":64,"tag":79,"props":193,"children":195},{"className":194},[],[196],{"type":70,"value":197},"dns_probe_context",{"type":70,"value":199}," — establishes VPC-attribute preconditions: enableDnsSupport,\nenableDnsHostnames, address family, DHCP option set. A resolution result means\nnothing until you know whether the VPC resolver is answering.",{"type":64,"tag":104,"props":201,"children":202},{},[203,209,211,217],{"type":64,"tag":79,"props":204,"children":206},{"className":205},[],[207],{"type":70,"value":208},"dns_probe_compare",{"type":70,"value":210}," — runs the allowlisted probe set inside the instance via\nSSM. Returns each resolver's answer and the resolver's own identity from\n",{"type":64,"tag":79,"props":212,"children":214},{"className":213},[],[215],{"type":70,"value":216},"hostname.bind",{"type":70,"value":218},". The VPC DHCP resolver is auto-added for comparison.",{"type":64,"tag":104,"props":220,"children":221},{},[222,227],{"type":64,"tag":79,"props":223,"children":225},{"className":224},[],[226],{"type":70,"value":146},{"type":70,"value":228}," — load the pattern runbook matching the observed signature\n(see trap-to-SOP mapping below).",{"type":64,"tag":168,"props":230,"children":232},{"id":231},"interpretation-rules",[233],{"type":70,"value":234},"Interpretation rules",{"type":64,"tag":100,"props":236,"children":237},{},[238,259,272],{"type":64,"tag":104,"props":239,"children":240},{},[241,243,249,251,257],{"type":70,"value":242},"If ",{"type":64,"tag":79,"props":244,"children":246},{"className":245},[],[247],{"type":70,"value":248},"enableDnsSupport",{"type":70,"value":250}," is false: load ",{"type":64,"tag":79,"props":252,"children":254},{"className":253},[],[255],{"type":70,"value":256},"A-resolver-disabled-precondition",{"type":70,"value":258},". The\nVPC resolver is intentionally dark and every probe failure follows from that.",{"type":64,"tag":104,"props":260,"children":261},{},[262,264,270],{"type":70,"value":263},"Compare the instance's ",{"type":64,"tag":79,"props":265,"children":267},{"className":266},[],[268],{"type":70,"value":269},"\u002Fetc\u002Fresolv.conf",{"type":70,"value":271}," (from the probe output) against the\nDHCP option set. A mismatch means the instance is not using the VPC-intended\nresolver.",{"type":64,"tag":104,"props":273,"children":274},{},[275,277,283],{"type":70,"value":276},"Judge answers by name category (load ",{"type":64,"tag":79,"props":278,"children":280},{"className":279},[],[281],{"type":70,"value":282},"A-name-category-classification",{"type":70,"value":284},"), not by\nwhether resolvers agree. Two resolvers returning the same wrong answer is still\na failure.",{"type":64,"tag":168,"props":286,"children":288},{"id":287},"mode-a-trap-to-sop-mapping",[289],{"type":70,"value":290},"Mode A trap-to-SOP mapping",{"type":64,"tag":292,"props":293,"children":294},"table",{},[295,314],{"type":64,"tag":296,"props":297,"children":298},"thead",{},[299],{"type":64,"tag":300,"props":301,"children":302},"tr",{},[303,309],{"type":64,"tag":304,"props":305,"children":306},"th",{},[307],{"type":70,"value":308},"Observed signature",{"type":64,"tag":304,"props":310,"children":311},{},[312],{"type":70,"value":313},"SOP slug",{"type":64,"tag":315,"props":316,"children":317},"tbody",{},[318,336,353,370,386],{"type":64,"tag":300,"props":319,"children":320},{},[321,327],{"type":64,"tag":322,"props":323,"children":324},"td",{},[325],{"type":70,"value":326},"Custom resolver answers differently from VPC .2",{"type":64,"tag":322,"props":328,"children":329},{},[330],{"type":64,"tag":79,"props":331,"children":333},{"className":332},[],[334],{"type":70,"value":335},"A-custom-resolver-divergence",{"type":64,"tag":300,"props":337,"children":338},{},[339,344],{"type":64,"tag":322,"props":340,"children":341},{},[342],{"type":70,"value":343},"FORWARD rule and PHZ both match the name",{"type":64,"tag":322,"props":345,"children":346},{},[347],{"type":64,"tag":79,"props":348,"children":350},{"className":349},[],[351],{"type":70,"value":352},"A-forward-vs-phz-precedence-collision",{"type":64,"tag":300,"props":354,"children":355},{},[356,361],{"type":64,"tag":322,"props":357,"children":358},{},[359],{"type":70,"value":360},"A record works, AAAA fails (or vice versa)",{"type":64,"tag":322,"props":362,"children":363},{},[364],{"type":64,"tag":79,"props":365,"children":367},{"className":366},[],[368],{"type":70,"value":369},"A-address-family-divergence",{"type":64,"tag":300,"props":371,"children":372},{},[373,378],{"type":64,"tag":322,"props":374,"children":375},{},[376],{"type":70,"value":377},"enableDnsSupport is false",{"type":64,"tag":322,"props":379,"children":380},{},[381],{"type":64,"tag":79,"props":382,"children":384},{"className":383},[],[385],{"type":70,"value":256},{"type":64,"tag":300,"props":387,"children":388},{},[389,394],{"type":64,"tag":322,"props":390,"children":391},{},[392],{"type":70,"value":393},"General live comparison procedure",{"type":64,"tag":322,"props":395,"children":396},{},[397],{"type":64,"tag":79,"props":398,"children":400},{"className":399},[],[401],{"type":70,"value":402},"A-mode-a-live-resolver-comparison",{"type":64,"tag":168,"props":404,"children":406},{"id":405},"reporting-format-for-mode-a",[407],{"type":70,"value":408},"Reporting format for Mode A",{"type":64,"tag":73,"props":410,"children":411},{},[412,414,419,421,426],{"type":70,"value":413},"Label every finding as ",{"type":64,"tag":108,"props":415,"children":416},{},[417],{"type":70,"value":418},"Observed",{"type":70,"value":420}," (ground truth from the probe). State which\nresolver answered and what it returned. When Mode A and Mode B produce different\nconclusions for the same name, ",{"type":64,"tag":108,"props":422,"children":423},{},[424],{"type":70,"value":425},"Mode A wins",{"type":70,"value":427}," because it is ground truth from\ninside the subnet.",{"type":64,"tag":158,"props":429,"children":430},{},[],{"type":64,"tag":88,"props":432,"children":434},{"id":433},"mode-b-route-pre-change-validation",[435],{"type":70,"value":436},"Mode B route: pre-change validation",{"type":64,"tag":168,"props":438,"children":440},{"id":439},"required-inputs-1",[441],{"type":70,"value":173},{"type":64,"tag":73,"props":443,"children":444},{},[445,447,453],{"type":70,"value":446},"account_id, region, vpc_id, and a change descriptor (structured dict with ",{"type":64,"tag":79,"props":448,"children":450},{"className":449},[],[451],{"type":70,"value":452},"type",{"type":70,"value":454},"\nand type-specific fields). No instance required.",{"type":64,"tag":168,"props":456,"children":458},{"id":457},"tool-sequence-in-order-1",[459],{"type":70,"value":184},{"type":64,"tag":186,"props":461,"children":462},{},[463,474,485],{"type":64,"tag":104,"props":464,"children":465},{},[466,472],{"type":64,"tag":79,"props":467,"children":469},{"className":468},[],[470],{"type":70,"value":471},"dns_simulate_effective_config",{"type":70,"value":473}," — returns the VPC's effective DNS config: the\nunion of directly attached resources and anything inherited through an\nassociated Route 53 Profile, each construct tagged by source.",{"type":64,"tag":104,"props":475,"children":476},{},[477,483],{"type":64,"tag":79,"props":478,"children":480},{"className":479},[],[481],{"type":70,"value":482},"dns_simulate_change",{"type":70,"value":484}," — applies the proposed change symbolically and returns a\nper-name impact report (before\u002Fafter, delta, traps, severity, volume).",{"type":64,"tag":104,"props":486,"children":487},{},[488,493],{"type":64,"tag":79,"props":489,"children":491},{"className":490},[],[492],{"type":70,"value":146},{"type":70,"value":494}," — load runbooks for any traps reported in the impact table\n(see trap-to-SOP mapping below).",{"type":64,"tag":168,"props":496,"children":498},{"id":497},"interpretation-rules-1",[499],{"type":70,"value":234},{"type":64,"tag":100,"props":501,"children":502},{},[503,508,513],{"type":64,"tag":104,"props":504,"children":505},{},[506],{"type":70,"value":507},"Never recommend applying a change without simulating it first. A broad FORWARD\nrule, enabling private DNS on an interface endpoint, or a Profile association\ncan silently redirect names that currently resolve correctly.",{"type":64,"tag":104,"props":509,"children":510},{},[511],{"type":70,"value":512},"The candidate set is limited to API-derived names (PHZ records, rule domains,\nVPCE apexes, Firewall domain lists) or operator-supplied names. It is not\nexhaustive. State the coverage boundary.",{"type":64,"tag":104,"props":514,"children":515},{},[516,518,524],{"type":70,"value":517},"If the operator supplies ",{"type":64,"tag":79,"props":519,"children":521},{"className":520},[],[522],{"type":70,"value":523},"volumes",{"type":70,"value":525}," (from Resolver Query Logs), names are ranked\nby traffic. This is enrichment; absence does not invalidate the simulation.",{"type":64,"tag":168,"props":527,"children":529},{"id":528},"mode-b-trap-to-sop-mapping",[530],{"type":70,"value":531},"Mode B trap-to-SOP mapping",{"type":64,"tag":292,"props":533,"children":534},{},[535,550],{"type":64,"tag":296,"props":536,"children":537},{},[538],{"type":64,"tag":300,"props":539,"children":540},{},[541,546],{"type":64,"tag":304,"props":542,"children":543},{},[544],{"type":70,"value":545},"Trap label in impact report",{"type":64,"tag":304,"props":547,"children":548},{},[549],{"type":70,"value":313},{"type":64,"tag":315,"props":551,"children":552},{},[553,570,587,604,621,638],{"type":64,"tag":300,"props":554,"children":555},{},[556,561],{"type":64,"tag":322,"props":557,"children":558},{},[559],{"type":70,"value":560},"VPCE-shadow-NXDOMAIN",{"type":64,"tag":322,"props":562,"children":563},{},[564],{"type":64,"tag":79,"props":565,"children":567},{"className":566},[],[568],{"type":70,"value":569},"B-vpce-shadow-nxdomain",{"type":64,"tag":300,"props":571,"children":572},{},[573,578],{"type":64,"tag":322,"props":574,"children":575},{},[576],{"type":70,"value":577},"broad-FORWARD-sweep",{"type":64,"tag":322,"props":579,"children":580},{},[581],{"type":64,"tag":79,"props":582,"children":584},{"className":583},[],[585],{"type":70,"value":586},"B-broad-forward-sweep",{"type":64,"tag":300,"props":588,"children":589},{},[590,595],{"type":64,"tag":322,"props":591,"children":592},{},[593],{"type":70,"value":594},"flag-AND-mismatch",{"type":64,"tag":322,"props":596,"children":597},{},[598],{"type":64,"tag":79,"props":599,"children":601},{"className":600},[],[602],{"type":70,"value":603},"B-flag-and-mismatch",{"type":64,"tag":300,"props":605,"children":606},{},[607,612],{"type":64,"tag":322,"props":608,"children":609},{},[610],{"type":70,"value":611},"DNS-Firewall-block",{"type":64,"tag":322,"props":613,"children":614},{},[615],{"type":64,"tag":79,"props":616,"children":618},{"className":617},[],[619],{"type":70,"value":620},"B-dns-firewall-block",{"type":64,"tag":300,"props":622,"children":623},{},[624,629],{"type":64,"tag":322,"props":625,"children":626},{},[627],{"type":70,"value":628},"profile-union-shift",{"type":64,"tag":322,"props":630,"children":631},{},[632],{"type":64,"tag":79,"props":633,"children":635},{"className":634},[],[636],{"type":70,"value":637},"B-profile-propagation-timing",{"type":64,"tag":300,"props":639,"children":640},{},[641,646],{"type":64,"tag":322,"props":642,"children":643},{},[644],{"type":70,"value":645},"General pre-change procedure",{"type":64,"tag":322,"props":647,"children":648},{},[649],{"type":64,"tag":79,"props":650,"children":652},{"className":651},[],[653],{"type":70,"value":654},"B-mode-b-pre-change-validation",{"type":64,"tag":168,"props":656,"children":658},{"id":657},"reporting-format-for-mode-b",[659],{"type":70,"value":660},"Reporting format for Mode B",{"type":64,"tag":73,"props":662,"children":663},{},[664,665,670],{"type":70,"value":413},{"type":64,"tag":108,"props":666,"children":667},{},[668],{"type":70,"value":669},"Predicted",{"type":70,"value":671}," (symbolic, not ground truth). State the\ncandidate-set size, its source (API-derived or operator-supplied), and that names\noutside this set were not evaluated. Include the propagation timing caveat for\nProfile changes.",{"type":64,"tag":158,"props":673,"children":674},{},[],{"type":64,"tag":88,"props":676,"children":678},{"id":677},"cross-account-opacity",[679],{"type":70,"value":680},"Cross-account opacity",{"type":64,"tag":73,"props":682,"children":683},{},[684,686,691,692,698],{"type":70,"value":685},"Call ",{"type":64,"tag":79,"props":687,"children":689},{"className":688},[],[690],{"type":70,"value":146},{"type":70,"value":148},{"type":64,"tag":79,"props":693,"children":695},{"className":694},[],[696],{"type":70,"value":697},"C-cross-account-opaque-constructs",{"type":70,"value":699}," when the effective\nconfig or impact report contains opaque markers. Cross-account constructs shared\nvia RAM or a Route 53 Profile may be enumerable but their contents are not\nreadable from the consumer account. Report them as \"present but unknown content\"\nrather than treating them as absent or inferring past them.",{"type":64,"tag":88,"props":701,"children":703},{"id":702},"limitations",[704],{"type":70,"value":705},"Limitations",{"type":64,"tag":73,"props":707,"children":708},{},[709,710,715,716,722],{"type":70,"value":685},{"type":64,"tag":79,"props":711,"children":713},{"className":712},[],[714],{"type":70,"value":146},{"type":70,"value":148},{"type":64,"tag":79,"props":717,"children":719},{"className":718},[],[720],{"type":70,"value":721},"C-limitations-and-boundaries",{"type":70,"value":723}," and state the relevant\nboundaries to the operator. Key constraints:",{"type":64,"tag":100,"props":725,"children":726},{},[727,732,737,742,747],{"type":64,"tag":104,"props":728,"children":729},{},[730],{"type":70,"value":731},"All tools are read-only. Do not modify, delete, or create DNS resources.",{"type":64,"tag":104,"props":733,"children":734},{},[735],{"type":70,"value":736},"Mode A requires SSM reachability (ssm, ssmmessages, ec2messages VPC endpoints\nand an instance role with AmazonSSMManagedInstanceCore).",{"type":64,"tag":104,"props":738,"children":739},{},[740],{"type":70,"value":741},"Mode B candidate sets are not exhaustive. The \"no impacts\" conclusion applies\nonly within the tested set.",{"type":64,"tag":104,"props":743,"children":744},{},[745],{"type":70,"value":746},"Opaque constructs cannot be resolved from this account.",{"type":64,"tag":104,"props":748,"children":749},{},[750],{"type":70,"value":751},"Resolver Query Log ingestion is not implemented; volumes must be supplied by\nthe operator.",{"type":64,"tag":88,"props":753,"children":755},{"id":754},"final-response-requirements",[756],{"type":70,"value":757},"Final response requirements",{"type":64,"tag":73,"props":759,"children":760},{},[761],{"type":70,"value":762},"Every response produced by this skill must include:",{"type":64,"tag":186,"props":764,"children":765},{},[766,783,788,793,798],{"type":64,"tag":104,"props":767,"children":768},{},[769,771,775,777,781],{"type":70,"value":770},"Each finding labelled ",{"type":64,"tag":108,"props":772,"children":773},{},[774],{"type":70,"value":418},{"type":70,"value":776}," (Mode A) or ",{"type":64,"tag":108,"props":778,"children":779},{},[780],{"type":70,"value":669},{"type":70,"value":782}," (Mode B).",{"type":64,"tag":104,"props":784,"children":785},{},[786],{"type":70,"value":787},"When both modes were used, state \"Mode A wins\" for any conflict.",{"type":64,"tag":104,"props":789,"children":790},{},[791],{"type":70,"value":792},"The candidate-set coverage: how many names, what source, what was not tested.",{"type":64,"tag":104,"props":794,"children":795},{},[796],{"type":70,"value":797},"Any opaque constructs and their impact on the conclusion.",{"type":64,"tag":104,"props":799,"children":800},{},[801],{"type":70,"value":802},"Recommended next steps or the specific change to apply (never apply it).",{"type":64,"tag":88,"props":804,"children":806},{"id":805},"prerequisites",[807],{"type":70,"value":808},"Prerequisites",{"type":64,"tag":73,"props":810,"children":811},{},[812,814,820],{"type":70,"value":813},"Requires the aws-vpc-dns-diagnostics MCP server registered in the Agent Space\nwith its tools allowlisted. The server is at ",{"type":64,"tag":79,"props":815,"children":817},{"className":816},[],[818],{"type":70,"value":819},"mcp\u002Faws-vpc-dns-diagnostics-mcp\u002F",{"type":70,"value":821},".\nIf the server is not registered or SSM is unreachable, report that as the blocker\nrather than guessing at the resolution path.",{"items":823,"total":924},[824,838,845,861,877,893,908],{"slug":825,"name":825,"fn":826,"description":827,"org":828,"tags":829,"stars":24,"repoUrl":25,"updatedAt":837},"aws-health-events","analyze AWS Health events for incidents","ALWAYS use this skill in the beginning of any incident investigation, root cause analysis, or operational troubleshooting. This skill retrieves and analyzes AWS Health events (service issues, scheduled changes, and account notifications) to identify AWS-side events that may explain or correlate with observed operational issues. Activate this skill when investigating an issue and you observe service degradation, elevated error rates, latency spikes, connection failures, throttling, capacity issues, deployment-related failures, alarms, or any operational event or issue. This skill searches AWS Health events by service, time window, region, and status to surface active or recent service disruptions, scheduled maintenance, and account-specific notifications that inform the current investigation. Also activate when a user requests a health event summary or report for their account over a specified time period.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[830,831,832,834],{"name":20,"slug":8,"type":15},{"name":22,"slug":23,"type":15},{"name":833,"slug":41,"type":15},"Incident Response",{"name":835,"slug":836,"type":15},"Monitoring","monitoring","2026-08-20T03:53:41.178955",{"slug":4,"name":4,"fn":5,"description":6,"org":839,"tags":840,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[841,842,843,844],{"name":20,"slug":8,"type":15},{"name":22,"slug":23,"type":15},{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"slug":846,"name":846,"fn":847,"description":848,"org":849,"tags":850,"stars":24,"repoUrl":25,"updatedAt":860},"crm-production-investigation-guidelines","investigate CRM production incidents","Guidelines for investigating production incidents in the CRM application. Use when triaging any alert or incident involving the CRM REST API, SQS queues, Lambda functions, or Aurora DSQL database in this AWS account. Ensures thorough root cause analysis using AWS-native observability tools.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[851,852,855,856,857],{"name":20,"slug":8,"type":15},{"name":853,"slug":854,"type":15},"CRM","crm",{"name":22,"slug":23,"type":15},{"name":833,"slug":41,"type":15},{"name":858,"slug":859,"type":15},"Operations","operations","2026-08-20T03:53:23.532781",{"slug":862,"name":862,"fn":863,"description":864,"org":865,"tags":866,"stars":24,"repoUrl":25,"updatedAt":876},"database-migration-service-expertise","troubleshoot AWS Database Migration Service","AWS Database Migration Service (DMS) operational review and troubleshooting skill. Conducts best practices validation, health assessments, performance diagnostics, cost optimization reviews, and migration cutover guidance. Triggers on requests like \"DMS review\", \"DMS health check\", \"DMS troubleshooting\", \"migration assessment\", \"DMS best practices audit\", \"DMS cost optimization\", \"replication instance review\", \"CDC latency issue\", or \"DMS task failure\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[867,868,871,872,875],{"name":20,"slug":8,"type":15},{"name":869,"slug":870,"type":15},"Database","database",{"name":22,"slug":23,"type":15},{"name":873,"slug":874,"type":15},"Migration","migration",{"name":858,"slug":859,"type":15},"2026-08-20T03:53:23.927999",{"slug":878,"name":878,"fn":879,"description":880,"org":881,"tags":882,"stars":24,"repoUrl":25,"updatedAt":892},"database-rds-devops","diagnose Aurora MySQL and PostgreSQL databases","Database-level data-plane diagnostics for Aurora MySQL and Aurora PostgreSQL. Executes predefined read-only health check queries via RDS Data API to analyze buffer pool, connections, locks, replication, storage, performance, and index efficiency. Requires the rds-aidba MCP server for database-internal access beyond what CloudWatch and RDS APIs provide.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[883,884,885,886,889],{"name":20,"slug":8,"type":15},{"name":869,"slug":870,"type":15},{"name":22,"slug":23,"type":15},{"name":887,"slug":888,"type":15},"MySQL","mysql",{"name":890,"slug":891,"type":15},"PostgreSQL","postgresql","2026-08-20T03:53:41.560344",{"slug":894,"name":894,"fn":895,"description":896,"org":897,"tags":898,"stars":24,"repoUrl":25,"updatedAt":907},"eks-operation-review","audit Amazon EKS cluster operations","Comprehensive Amazon EKS operational review aligned with the AWS EKS Best Practices Guide. Use this skill when a user asks to review, audit, or assess EKS clusters for best practices compliance, operational readiness, security posture, cost optimization, reliability, networking, scalability, or upgrade readiness. Triggers on requests like \"EKS review\", \"EKS best practices audit\", \"EKS operational assessment\", \"review my EKS cluster\", or \"EKS health check\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[899,902,903,906],{"name":900,"slug":901,"type":15},"Audit","audit",{"name":20,"slug":8,"type":15},{"name":904,"slug":905,"type":15},"Kubernetes","kubernetes",{"name":858,"slug":859,"type":15},"2026-08-20T03:53:20.524374",{"slug":909,"name":909,"fn":910,"description":911,"org":912,"tags":913,"stars":24,"repoUrl":25,"updatedAt":923},"enrich-with-aws-security-agent","investigate security root causes in AWS","Automatically load this skill when investigating application outages, service degradation, or errors that could have security-related root causes — including unexplained downtime, authentication or authorization failures, injection attacks, data exposure, or suspicious application behavior. Query AWS Security Agent CloudWatch logs to retrieve detailed code review findings with actionable, low-level details (file, line number, vulnerability type) that customers can directly fix.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[914,917,918,919,920],{"name":915,"slug":916,"type":15},"Auth","auth",{"name":20,"slug":8,"type":15},{"name":22,"slug":23,"type":15},{"name":833,"slug":41,"type":15},{"name":921,"slug":922,"type":15},"Security","security","2026-08-20T03:53:23.097965",15,{"items":926,"total":1091},[927,945,960,973,988,998,1011,1027,1041,1054,1065,1077],{"slug":928,"name":928,"fn":929,"description":930,"org":931,"tags":932,"stars":942,"repoUrl":943,"updatedAt":944},"agents-build","add capabilities to existing agent projects","Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: \"add memory\", \"remember across sessions\", \"call agent from app\", \"invoke agent from code\", \"agent auth\", \"streaming\", \"VPC\", \"VPC connectivity\", \"can't reach from VPC\", \"multi-agent\", \"A2A\", \"A2A auth\", \"orchestrator not delegating\", \"specialist not called\", \"migrate Bedrock Agent\", \"migration issue\", \"change model\", \"browser tool\", \"code interpreter\", \"delete agent\", \"tear down\", \"agentcore remove\", \"cross-account memory\", \"add payments capability to my agent\", \"wire payments plugin\", \"integrate x402 payments with the agent I'm building\", \"add MPP payments\", \"Machine Payments Protocol\". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI\u002Fdev-server errors: use agents-debug. Runtime x402\u002FMPP payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[933,935,938,939],{"name":934,"slug":32,"type":15},"Agents",{"name":936,"slug":937,"type":15},"Automation","automation",{"name":20,"slug":8,"type":15},{"name":940,"slug":941,"type":15},"Engineering","engineering",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-08-20T03:27:06.137661",{"slug":946,"name":946,"fn":947,"description":948,"org":949,"tags":950,"stars":942,"repoUrl":943,"updatedAt":959},"agents-connect","connect agents to external services","Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: \"connect to API\", \"add gateway\", \"connect to MCP server\", \"Lambda tools\", \"OpenAPI\", \"gateway target\", \"Cedar policy\", \"restrict tools\", \"policy engine\", \"gateway auth error\", \"store API key\", \"outbound credential\", \"env var API key\", \"API key None after deploy\", \"credential not available after deploy\", \"should this be a gateway target\", \"give my agent tools\", \"add tools to agent\". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[951,952,955,958],{"name":934,"slug":32,"type":15},{"name":953,"slug":954,"type":15},"API Development","api-development",{"name":956,"slug":957,"type":15},"Authentication","authentication",{"name":20,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":961,"name":961,"fn":962,"description":963,"org":964,"tags":965,"stars":942,"repoUrl":943,"updatedAt":972},"agents-debug","debug agent and environment issues","Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: \"agent not working\", \"wrong answer\", \"agent error\", \"tool call failing\", \"debug agent\", \"check logs\", \"read traces\", \"broken\", \"500 error\", \"424 error\", \"model access denied\", \"command not found\", \"stuck in DELETING\", \"maxVms exceeded\", \"cold start diagnosis\", \"cold start slow\", \"agentcore create error\", \"create failed\", \"exit code 7\", \"connection refused local dev\". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[966,967,968,969],{"name":934,"slug":32,"type":15},{"name":20,"slug":8,"type":15},{"name":22,"slug":23,"type":15},{"name":970,"slug":971,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":974,"name":974,"fn":975,"description":976,"org":977,"tags":978,"stars":942,"repoUrl":943,"updatedAt":987},"agents-deploy","deploy AI agents to AWS","Use when deploying your agent to AWS, or when a deploy has failed. Handles pre-flight validation, CDK\u002FIAM\u002Fquota error diagnosis, version management, rollback, and canary deployments. Triggers on: \"deploy my agent\", \"agentcore deploy\", \"deploy failed\", \"CDK error\", \"rollback\", \"canary deploy\", \"pin version\", \"redeploy\", \"deploy stuck\". Not for production hardening — use agents-harden. Not for adding capabilities before deploy — use agents-build or agents-connect. Not for VPC configuration errors — use agents-build.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[979,980,981,984],{"name":934,"slug":32,"type":15},{"name":20,"slug":8,"type":15},{"name":982,"slug":983,"type":15},"CI\u002FCD","ci-cd",{"name":985,"slug":986,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":989,"name":989,"fn":990,"description":991,"org":992,"tags":993,"stars":942,"repoUrl":943,"updatedAt":997},"agents-get-started","scaffold and deploy new agent projects","Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: \"build an agent\", \"create an agent\", \"get started\", \"new project\", \"agentcore create\", \"which framework\", \"Strands vs LangGraph\", \"hello world agent\", \"first agent\", \"create MCP server\", \"host MCP server\", \"agentcore dev\", \"dev server\", \"what port\", \"local development\". Not for adding capabilities to existing projects — use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[994,995,996],{"name":934,"slug":32,"type":15},{"name":20,"slug":8,"type":15},{"name":985,"slug":986,"type":15},"2026-07-12T08:42:51.963247",{"slug":999,"name":999,"fn":1000,"description":1001,"org":1002,"tags":1003,"stars":942,"repoUrl":943,"updatedAt":1010},"agents-harden","harden agents for production","Use when preparing your agent for production — IAM scoping, inbound auth (JWT, SigV4), secrets management, cold start optimization, session lifecycle, rate limiting, input validation, and quota guidance. Triggers on: \"production checklist\", \"harden agent\", \"production ready\", \"secure agent\", \"inbound auth\", \"going live\", \"cold start optimization\", \"session lifecycle\", \"StopRuntimeSession\", \"quota\", \"throttling\", \"maxVms\", \"rate limit\", \"security audit of outbound API calls\", \"gateway target audit for production\", \"restrict who can call\", \"lock down endpoint\", \"only our app can call\". Not for Cedar tool-restriction policies — use agents-connect. Not for quality measurement — use agents-optimize. Not for outbound credential storage or API key wiring — use agents-connect. Not for A2A agent-to-agent auth — use agents-build. Cold start observation and diagnosis (not optimization) routes to agents-debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1004,1005,1006,1009],{"name":934,"slug":32,"type":15},{"name":20,"slug":8,"type":15},{"name":1007,"slug":1008,"type":15},"Best Practices","best-practices",{"name":921,"slug":922,"type":15},"2026-07-16T06:00:42.174705",{"slug":1012,"name":1012,"fn":1013,"description":1014,"org":1015,"tags":1016,"stars":942,"repoUrl":943,"updatedAt":1026},"agents-optimize","optimize agent quality and performance","Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI\u002FCD quality gates, observability, or cost optimization. Triggers on: \"evaluate my agent\", \"add evaluator\", \"measure quality\", \"quality gate\", \"run evals\", \"agent too slow\", \"why is it slow\", \"reduce latency\", \"set up observability\", \"CloudWatch dashboard\", \"how much does my agent cost\", \"cost optimization\", \"logs not showing up\", \"logs missing\", \"spans not found\", \"eval failing\", \"eval error\", \"dev traces\", \"local traces\", \"agentcore dev traces\", \"traces to CloudWatch\". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1017,1018,1019,1022,1023],{"name":934,"slug":32,"type":15},{"name":20,"slug":8,"type":15},{"name":1020,"slug":1021,"type":15},"Evals","evals",{"name":970,"slug":971,"type":15},{"name":1024,"slug":1025,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",{"slug":1028,"name":1028,"fn":1029,"description":1030,"org":1031,"tags":1032,"stars":942,"repoUrl":943,"updatedAt":1040},"agents-pay","handle x402 payments for agent tasks","Use when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits. Covers payment setup, policy, session budgets, and troubleshooting. Triggers on: \"my agent hit a 402 while calling an API\", \"a tool call returned 402 Payment Required\", \"my agent needs to pay for x402-protected content\", \"let the agent pay for content, capped at $5 per session\", \"set a spend limit for the agent\", \"ProcessPayment failed\", or \"why did my agent refuse to pay\". Not for BUILDING payment capability for end users, including wallets and framework middleware; use agents-build and references\u002Fpayments.md. For non-paid APIs via Gateway use agents-connect. For inbound auth use agents-harden. For project scaffolding use agents-get-started.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1033,1034,1035,1038],{"name":934,"slug":32,"type":15},{"name":936,"slug":937,"type":15},{"name":1036,"slug":1037,"type":15},"Payments","payments",{"name":1039,"slug":1039,"type":15},"x402","2026-08-10T04:16:31.844309",{"slug":1042,"name":1042,"fn":1043,"description":1044,"org":1045,"tags":1046,"stars":942,"repoUrl":943,"updatedAt":1053},"amazon-aurora-mysql","manage Amazon Aurora MySQL clusters","Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1047,1048,1049,1050],{"name":20,"slug":8,"type":15},{"name":869,"slug":870,"type":15},{"name":887,"slug":888,"type":15},{"name":1051,"slug":1052,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":1055,"name":1055,"fn":1056,"description":1057,"org":1058,"tags":1059,"stars":942,"repoUrl":943,"updatedAt":1064},"amazon-aurora-postgresql","configure Amazon Aurora PostgreSQL clusters","Amazon Aurora PostgreSQL — creates, modifies, and advises on Aurora PostgreSQL clusters specifically (PostgreSQL-compatible engine, Aurora serverless, express configuration, pgvector, Babelfish). Trigger for Aurora PostgreSQL cluster operations, express-configuration quick-start, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or PostgreSQL upgrade planning. For Aurora MySQL, use amazon-aurora-mysql instead. Contains safety guardrails, express-first routing, and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1060,1061,1062,1063],{"name":20,"slug":8,"type":15},{"name":869,"slug":870,"type":15},{"name":890,"slug":891,"type":15},{"name":1051,"slug":1052,"type":15},"2026-07-16T06:00:34.789624",{"slug":1066,"name":1066,"fn":1067,"description":1068,"org":1069,"tags":1070,"stars":942,"repoUrl":943,"updatedAt":1076},"amazon-bedrock","build generative AI apps with Amazon Bedrock","Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore (including the Harness managed agent loop). Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, migrating\u002Fporting\u002Fconverting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing models (Claude, Llama, Nova, Titan). ALSO USE for prompt caching, quota health checks and throttling diagnosis, cost attribution, migrating between Claude model generations, chunking strategies, API selection (Converse vs InvokeModel), and model selection. Also covers AgentCore Payments setup (x402, microtransactions, Payment Manager, Coinbase CDP, Stripe Privy, 402 Payment Required, paid endpoint). NOT for custom model training, Rekognition, or Comprehend.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1071,1072,1073],{"name":934,"slug":32,"type":15},{"name":20,"slug":8,"type":15},{"name":1074,"slug":1075,"type":15},"LLM","llm","2026-08-07T04:38:13.03499",{"slug":1078,"name":1078,"fn":1079,"description":1080,"org":1081,"tags":1082,"stars":942,"repoUrl":943,"updatedAt":1090},"amazon-braket","run quantum computing workflows on AWS","Runs quantum computing workflows on AWS through Amazon Braket — discovering devices (QPUs and simulators) and their availability, building gate-model circuits and analog Hamiltonian programs, submitting quantum tasks, program sets and hybrid jobs, looking up prices, and capping spend with spending limits. Applies to any request about quantum computing, quantum hardware, quantum simulation, AHS, OpenQASM, or running a quantum algorithm on AWS.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1083,1084,1087],{"name":20,"slug":8,"type":15},{"name":1085,"slug":1086,"type":15},"Quantum Computing","quantum-computing",{"name":1088,"slug":1089,"type":15},"Simulation","simulation","2026-08-20T03:53:19.377174",139]