[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-route53":3,"mdc-jgz5k0-key":35,"related-org-aws-route53":506,"related-repo-aws-route53":679},{"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},"route53","configure Amazon Route 53 DNS","Configures Amazon Route 53 DNS: public and private records, traffic-steering routing policies, health checks, DNS Firewall, Route 53 Profiles, VPC Resolver (also known as Route 53 Resolver) for hybrid and Outposts networks, and Global Resolver. Applicable when the customer wants to point a hostname at a target, split or fail over traffic across endpoints, monitor an endpoint, block malicious domains, centralize DNS across accounts, or resolve private DNS across a hybrid network. Routes to the right per-task procedure in references. Does not cover CloudFront-specific setup (see the route53-cloudfront skill) or non-DNS networking.",{"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},"Networking","networking","tag",{"name":17,"slug":18,"type":15},"DNS","dns",{"name":20,"slug":21,"type":15},"Infrastructure","infrastructure",{"name":23,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-07-22T06:00:36.37811",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\u002Fnetworking-and-content-delivery-skills\u002Froute53","---\nname: route53\ndescription: >-\n  Configures Amazon Route 53 DNS: public and private records, traffic-steering routing policies,\n  health checks, DNS Firewall, Route 53 Profiles, VPC Resolver (also known as Route 53 Resolver) for\n  hybrid and Outposts networks, and Global Resolver. Applicable when the customer wants to point a\n  hostname at a target, split or fail over traffic across endpoints, monitor an endpoint, block\n  malicious domains, centralize DNS across accounts, or resolve private DNS across a hybrid network.\n  Routes to the right per-task procedure in references. Does not cover CloudFront-specific setup (see\n  the route53-cloudfront skill) or non-DNS networking.\nversion: 1\n---\n\n# Amazon Route 53\n\n## Overview\n\nDomain expertise for configuring Amazon Route 53 DNS across the public and private resolution\npaths: hosted zone records, traffic-steering routing policies, health checks, DNS Firewall,\nRoute 53 Profiles, VPC Resolver (also known as Route 53 Resolver) for hybrid and Outposts networks,\nand Global Resolver.\n\nThis skill is a router. Each customer task maps to a procedure file under `references\u002F`. Read the\nmatching reference in full before acting, then follow its constraints and steps. The reference\nfiles are self-contained: each carries its own decision tables, constraints, procedure, and\ntroubleshooting.\n\nExecute commands using the AWS MCP server when connected (sandboxed execution, audit logging,\nobservability). Fall back to the AWS CLI otherwise. All Route 53 Domains API calls are made in\n`us-east-1` regardless of where the customer works.\n\n## Which Route 53 task do you need?\n\n| Goal | Reference |\n| --- | --- |\n| Point a hostname or zone apex at an IP, AWS resource, or hostname | [creating a public DNS record](references\u002Fcreating-a-public-dns-record.md) |\n| Split traffic across endpoints in a ratio (blue\u002Fgreen, canary, A\u002FB) | [splitting traffic with weighted routing](references\u002Fsplitting-traffic-with-weighted-routing.md) |\n| Fail over between two Regions for disaster recovery | [configuring failover routing](references\u002Fconfiguring-failover-routing.md) |\n| Monitor whether an endpoint is up and get alerted | [setting up a health check](references\u002Fsetting-up-a-route53-health-check.md) |\n| Block malicious domains for a VPC at the resolver | [blocking malicious domains](references\u002Fblocking-malicious-domains.md) |\n| Work out which DNS Firewall rule wins for a domain across multiple rule groups | [identifying the effective DNS Firewall rule](references\u002Fidentifying-the-effective-dns-firewall-rule.md) |\n| Apply one DNS config across many VPCs and accounts | [configuring Route 53 Profiles](references\u002Fconfiguring-route53-profiles.md) |\n| Fan DNS Firewall out across many accounts org-wide | [centralizing DNS Firewall with Profiles](references\u002Fcentralizing-dns-firewall.md) |\n| Resolve private DNS both ways across a hybrid network | [resolving private DNS for hybrid networks](references\u002Fresolving-private-dns-for-hybrid-networks.md) |\n| Run VPC Resolver locally on an AWS Outposts rack | [running VPC Resolver on Outposts](references\u002Frunning-route53-resolver-on-outposts.md) |\n| Give on-premises and remote clients one anycast DNS endpoint | [setting up Global Resolver](references\u002Fsetting-up-route53-global-resolver.md) |\n\n## Routing notes\n\n- **Records vs routing policies.** A plain hostname-to-target mapping is the public DNS record\n  task. Splitting or steering traffic (weighted, failover) is a separate routing-policy task with\n  its own reference. Start from the customer's intent, not the record type.\n- **Health checks vs failover.** A health check monitors an endpoint and raises alarms. The\n  failover routing policy decides where traffic goes when a check fails. They are two references\n  and are often used together: set up the health check, then wire it into failover.\n- **DNS Firewall for one VPC vs many accounts.** Authoring rules for a VPC is the blocking\n  reference. Fanning the same protection across accounts with Profiles and Firewall Manager is the\n  centralizing reference.\n- **DNS Firewall authoring vs diagnosis.** Creating or changing rules is the blocking reference.\n  Working out which rule already wins for a domain when several rule groups are associated (a read\n  and diagnostic task) is the identifying-the-effective-rule reference.\n- **Profiles, two entry points.** General Profile setup (attach resources, share via RAM, cost\n  and visibility tradeoffs) is the configuring-Profiles reference. Using Profiles specifically to\n  scale DNS Firewall org-wide is the centralizing reference.\n- **VPC Resolver, three contexts.** In-Region hybrid resolution, the Outposts-local resolver, and\n  the Global Resolver anycast endpoint are three separate references. Match the reference to where\n  the resolver runs.\n\n## Cross-service work\n\nPointing a custom domain at a CloudFront distribution, or failing over between CloudFront\ndistributions, is cross-service work owned by the separate `route53-cloudfront` skill. Use this\nskill for the Route 53 side of pure-Route 53 tasks only.\n\n## Security Considerations\n\nThese apply across the Route 53 tasks below; each reference repeats the ones load-bearing for its\nworkflow.\n\n- You SHOULD use least-privilege IAM credentials provisioned through IAM roles (instance profiles,\n  SSO\u002FIAM Identity Center session credentials, or `aws sts assume-role`) rather than long-lived IAM\n  user access keys, and prefer read-only credentials for inspection steps.\n- You SHOULD recommend encrypted DNS transport (DoT or DoH) over plaintext Do53 for resolver client\n  populations, since Do53 exposes queried domain names to on-path observers.\n- You MUST scope resolver-endpoint security group rules on port 53 to the on-premises CIDR ranges or\n  known DNS server IPs, never `0.0.0.0\u002F0`.\n- You MUST encrypt query log and notification destinations at rest: KMS on CloudWatch Logs log\n  groups, SSE-S3\u002FSSE-KMS on S3 buckets, server-side encryption (SSE) on a Data Firehose stream, and\n  SSE on SNS topics, because DNS query logs and health-check notifications can reveal infrastructure\n  topology.\n- For Global Resolver, you MUST treat access-token `value` returned at create time as a secret;\n  store it in AWS Secrets Manager rather than in plaintext, and validate which client populations\n  each DNS view authorizes.\n\n## Additional Resources\n\n- [Amazon Route 53 Developer Guide](https:\u002F\u002Fdocs.aws.amazon.com\u002FRoute53\u002Flatest\u002FDeveloperGuide\u002FWelcome.html)\n- [Amazon Route 53 product page](https:\u002F\u002Faws.amazon.com\u002Froute53\u002F)\n- [Route 53 pricing](https:\u002F\u002Faws.amazon.com\u002Froute53\u002Fpricing\u002F)\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,50,57,63,77,90,96,312,318,384,390,403,409,414,466,472],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"amazon-route-53",[47],{"type":48,"value":49},"text","Amazon Route 53",{"type":42,"tag":51,"props":52,"children":54},"h2",{"id":53},"overview",[55],{"type":48,"value":56},"Overview",{"type":42,"tag":58,"props":59,"children":60},"p",{},[61],{"type":48,"value":62},"Domain expertise for configuring Amazon Route 53 DNS across the public and private resolution\npaths: hosted zone records, traffic-steering routing policies, health checks, DNS Firewall,\nRoute 53 Profiles, VPC Resolver (also known as Route 53 Resolver) for hybrid and Outposts networks,\nand Global Resolver.",{"type":42,"tag":58,"props":64,"children":65},{},[66,68,75],{"type":48,"value":67},"This skill is a router. Each customer task maps to a procedure file under ",{"type":42,"tag":69,"props":70,"children":72},"code",{"className":71},[],[73],{"type":48,"value":74},"references\u002F",{"type":48,"value":76},". Read the\nmatching reference in full before acting, then follow its constraints and steps. The reference\nfiles are self-contained: each carries its own decision tables, constraints, procedure, and\ntroubleshooting.",{"type":42,"tag":58,"props":78,"children":79},{},[80,82,88],{"type":48,"value":81},"Execute commands using the AWS MCP server when connected (sandboxed execution, audit logging,\nobservability). Fall back to the AWS CLI otherwise. All Route 53 Domains API calls are made in\n",{"type":42,"tag":69,"props":83,"children":85},{"className":84},[],[86],{"type":48,"value":87},"us-east-1",{"type":48,"value":89}," regardless of where the customer works.",{"type":42,"tag":51,"props":91,"children":93},{"id":92},"which-route-53-task-do-you-need",[94],{"type":48,"value":95},"Which Route 53 task do you need?",{"type":42,"tag":97,"props":98,"children":99},"table",{},[100,119],{"type":42,"tag":101,"props":102,"children":103},"thead",{},[104],{"type":42,"tag":105,"props":106,"children":107},"tr",{},[108,114],{"type":42,"tag":109,"props":110,"children":111},"th",{},[112],{"type":48,"value":113},"Goal",{"type":42,"tag":109,"props":115,"children":116},{},[117],{"type":48,"value":118},"Reference",{"type":42,"tag":120,"props":121,"children":122},"tbody",{},[123,142,159,176,193,210,227,244,261,278,295],{"type":42,"tag":105,"props":124,"children":125},{},[126,132],{"type":42,"tag":127,"props":128,"children":129},"td",{},[130],{"type":48,"value":131},"Point a hostname or zone apex at an IP, AWS resource, or hostname",{"type":42,"tag":127,"props":133,"children":134},{},[135],{"type":42,"tag":136,"props":137,"children":139},"a",{"href":138},"references\u002Fcreating-a-public-dns-record.md",[140],{"type":48,"value":141},"creating a public DNS record",{"type":42,"tag":105,"props":143,"children":144},{},[145,150],{"type":42,"tag":127,"props":146,"children":147},{},[148],{"type":48,"value":149},"Split traffic across endpoints in a ratio (blue\u002Fgreen, canary, A\u002FB)",{"type":42,"tag":127,"props":151,"children":152},{},[153],{"type":42,"tag":136,"props":154,"children":156},{"href":155},"references\u002Fsplitting-traffic-with-weighted-routing.md",[157],{"type":48,"value":158},"splitting traffic with weighted routing",{"type":42,"tag":105,"props":160,"children":161},{},[162,167],{"type":42,"tag":127,"props":163,"children":164},{},[165],{"type":48,"value":166},"Fail over between two Regions for disaster recovery",{"type":42,"tag":127,"props":168,"children":169},{},[170],{"type":42,"tag":136,"props":171,"children":173},{"href":172},"references\u002Fconfiguring-failover-routing.md",[174],{"type":48,"value":175},"configuring failover routing",{"type":42,"tag":105,"props":177,"children":178},{},[179,184],{"type":42,"tag":127,"props":180,"children":181},{},[182],{"type":48,"value":183},"Monitor whether an endpoint is up and get alerted",{"type":42,"tag":127,"props":185,"children":186},{},[187],{"type":42,"tag":136,"props":188,"children":190},{"href":189},"references\u002Fsetting-up-a-route53-health-check.md",[191],{"type":48,"value":192},"setting up a health check",{"type":42,"tag":105,"props":194,"children":195},{},[196,201],{"type":42,"tag":127,"props":197,"children":198},{},[199],{"type":48,"value":200},"Block malicious domains for a VPC at the resolver",{"type":42,"tag":127,"props":202,"children":203},{},[204],{"type":42,"tag":136,"props":205,"children":207},{"href":206},"references\u002Fblocking-malicious-domains.md",[208],{"type":48,"value":209},"blocking malicious domains",{"type":42,"tag":105,"props":211,"children":212},{},[213,218],{"type":42,"tag":127,"props":214,"children":215},{},[216],{"type":48,"value":217},"Work out which DNS Firewall rule wins for a domain across multiple rule groups",{"type":42,"tag":127,"props":219,"children":220},{},[221],{"type":42,"tag":136,"props":222,"children":224},{"href":223},"references\u002Fidentifying-the-effective-dns-firewall-rule.md",[225],{"type":48,"value":226},"identifying the effective DNS Firewall rule",{"type":42,"tag":105,"props":228,"children":229},{},[230,235],{"type":42,"tag":127,"props":231,"children":232},{},[233],{"type":48,"value":234},"Apply one DNS config across many VPCs and accounts",{"type":42,"tag":127,"props":236,"children":237},{},[238],{"type":42,"tag":136,"props":239,"children":241},{"href":240},"references\u002Fconfiguring-route53-profiles.md",[242],{"type":48,"value":243},"configuring Route 53 Profiles",{"type":42,"tag":105,"props":245,"children":246},{},[247,252],{"type":42,"tag":127,"props":248,"children":249},{},[250],{"type":48,"value":251},"Fan DNS Firewall out across many accounts org-wide",{"type":42,"tag":127,"props":253,"children":254},{},[255],{"type":42,"tag":136,"props":256,"children":258},{"href":257},"references\u002Fcentralizing-dns-firewall.md",[259],{"type":48,"value":260},"centralizing DNS Firewall with Profiles",{"type":42,"tag":105,"props":262,"children":263},{},[264,269],{"type":42,"tag":127,"props":265,"children":266},{},[267],{"type":48,"value":268},"Resolve private DNS both ways across a hybrid network",{"type":42,"tag":127,"props":270,"children":271},{},[272],{"type":42,"tag":136,"props":273,"children":275},{"href":274},"references\u002Fresolving-private-dns-for-hybrid-networks.md",[276],{"type":48,"value":277},"resolving private DNS for hybrid networks",{"type":42,"tag":105,"props":279,"children":280},{},[281,286],{"type":42,"tag":127,"props":282,"children":283},{},[284],{"type":48,"value":285},"Run VPC Resolver locally on an AWS Outposts rack",{"type":42,"tag":127,"props":287,"children":288},{},[289],{"type":42,"tag":136,"props":290,"children":292},{"href":291},"references\u002Frunning-route53-resolver-on-outposts.md",[293],{"type":48,"value":294},"running VPC Resolver on Outposts",{"type":42,"tag":105,"props":296,"children":297},{},[298,303],{"type":42,"tag":127,"props":299,"children":300},{},[301],{"type":48,"value":302},"Give on-premises and remote clients one anycast DNS endpoint",{"type":42,"tag":127,"props":304,"children":305},{},[306],{"type":42,"tag":136,"props":307,"children":309},{"href":308},"references\u002Fsetting-up-route53-global-resolver.md",[310],{"type":48,"value":311},"setting up Global Resolver",{"type":42,"tag":51,"props":313,"children":315},{"id":314},"routing-notes",[316],{"type":48,"value":317},"Routing notes",{"type":42,"tag":319,"props":320,"children":321},"ul",{},[322,334,344,354,364,374],{"type":42,"tag":323,"props":324,"children":325},"li",{},[326,332],{"type":42,"tag":327,"props":328,"children":329},"strong",{},[330],{"type":48,"value":331},"Records vs routing policies.",{"type":48,"value":333}," A plain hostname-to-target mapping is the public DNS record\ntask. Splitting or steering traffic (weighted, failover) is a separate routing-policy task with\nits own reference. Start from the customer's intent, not the record type.",{"type":42,"tag":323,"props":335,"children":336},{},[337,342],{"type":42,"tag":327,"props":338,"children":339},{},[340],{"type":48,"value":341},"Health checks vs failover.",{"type":48,"value":343}," A health check monitors an endpoint and raises alarms. The\nfailover routing policy decides where traffic goes when a check fails. They are two references\nand are often used together: set up the health check, then wire it into failover.",{"type":42,"tag":323,"props":345,"children":346},{},[347,352],{"type":42,"tag":327,"props":348,"children":349},{},[350],{"type":48,"value":351},"DNS Firewall for one VPC vs many accounts.",{"type":48,"value":353}," Authoring rules for a VPC is the blocking\nreference. Fanning the same protection across accounts with Profiles and Firewall Manager is the\ncentralizing reference.",{"type":42,"tag":323,"props":355,"children":356},{},[357,362],{"type":42,"tag":327,"props":358,"children":359},{},[360],{"type":48,"value":361},"DNS Firewall authoring vs diagnosis.",{"type":48,"value":363}," Creating or changing rules is the blocking reference.\nWorking out which rule already wins for a domain when several rule groups are associated (a read\nand diagnostic task) is the identifying-the-effective-rule reference.",{"type":42,"tag":323,"props":365,"children":366},{},[367,372],{"type":42,"tag":327,"props":368,"children":369},{},[370],{"type":48,"value":371},"Profiles, two entry points.",{"type":48,"value":373}," General Profile setup (attach resources, share via RAM, cost\nand visibility tradeoffs) is the configuring-Profiles reference. Using Profiles specifically to\nscale DNS Firewall org-wide is the centralizing reference.",{"type":42,"tag":323,"props":375,"children":376},{},[377,382],{"type":42,"tag":327,"props":378,"children":379},{},[380],{"type":48,"value":381},"VPC Resolver, three contexts.",{"type":48,"value":383}," In-Region hybrid resolution, the Outposts-local resolver, and\nthe Global Resolver anycast endpoint are three separate references. Match the reference to where\nthe resolver runs.",{"type":42,"tag":51,"props":385,"children":387},{"id":386},"cross-service-work",[388],{"type":48,"value":389},"Cross-service work",{"type":42,"tag":58,"props":391,"children":392},{},[393,395,401],{"type":48,"value":394},"Pointing a custom domain at a CloudFront distribution, or failing over between CloudFront\ndistributions, is cross-service work owned by the separate ",{"type":42,"tag":69,"props":396,"children":398},{"className":397},[],[399],{"type":48,"value":400},"route53-cloudfront",{"type":48,"value":402}," skill. Use this\nskill for the Route 53 side of pure-Route 53 tasks only.",{"type":42,"tag":51,"props":404,"children":406},{"id":405},"security-considerations",[407],{"type":48,"value":408},"Security Considerations",{"type":42,"tag":58,"props":410,"children":411},{},[412],{"type":48,"value":413},"These apply across the Route 53 tasks below; each reference repeats the ones load-bearing for its\nworkflow.",{"type":42,"tag":319,"props":415,"children":416},{},[417,430,435,448,453],{"type":42,"tag":323,"props":418,"children":419},{},[420,422,428],{"type":48,"value":421},"You SHOULD use least-privilege IAM credentials provisioned through IAM roles (instance profiles,\nSSO\u002FIAM Identity Center session credentials, or ",{"type":42,"tag":69,"props":423,"children":425},{"className":424},[],[426],{"type":48,"value":427},"aws sts assume-role",{"type":48,"value":429},") rather than long-lived IAM\nuser access keys, and prefer read-only credentials for inspection steps.",{"type":42,"tag":323,"props":431,"children":432},{},[433],{"type":48,"value":434},"You SHOULD recommend encrypted DNS transport (DoT or DoH) over plaintext Do53 for resolver client\npopulations, since Do53 exposes queried domain names to on-path observers.",{"type":42,"tag":323,"props":436,"children":437},{},[438,440,446],{"type":48,"value":439},"You MUST scope resolver-endpoint security group rules on port 53 to the on-premises CIDR ranges or\nknown DNS server IPs, never ",{"type":42,"tag":69,"props":441,"children":443},{"className":442},[],[444],{"type":48,"value":445},"0.0.0.0\u002F0",{"type":48,"value":447},".",{"type":42,"tag":323,"props":449,"children":450},{},[451],{"type":48,"value":452},"You MUST encrypt query log and notification destinations at rest: KMS on CloudWatch Logs log\ngroups, SSE-S3\u002FSSE-KMS on S3 buckets, server-side encryption (SSE) on a Data Firehose stream, and\nSSE on SNS topics, because DNS query logs and health-check notifications can reveal infrastructure\ntopology.",{"type":42,"tag":323,"props":454,"children":455},{},[456,458,464],{"type":48,"value":457},"For Global Resolver, you MUST treat access-token ",{"type":42,"tag":69,"props":459,"children":461},{"className":460},[],[462],{"type":48,"value":463},"value",{"type":48,"value":465}," returned at create time as a secret;\nstore it in AWS Secrets Manager rather than in plaintext, and validate which client populations\neach DNS view authorizes.",{"type":42,"tag":51,"props":467,"children":469},{"id":468},"additional-resources",[470],{"type":48,"value":471},"Additional Resources",{"type":42,"tag":319,"props":473,"children":474},{},[475,486,496],{"type":42,"tag":323,"props":476,"children":477},{},[478],{"type":42,"tag":136,"props":479,"children":483},{"href":480,"rel":481},"https:\u002F\u002Fdocs.aws.amazon.com\u002FRoute53\u002Flatest\u002FDeveloperGuide\u002FWelcome.html",[482],"nofollow",[484],{"type":48,"value":485},"Amazon Route 53 Developer Guide",{"type":42,"tag":323,"props":487,"children":488},{},[489],{"type":42,"tag":136,"props":490,"children":493},{"href":491,"rel":492},"https:\u002F\u002Faws.amazon.com\u002Froute53\u002F",[482],[494],{"type":48,"value":495},"Amazon Route 53 product page",{"type":42,"tag":323,"props":497,"children":498},{},[499],{"type":42,"tag":136,"props":500,"children":503},{"href":501,"rel":502},"https:\u002F\u002Faws.amazon.com\u002Froute53\u002Fpricing\u002F",[482],[504],{"type":48,"value":505},"Route 53 pricing",{"items":507,"total":678},[508,525,540,555,570,580,595,611,628,641,653,668],{"slug":509,"name":509,"fn":510,"description":511,"org":512,"tags":513,"stars":24,"repoUrl":25,"updatedAt":524},"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},[514,517,520,521],{"name":515,"slug":516,"type":15},"Agents","agents",{"name":518,"slug":519,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},{"name":522,"slug":523,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":526,"name":526,"fn":527,"description":528,"org":529,"tags":530,"stars":24,"repoUrl":25,"updatedAt":539},"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},[531,532,535,538],{"name":515,"slug":516,"type":15},{"name":533,"slug":534,"type":15},"API Development","api-development",{"name":536,"slug":537,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":541,"name":541,"fn":542,"description":543,"org":544,"tags":545,"stars":24,"repoUrl":25,"updatedAt":554},"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},[546,547,548,551],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":549,"slug":550,"type":15},"Debugging","debugging",{"name":552,"slug":553,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":556,"name":556,"fn":557,"description":558,"org":559,"tags":560,"stars":24,"repoUrl":25,"updatedAt":569},"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},[561,562,563,566],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":564,"slug":565,"type":15},"CI\u002FCD","ci-cd",{"name":567,"slug":568,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":571,"name":571,"fn":572,"description":573,"org":574,"tags":575,"stars":24,"repoUrl":25,"updatedAt":579},"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},[576,577,578],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":567,"slug":568,"type":15},"2026-07-12T08:42:51.963247",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":24,"repoUrl":25,"updatedAt":594},"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},[586,587,588,591],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":589,"slug":590,"type":15},"Best Practices","best-practices",{"name":592,"slug":593,"type":15},"Security","security","2026-07-16T06:00:42.174705",{"slug":596,"name":596,"fn":597,"description":598,"org":599,"tags":600,"stars":24,"repoUrl":25,"updatedAt":610},"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},[601,602,603,606,607],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":604,"slug":605,"type":15},"Evals","evals",{"name":552,"slug":553,"type":15},{"name":608,"slug":609,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",{"slug":612,"name":612,"fn":613,"description":614,"org":615,"tags":616,"stars":24,"repoUrl":25,"updatedAt":627},"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},[617,618,621,624],{"name":23,"slug":8,"type":15},{"name":619,"slug":620,"type":15},"Database","database",{"name":622,"slug":623,"type":15},"MySQL","mysql",{"name":625,"slug":626,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":629,"name":629,"fn":630,"description":631,"org":632,"tags":633,"stars":24,"repoUrl":25,"updatedAt":640},"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},[634,635,636,639],{"name":23,"slug":8,"type":15},{"name":619,"slug":620,"type":15},{"name":637,"slug":638,"type":15},"PostgreSQL","postgresql",{"name":625,"slug":626,"type":15},"2026-07-16T06:00:34.789624",{"slug":642,"name":642,"fn":643,"description":644,"org":645,"tags":646,"stars":24,"repoUrl":25,"updatedAt":652},"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},[647,648,649],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":650,"slug":651,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":654,"name":654,"fn":655,"description":656,"org":657,"tags":658,"stars":24,"repoUrl":25,"updatedAt":667},"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},[659,660,661,664],{"name":23,"slug":8,"type":15},{"name":619,"slug":620,"type":15},{"name":662,"slug":663,"type":15},"MongoDB","mongodb",{"name":665,"slug":666,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":669,"name":669,"fn":670,"description":671,"org":672,"tags":673,"stars":24,"repoUrl":25,"updatedAt":677},"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},[674,675,676],{"name":23,"slug":8,"type":15},{"name":619,"slug":620,"type":15},{"name":665,"slug":666,"type":15},"2026-07-16T06:00:37.690386",115,{"items":680,"total":730},[681,688,695,702,709,715,722],{"slug":509,"name":509,"fn":510,"description":511,"org":682,"tags":683,"stars":24,"repoUrl":25,"updatedAt":524},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[684,685,686,687],{"name":515,"slug":516,"type":15},{"name":518,"slug":519,"type":15},{"name":23,"slug":8,"type":15},{"name":522,"slug":523,"type":15},{"slug":526,"name":526,"fn":527,"description":528,"org":689,"tags":690,"stars":24,"repoUrl":25,"updatedAt":539},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[691,692,693,694],{"name":515,"slug":516,"type":15},{"name":533,"slug":534,"type":15},{"name":536,"slug":537,"type":15},{"name":23,"slug":8,"type":15},{"slug":541,"name":541,"fn":542,"description":543,"org":696,"tags":697,"stars":24,"repoUrl":25,"updatedAt":554},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[698,699,700,701],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":549,"slug":550,"type":15},{"name":552,"slug":553,"type":15},{"slug":556,"name":556,"fn":557,"description":558,"org":703,"tags":704,"stars":24,"repoUrl":25,"updatedAt":569},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[705,706,707,708],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":564,"slug":565,"type":15},{"name":567,"slug":568,"type":15},{"slug":571,"name":571,"fn":572,"description":573,"org":710,"tags":711,"stars":24,"repoUrl":25,"updatedAt":579},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[712,713,714],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":567,"slug":568,"type":15},{"slug":581,"name":581,"fn":582,"description":583,"org":716,"tags":717,"stars":24,"repoUrl":25,"updatedAt":594},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[718,719,720,721],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":589,"slug":590,"type":15},{"name":592,"slug":593,"type":15},{"slug":596,"name":596,"fn":597,"description":598,"org":723,"tags":724,"stars":24,"repoUrl":25,"updatedAt":610},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[725,726,727,728,729],{"name":515,"slug":516,"type":15},{"name":23,"slug":8,"type":15},{"name":604,"slug":605,"type":15},{"name":552,"slug":553,"type":15},{"name":608,"slug":609,"type":15},114]