[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-aws-resilience-lifecycle":3,"mdc-2hob8a-key":35,"related-org-aws-aws-resilience-lifecycle":484,"related-repo-aws-aws-resilience-lifecycle":657},{"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":30,"sourceUrl":33,"mdContent":34},"aws-resilience-lifecycle","manage AWS resilience lifecycle","Guides the end-to-end AWS resilience lifecycle integrating Resilience Hub v2, Fault Injection Service, and Application Recovery Controller. Covers the Define → Test → Operate workflow: from policy creation through failure mode assessment, to FIS experiment validation, to ARC operational controls. Applicable when the user wants a complete resilience strategy, needs to connect findings to experiments to controls, or is planning a resilience program. Also applicable for the meta question of whether marking NGRH findings as resolved is enough, whether they are \"done\" after resolving findings, or how to validate findings before resolving them. Not applicable for resolving or remediating a specific individual finding (see resilience-hub-failure-mode-assessment), or when a single service is explicitly named (e.g. \"what FIS experiment should I run\").\n",{"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,22],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"Monitoring","monitoring",{"name":20,"slug":21,"type":15},"Reliability","reliability",{"name":23,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-07-25T05:56:35.30358",null,157,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS","https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws\u002Ftree\u002FHEAD\u002Fskills\u002Fspecialized-skills\u002Fresilience-skills\u002Faws-resilience-lifecycle","---\nname: aws-resilience-lifecycle\ndescription: >\n  Guides the end-to-end AWS resilience lifecycle integrating Resilience Hub v2, Fault Injection Service,\n  and Application Recovery Controller. Covers the Define → Test → Operate workflow: from\n  policy creation through failure mode assessment, to FIS experiment validation, to ARC\n  operational controls. Applicable when the user wants a complete resilience strategy, needs to\n  connect findings to experiments to controls, or is planning a resilience program.\n  Also applicable for the meta question of whether marking NGRH findings as resolved is enough,\n  whether they are \"done\" after resolving findings, or how to validate findings before\n  resolving them. Not applicable for resolving or remediating a specific individual finding\n  (see resilience-hub-failure-mode-assessment), or when a single service is explicitly\n  named (e.g. \"what FIS experiment should I run\").\nversion: 1\n---\n\n# AWS Resilience Lifecycle\n\n## Overview\n\nDomain expertise for the integrated resilience lifecycle across three AWS services:\nDefine (Resilience Hub v2 — also called NGRH, New Generation Resilience Hub) → Test (FIS) → Operate (ARC).\n\n**Terminology:** in this skill an unqualified \"Resilience Hub\" always means **v2** (NGRH \u002F New Generation Resilience Hub, CLI namespace `aws resiliencehubv2`). v1 (`aws resiliencehub`) is referenced *only* explicitly, and only for migration.\n\n> The AWS MCP server is recommended for executing this skill's AWS API calls, but it is not required — all operations also work with the AWS CLI directly.\n\n## Guardrail — where this skill's own files live (MCP vs local install)\n\nBefore reading a reference file, determine how this skill was loaded:\n\n- **Loaded via the AWS MCP `retrieve_skill` tool:** the skill's reference files are not on the local filesystem. Fetch each one through `retrieve_skill` with the `file` parameter (e.g. `file=\"references\u002Flifecycle-workflow.md\"` or `file=\"references\u002Fapi-reference.md\"`) — do NOT `file_read` these paths locally or search the filesystem for them.\n- **Installed locally** (e.g. `.kiro\u002Fskills\u002Faws-resilience-lifecycle\u002F` or `~\u002F.claude\u002Fskills\u002Faws-resilience-lifecycle\u002F`): read reference files from the local skill directory using the relative paths shown here.\n\nThis applies only to the skill's own reference files; always read and write user or session data in the working directory, never through `retrieve_skill`.\n\n## Execute the full lifecycle\n\nTo implement end-to-end resilience across all three services, follow the procedure exactly.\nSee [references\u002Flifecycle-workflow.md](references\u002Flifecycle-workflow.md).\n\nFor operational patterns and policy design guidance, see\n[references\u002Fbest-practices.md](references\u002Fbest-practices.md).\n\n## Validate findings before you resolve them\n\nMarking NGRH findings as resolved without proving the fix with fault injection is **paper\ncompliance** — it records intent, not resilience. You MUST validate each remediation with an\nexperiment that reproduces the failure mode BEFORE marking the finding resolved. Run the\nexperiment, confirm the system recovers within its objectives, then mark resolved. Marking\nresolved first and validating \"later\" is the anti-pattern.\n\n## Monitoring & observability\n\nWhen the user asks what monitoring\u002Fobservability they need for resilience, **recommend the\ncompanion AWS Observability skill** as the source for CloudWatch alarms, dashboards, and metric\ndesign — do NOT replicate observability setup content here. Stay in the resilience lane and\nexplain how observability plugs into the lifecycle:\n\n- **FIS stop conditions:** CloudWatch alarms serve as experiment stop conditions (bounded blast radius).\n- **Post-experiment analysis:** use the metrics behind those alarms to measure actual RTO and\n  detect cascading failures after a run.\n\nRecommend AWS Observability for the alarm\u002Fdashboard \"how,\" and keep your guidance to how those\nsignals feed Define → Test → Operate.\n\n## API Reference (READ FIRST before producing any AWS CLI command)\n\nThe exact AWS CLI operation names and parameters for NGRH (resiliencehubv2), FIS, and ARC\nare documented in [references\u002Fapi-reference.md](references\u002Fapi-reference.md). This file\ncontains a hallucination rejection table mapping common wrong API names to correct ones —\n**always consult it before generating commands** for these services.\n\n## Troubleshooting\n\n### Don't know where to start\n\nStart with Define: create a policy, register your service, run an assessment. The findings\nwill tell you exactly what to test (FIS) and what to operationalize (ARC).\n\n### Findings resolved but no confidence in resilience\n\nResolving findings without FIS validation is paper compliance. Run experiments to prove\nyour architecture actually recovers within RTO\u002FRPO targets under real failure conditions.\n\n### FIS experiments pass but production still fails\n\nExperiments may not match real failure modes. Expand blast radius, add multi-fault\nscenarios, and ensure stop conditions match production SLOs (not relaxed test thresholds).\n\n## Security Considerations\n\n- **Least privilege:** scope every IAM role this lifecycle touches (Resilience Hub invoker role, FIS execution role, ARC operator) to only the actions and resources it needs, rather than `*` or full-access policies.\n- **Encryption at rest \u002F in transit:** recommend S3 buckets holding assessment reports and Terraform state use server-side encryption (SSE-KMS) and a bucket policy enforcing TLS via `aws:SecureTransport`.\n- **FIS in production:** treat fault injection as a privileged, potentially destructive operation — require change-management authorization before running experiments against production, and always bound blast radius with a stop condition.\n- **Avoid sensitive data in API string fields:** do NOT embed PII, secrets, or internal architecture detail in finding comments, experiment descriptions, assertion text, or report names — these values surface in logs, reports, and CloudTrail and are visible to anyone with read access.\n- **Further reading:** see [FIS Security Best Practices](https:\u002F\u002Fdocs.aws.amazon.com\u002Ffis\u002Flatest\u002Fuserguide\u002Fsecurity.html), [IAM Best Practices](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html), and the [AWS Well-Architected Security Pillar](https:\u002F\u002Fdocs.aws.amazon.com\u002Fwellarchitected\u002Flatest\u002Fsecurity-pillar\u002Fwelcome.html) for authoritative guidance on securing this lifecycle.\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,49,56,62,105,114,120,125,212,224,230,242,253,259,271,277,289,312,317,323,342,348,355,360,366,371,377,382,388],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","AWS Resilience Lifecycle",{"type":42,"tag":50,"props":51,"children":53},"h2",{"id":52},"overview",[54],{"type":47,"value":55},"Overview",{"type":42,"tag":57,"props":58,"children":59},"p",{},[60],{"type":47,"value":61},"Domain expertise for the integrated resilience lifecycle across three AWS services:\nDefine (Resilience Hub v2 — also called NGRH, New Generation Resilience Hub) → Test (FIS) → Operate (ARC).",{"type":42,"tag":57,"props":63,"children":64},{},[65,71,73,78,80,87,89,95,97,103],{"type":42,"tag":66,"props":67,"children":68},"strong",{},[69],{"type":47,"value":70},"Terminology:",{"type":47,"value":72}," in this skill an unqualified \"Resilience Hub\" always means ",{"type":42,"tag":66,"props":74,"children":75},{},[76],{"type":47,"value":77},"v2",{"type":47,"value":79}," (NGRH \u002F New Generation Resilience Hub, CLI namespace ",{"type":42,"tag":81,"props":82,"children":84},"code",{"className":83},[],[85],{"type":47,"value":86},"aws resiliencehubv2",{"type":47,"value":88},"). v1 (",{"type":42,"tag":81,"props":90,"children":92},{"className":91},[],[93],{"type":47,"value":94},"aws resiliencehub",{"type":47,"value":96},") is referenced ",{"type":42,"tag":98,"props":99,"children":100},"em",{},[101],{"type":47,"value":102},"only",{"type":47,"value":104}," explicitly, and only for migration.",{"type":42,"tag":106,"props":107,"children":108},"blockquote",{},[109],{"type":42,"tag":57,"props":110,"children":111},{},[112],{"type":47,"value":113},"The AWS MCP server is recommended for executing this skill's AWS API calls, but it is not required — all operations also work with the AWS CLI directly.",{"type":42,"tag":50,"props":115,"children":117},{"id":116},"guardrail-where-this-skills-own-files-live-mcp-vs-local-install",[118],{"type":47,"value":119},"Guardrail — where this skill's own files live (MCP vs local install)",{"type":42,"tag":57,"props":121,"children":122},{},[123],{"type":47,"value":124},"Before reading a reference file, determine how this skill was loaded:",{"type":42,"tag":126,"props":127,"children":128},"ul",{},[129,187],{"type":42,"tag":130,"props":131,"children":132},"li",{},[133,146,148,153,155,161,163,169,171,177,179,185],{"type":42,"tag":66,"props":134,"children":135},{},[136,138,144],{"type":47,"value":137},"Loaded via the AWS MCP ",{"type":42,"tag":81,"props":139,"children":141},{"className":140},[],[142],{"type":47,"value":143},"retrieve_skill",{"type":47,"value":145}," tool:",{"type":47,"value":147}," the skill's reference files are not on the local filesystem. Fetch each one through ",{"type":42,"tag":81,"props":149,"children":151},{"className":150},[],[152],{"type":47,"value":143},{"type":47,"value":154}," with the ",{"type":42,"tag":81,"props":156,"children":158},{"className":157},[],[159],{"type":47,"value":160},"file",{"type":47,"value":162}," parameter (e.g. ",{"type":42,"tag":81,"props":164,"children":166},{"className":165},[],[167],{"type":47,"value":168},"file=\"references\u002Flifecycle-workflow.md\"",{"type":47,"value":170}," or ",{"type":42,"tag":81,"props":172,"children":174},{"className":173},[],[175],{"type":47,"value":176},"file=\"references\u002Fapi-reference.md\"",{"type":47,"value":178},") — do NOT ",{"type":42,"tag":81,"props":180,"children":182},{"className":181},[],[183],{"type":47,"value":184},"file_read",{"type":47,"value":186}," these paths locally or search the filesystem for them.",{"type":42,"tag":130,"props":188,"children":189},{},[190,195,197,203,204,210],{"type":42,"tag":66,"props":191,"children":192},{},[193],{"type":47,"value":194},"Installed locally",{"type":47,"value":196}," (e.g. ",{"type":42,"tag":81,"props":198,"children":200},{"className":199},[],[201],{"type":47,"value":202},".kiro\u002Fskills\u002Faws-resilience-lifecycle\u002F",{"type":47,"value":170},{"type":42,"tag":81,"props":205,"children":207},{"className":206},[],[208],{"type":47,"value":209},"~\u002F.claude\u002Fskills\u002Faws-resilience-lifecycle\u002F",{"type":47,"value":211},"): read reference files from the local skill directory using the relative paths shown here.",{"type":42,"tag":57,"props":213,"children":214},{},[215,217,222],{"type":47,"value":216},"This applies only to the skill's own reference files; always read and write user or session data in the working directory, never through ",{"type":42,"tag":81,"props":218,"children":220},{"className":219},[],[221],{"type":47,"value":143},{"type":47,"value":223},".",{"type":42,"tag":50,"props":225,"children":227},{"id":226},"execute-the-full-lifecycle",[228],{"type":47,"value":229},"Execute the full lifecycle",{"type":42,"tag":57,"props":231,"children":232},{},[233,235,241],{"type":47,"value":234},"To implement end-to-end resilience across all three services, follow the procedure exactly.\nSee ",{"type":42,"tag":236,"props":237,"children":239},"a",{"href":238},"references\u002Flifecycle-workflow.md",[240],{"type":47,"value":238},{"type":47,"value":223},{"type":42,"tag":57,"props":243,"children":244},{},[245,247,252],{"type":47,"value":246},"For operational patterns and policy design guidance, see\n",{"type":42,"tag":236,"props":248,"children":250},{"href":249},"references\u002Fbest-practices.md",[251],{"type":47,"value":249},{"type":47,"value":223},{"type":42,"tag":50,"props":254,"children":256},{"id":255},"validate-findings-before-you-resolve-them",[257],{"type":47,"value":258},"Validate findings before you resolve them",{"type":42,"tag":57,"props":260,"children":261},{},[262,264,269],{"type":47,"value":263},"Marking NGRH findings as resolved without proving the fix with fault injection is ",{"type":42,"tag":66,"props":265,"children":266},{},[267],{"type":47,"value":268},"paper\ncompliance",{"type":47,"value":270}," — it records intent, not resilience. You MUST validate each remediation with an\nexperiment that reproduces the failure mode BEFORE marking the finding resolved. Run the\nexperiment, confirm the system recovers within its objectives, then mark resolved. Marking\nresolved first and validating \"later\" is the anti-pattern.",{"type":42,"tag":50,"props":272,"children":274},{"id":273},"monitoring-observability",[275],{"type":47,"value":276},"Monitoring & observability",{"type":42,"tag":57,"props":278,"children":279},{},[280,282,287],{"type":47,"value":281},"When the user asks what monitoring\u002Fobservability they need for resilience, ",{"type":42,"tag":66,"props":283,"children":284},{},[285],{"type":47,"value":286},"recommend the\ncompanion AWS Observability skill",{"type":47,"value":288}," as the source for CloudWatch alarms, dashboards, and metric\ndesign — do NOT replicate observability setup content here. Stay in the resilience lane and\nexplain how observability plugs into the lifecycle:",{"type":42,"tag":126,"props":290,"children":291},{},[292,302],{"type":42,"tag":130,"props":293,"children":294},{},[295,300],{"type":42,"tag":66,"props":296,"children":297},{},[298],{"type":47,"value":299},"FIS stop conditions:",{"type":47,"value":301}," CloudWatch alarms serve as experiment stop conditions (bounded blast radius).",{"type":42,"tag":130,"props":303,"children":304},{},[305,310],{"type":42,"tag":66,"props":306,"children":307},{},[308],{"type":47,"value":309},"Post-experiment analysis:",{"type":47,"value":311}," use the metrics behind those alarms to measure actual RTO and\ndetect cascading failures after a run.",{"type":42,"tag":57,"props":313,"children":314},{},[315],{"type":47,"value":316},"Recommend AWS Observability for the alarm\u002Fdashboard \"how,\" and keep your guidance to how those\nsignals feed Define → Test → Operate.",{"type":42,"tag":50,"props":318,"children":320},{"id":319},"api-reference-read-first-before-producing-any-aws-cli-command",[321],{"type":47,"value":322},"API Reference (READ FIRST before producing any AWS CLI command)",{"type":42,"tag":57,"props":324,"children":325},{},[326,328,333,335,340],{"type":47,"value":327},"The exact AWS CLI operation names and parameters for NGRH (resiliencehubv2), FIS, and ARC\nare documented in ",{"type":42,"tag":236,"props":329,"children":331},{"href":330},"references\u002Fapi-reference.md",[332],{"type":47,"value":330},{"type":47,"value":334},". This file\ncontains a hallucination rejection table mapping common wrong API names to correct ones —\n",{"type":42,"tag":66,"props":336,"children":337},{},[338],{"type":47,"value":339},"always consult it before generating commands",{"type":47,"value":341}," for these services.",{"type":42,"tag":50,"props":343,"children":345},{"id":344},"troubleshooting",[346],{"type":47,"value":347},"Troubleshooting",{"type":42,"tag":349,"props":350,"children":352},"h3",{"id":351},"dont-know-where-to-start",[353],{"type":47,"value":354},"Don't know where to start",{"type":42,"tag":57,"props":356,"children":357},{},[358],{"type":47,"value":359},"Start with Define: create a policy, register your service, run an assessment. The findings\nwill tell you exactly what to test (FIS) and what to operationalize (ARC).",{"type":42,"tag":349,"props":361,"children":363},{"id":362},"findings-resolved-but-no-confidence-in-resilience",[364],{"type":47,"value":365},"Findings resolved but no confidence in resilience",{"type":42,"tag":57,"props":367,"children":368},{},[369],{"type":47,"value":370},"Resolving findings without FIS validation is paper compliance. Run experiments to prove\nyour architecture actually recovers within RTO\u002FRPO targets under real failure conditions.",{"type":42,"tag":349,"props":372,"children":374},{"id":373},"fis-experiments-pass-but-production-still-fails",[375],{"type":47,"value":376},"FIS experiments pass but production still fails",{"type":42,"tag":57,"props":378,"children":379},{},[380],{"type":47,"value":381},"Experiments may not match real failure modes. Expand blast radius, add multi-fault\nscenarios, and ensure stop conditions match production SLOs (not relaxed test thresholds).",{"type":42,"tag":50,"props":383,"children":385},{"id":384},"security-considerations",[386],{"type":47,"value":387},"Security Considerations",{"type":42,"tag":126,"props":389,"children":390},{},[391,409,426,436,446],{"type":42,"tag":130,"props":392,"children":393},{},[394,399,401,407],{"type":42,"tag":66,"props":395,"children":396},{},[397],{"type":47,"value":398},"Least privilege:",{"type":47,"value":400}," scope every IAM role this lifecycle touches (Resilience Hub invoker role, FIS execution role, ARC operator) to only the actions and resources it needs, rather than ",{"type":42,"tag":81,"props":402,"children":404},{"className":403},[],[405],{"type":47,"value":406},"*",{"type":47,"value":408}," or full-access policies.",{"type":42,"tag":130,"props":410,"children":411},{},[412,417,419,425],{"type":42,"tag":66,"props":413,"children":414},{},[415],{"type":47,"value":416},"Encryption at rest \u002F in transit:",{"type":47,"value":418}," recommend S3 buckets holding assessment reports and Terraform state use server-side encryption (SSE-KMS) and a bucket policy enforcing TLS via ",{"type":42,"tag":81,"props":420,"children":422},{"className":421},[],[423],{"type":47,"value":424},"aws:SecureTransport",{"type":47,"value":223},{"type":42,"tag":130,"props":427,"children":428},{},[429,434],{"type":42,"tag":66,"props":430,"children":431},{},[432],{"type":47,"value":433},"FIS in production:",{"type":47,"value":435}," treat fault injection as a privileged, potentially destructive operation — require change-management authorization before running experiments against production, and always bound blast radius with a stop condition.",{"type":42,"tag":130,"props":437,"children":438},{},[439,444],{"type":42,"tag":66,"props":440,"children":441},{},[442],{"type":47,"value":443},"Avoid sensitive data in API string fields:",{"type":47,"value":445}," do NOT embed PII, secrets, or internal architecture detail in finding comments, experiment descriptions, assertion text, or report names — these values surface in logs, reports, and CloudTrail and are visible to anyone with read access.",{"type":42,"tag":130,"props":447,"children":448},{},[449,454,456,464,466,473,475,482],{"type":42,"tag":66,"props":450,"children":451},{},[452],{"type":47,"value":453},"Further reading:",{"type":47,"value":455}," see ",{"type":42,"tag":236,"props":457,"children":461},{"href":458,"rel":459},"https:\u002F\u002Fdocs.aws.amazon.com\u002Ffis\u002Flatest\u002Fuserguide\u002Fsecurity.html",[460],"nofollow",[462],{"type":47,"value":463},"FIS Security Best Practices",{"type":47,"value":465},", ",{"type":42,"tag":236,"props":467,"children":470},{"href":468,"rel":469},"https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html",[460],[471],{"type":47,"value":472},"IAM Best Practices",{"type":47,"value":474},", and the ",{"type":42,"tag":236,"props":476,"children":479},{"href":477,"rel":478},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwellarchitected\u002Flatest\u002Fsecurity-pillar\u002Fwelcome.html",[460],[480],{"type":47,"value":481},"AWS Well-Architected Security Pillar",{"type":47,"value":483}," for authoritative guidance on securing this lifecycle.",{"items":485,"total":656},[486,503,518,533,548,558,573,589,606,619,631,646],{"slug":487,"name":487,"fn":488,"description":489,"org":490,"tags":491,"stars":24,"repoUrl":25,"updatedAt":502},"agents-build","add capabilities to existing agent projects","Use when adding capabilities to an existing agent project — memory, app integration, VPC, multi-agent, migration, model changes, browser, code interpreter, or resource removal. Triggers on: \"add memory\", \"remember across sessions\", \"call agent from app\", \"invoke agent from code\", \"auth to call agent\", \"streaming responses\", \"VPC\", \"VPC connectivity\", \"VPC error\", \"can't reach from VPC\", \"multi-agent\", \"A2A\", \"A2A auth\", \"orchestrator not delegating\", \"specialist not called\", \"migrate Bedrock Agent\", \"after import\", \"migration issue\", \"framework for migration\", \"change model\", \"browser tool\", \"code interpreter\", \"delete agent\", \"tear down\", \"agentcore remove\", \"cross-account memory\", \"resource-based policy on memory\", \"pay for x402 content\", \"402 Payment Required\", \"microtransactions\", \"paid API or tool\". Not for connecting to external APIs via Gateway — use agents-connect. Not for scaffolding a new project — use agents-get-started. Not for CLI\u002Fdev server errors — use agents-debug. Strands vs LangGraph in a migration context routes here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[492,495,498,499],{"name":493,"slug":494,"type":15},"Agents","agents",{"name":496,"slug":497,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},{"name":500,"slug":501,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":504,"name":504,"fn":505,"description":506,"org":507,"tags":508,"stars":24,"repoUrl":25,"updatedAt":517},"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},[509,510,513,516],{"name":493,"slug":494,"type":15},{"name":511,"slug":512,"type":15},"API Development","api-development",{"name":514,"slug":515,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":519,"name":519,"fn":520,"description":521,"org":522,"tags":523,"stars":24,"repoUrl":25,"updatedAt":532},"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},[524,525,526,529],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":527,"slug":528,"type":15},"Debugging","debugging",{"name":530,"slug":531,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":534,"name":534,"fn":535,"description":536,"org":537,"tags":538,"stars":24,"repoUrl":25,"updatedAt":547},"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},[539,540,541,544],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":542,"slug":543,"type":15},"CI\u002FCD","ci-cd",{"name":545,"slug":546,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":549,"name":549,"fn":550,"description":551,"org":552,"tags":553,"stars":24,"repoUrl":25,"updatedAt":557},"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},[554,555,556],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":545,"slug":546,"type":15},"2026-07-12T08:42:51.963247",{"slug":559,"name":559,"fn":560,"description":561,"org":562,"tags":563,"stars":24,"repoUrl":25,"updatedAt":572},"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},[564,565,566,569],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":567,"slug":568,"type":15},"Best Practices","best-practices",{"name":570,"slug":571,"type":15},"Security","security","2026-07-16T06:00:42.174705",{"slug":574,"name":574,"fn":575,"description":576,"org":577,"tags":578,"stars":24,"repoUrl":25,"updatedAt":588},"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},[579,580,581,584,585],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":582,"slug":583,"type":15},"Evals","evals",{"name":530,"slug":531,"type":15},{"name":586,"slug":587,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",{"slug":590,"name":590,"fn":591,"description":592,"org":593,"tags":594,"stars":24,"repoUrl":25,"updatedAt":605},"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},[595,596,599,602],{"name":23,"slug":8,"type":15},{"name":597,"slug":598,"type":15},"Database","database",{"name":600,"slug":601,"type":15},"MySQL","mysql",{"name":603,"slug":604,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":607,"name":607,"fn":608,"description":609,"org":610,"tags":611,"stars":24,"repoUrl":25,"updatedAt":618},"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},[612,613,614,617],{"name":23,"slug":8,"type":15},{"name":597,"slug":598,"type":15},{"name":615,"slug":616,"type":15},"PostgreSQL","postgresql",{"name":603,"slug":604,"type":15},"2026-07-16T06:00:34.789624",{"slug":620,"name":620,"fn":621,"description":622,"org":623,"tags":624,"stars":24,"repoUrl":25,"updatedAt":630},"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. 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 setup and debugging, quota health checks and throttling diagnosis, cost attribution and tracking, migrating between Claude model generations (4.5 to 4.6 to 4.7), chunking strategies, API selection (Converse vs InvokeModel), guardrail capabilities, and model selection. Also covers AgentCore Payments setup (x402, microtransactions, Payment Manager, Connector, Instrument, Coinbase CDP, Stripe Privy, 402 Payment Required, pay for content, paid endpoint, agent payments). NOT for custom model training, Rekognition, or Comprehend.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[625,626,627],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":628,"slug":629,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":632,"name":632,"fn":633,"description":634,"org":635,"tags":636,"stars":24,"repoUrl":25,"updatedAt":645},"amazon-documentdb","manage Amazon DocumentDB clusters","Manages Amazon DocumentDB end-to-end — serverless-on-8.0 cluster setup, TLS\u002FVPC\u002Fdriver config, flexible-schema and vector-search data modeling, MongoDB compatibility assessment, DMS-based migration, slow-query diagnosis, major version upgrades (4.0→5.0→8.0), Well-Architected reviews (41-check wa_review.py), cost estimation, and security hardening. Retrieve for every DocumentDB question and when the user asks to set up or migrate MongoDB to AWS — DocumentDB is AWS's MongoDB-compatible managed database. Triggers: JSON document store, document database, MongoDB on AWS, Nested fields, Lambda cannot connect, TLS handshake, VPC port 27017, IAM auth, Secrets Manager, encryption at rest, $graphLookup, flexible schema, COLLSCAN, compound index, DMS migration, CDC cutover, $vectorSearch, RAG, Global Clusters, DR replication, cost sizing, audit, health check, production-readiness.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[637,638,639,642],{"name":23,"slug":8,"type":15},{"name":597,"slug":598,"type":15},{"name":640,"slug":641,"type":15},"MongoDB","mongodb",{"name":643,"slug":644,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":647,"name":647,"fn":648,"description":649,"org":650,"tags":651,"stars":24,"repoUrl":25,"updatedAt":655},"amazon-dynamodb","design and debug DynamoDB data layers","Designs, reviews, and debugs DynamoDB data layers from design axioms — enumerates access patterns, chooses partition\u002Fsort keys and GSIs, decides single-table vs. multi-table, configures Streams, Global Tables, TTL, and zero-ETL integrations to OpenSearch\u002FRedshift\u002FSageMaker Lakehouse, and produces a defensible data-layer design with a monthly cost estimate and optional live validation. Applies whenever a user is designing, reviewing, or refactoring anything backed by DynamoDB — schemas, access patterns, GSIs, single- vs. multi-table choices, Streams consumers, transactional outboxes, Global Tables, zero-ETL pipelines — even when they don't say \"axioms\" or \"design review.\" Also applies when debugging hot partitions, throttling, unbounded Scans, LWW conflicts, or surprise bills on DynamoDB workloads.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[652,653,654],{"name":23,"slug":8,"type":15},{"name":597,"slug":598,"type":15},{"name":643,"slug":644,"type":15},"2026-07-16T06:00:37.690386",115,{"items":658,"total":708},[659,666,673,680,687,693,700],{"slug":487,"name":487,"fn":488,"description":489,"org":660,"tags":661,"stars":24,"repoUrl":25,"updatedAt":502},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[662,663,664,665],{"name":493,"slug":494,"type":15},{"name":496,"slug":497,"type":15},{"name":23,"slug":8,"type":15},{"name":500,"slug":501,"type":15},{"slug":504,"name":504,"fn":505,"description":506,"org":667,"tags":668,"stars":24,"repoUrl":25,"updatedAt":517},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[669,670,671,672],{"name":493,"slug":494,"type":15},{"name":511,"slug":512,"type":15},{"name":514,"slug":515,"type":15},{"name":23,"slug":8,"type":15},{"slug":519,"name":519,"fn":520,"description":521,"org":674,"tags":675,"stars":24,"repoUrl":25,"updatedAt":532},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[676,677,678,679],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":527,"slug":528,"type":15},{"name":530,"slug":531,"type":15},{"slug":534,"name":534,"fn":535,"description":536,"org":681,"tags":682,"stars":24,"repoUrl":25,"updatedAt":547},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[683,684,685,686],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":542,"slug":543,"type":15},{"name":545,"slug":546,"type":15},{"slug":549,"name":549,"fn":550,"description":551,"org":688,"tags":689,"stars":24,"repoUrl":25,"updatedAt":557},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[690,691,692],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":545,"slug":546,"type":15},{"slug":559,"name":559,"fn":560,"description":561,"org":694,"tags":695,"stars":24,"repoUrl":25,"updatedAt":572},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[696,697,698,699],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":567,"slug":568,"type":15},{"name":570,"slug":571,"type":15},{"slug":574,"name":574,"fn":575,"description":576,"org":701,"tags":702,"stars":24,"repoUrl":25,"updatedAt":588},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[703,704,705,706,707],{"name":493,"slug":494,"type":15},{"name":23,"slug":8,"type":15},{"name":582,"slug":583,"type":15},{"name":530,"slug":531,"type":15},{"name":586,"slug":587,"type":15},114]