[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-amazon-ses":3,"mdc--evb1z6-key":35,"related-repo-aws-amazon-ses":338,"related-org-aws-amazon-ses":442},{"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},"amazon-ses","configure Amazon SES for email","Configures Amazon SES V2 for production email sending — including domain identity creation, DKIM\u002FSPF\u002FDMARC authentication, one-shot DNS record presentation, and Route 53 automation — for developers setting up or troubleshooting SES domain verification and deliverability. Applicable when developers need to send emails from their domain via SES, verify a domain identity, configure email authentication, troubleshoot DKIM verification issues, or ensure their sending setup follows best practices. Not for email-address-only verification, Mail Manager inbound routing, SNS, Pinpoint, or WorkMail.",{"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},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"DNS","dns",{"name":20,"slug":8,"type":15},"AWS",{"name":22,"slug":23,"type":15},"Email","email",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-08-14T04:52:01.438926",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\u002Fmessaging-and-streaming-skills\u002Famazon-ses","---\nname: amazon-ses\ndescription: \"Configures Amazon SES V2 for production email sending — including domain identity creation, DKIM\u002FSPF\u002FDMARC authentication, one-shot DNS record presentation, and Route 53 automation — for developers setting up or troubleshooting SES domain verification and deliverability. Applicable when developers need to send emails from their domain via SES, verify a domain identity, configure email authentication, troubleshoot DKIM verification issues, or ensure their sending setup follows best practices. Not for email-address-only verification, Mail Manager inbound routing, SNS, Pinpoint, or WorkMail.\"\nversion: 1\n---\n\n# Amazon SES\n\n> **Recommended**: Use the [AWS MCP Server](https:\u002F\u002Fdocs.aws.amazon.com\u002Faws-mcp\u002Flatest\u002Fuserguide\u002Fwhat-is-mcp-server.html) with SES permissions for sandboxed execution and CloudTrail audit logging.\n> **Without MCP**: All operations use standard AWS CLI syntax (`aws sesv2 ...`).\n\n## Overview\n\nThis skill helps developers and DevOps engineers configure Amazon SES for production email sending. It targets users who are not email authentication experts — guiding them through complete domain setup following AWS best practices without requiring deep knowledge of DKIM, SPF, or DMARC.\n\n## Routing\n\n| If the user wants to... | Read |\n|-------------------------|------|\n| Set up a domain for sending, configure email authentication, or troubleshoot DKIM | [Setting up SES domain identity](references\u002Fsetting-up-ses-domain-identity.md) |\n\n## Security\n\n- Use IAM roles with ephemeral credentials (STS) — never long-lived access keys\n- Scope IAM permissions to specific SES actions per workflow (see reference files for required permissions)\n- Enable CloudTrail for SES API call auditing\n- DMARC `p=none` is monitoring only — plan progression to `p=quarantine` after confirming alignment\n- Never hardcode credentials, endpoints, or secrets in examples\n\n## Critical Rules\n\n- **MUST** create a domain identity (not email identity) for production sending\n- **MUST** configure custom MAIL FROM subdomain for SPF alignment\n- **MUST** configure DMARC TXT record (`p=none` minimum) for domain alignment\n- **MUST** present all DNS records together in one batch\n- **MUST** ask user for preferred MAIL FROM subdomain (do not assume a default)\n- **SHOULD** check if Route 53 hosts the domain and offer automatic DNS creation\n- **SHOULD NOT** claim 72-hour wait — verification typically completes in minutes once DNS propagates\n\n## Additional Resources\n\n- [SES Domain Verification](https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fcreating-identities.html)\n- [DKIM in SES](https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fsend-email-authentication-dkim.html)\n- [Custom MAIL FROM](https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fmail-from.html)\n- [DMARC Authentication](https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fsend-email-authentication-dmarc.html)\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,49,92,99,104,110,155,161,207,213,289,295],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Amazon SES",{"type":42,"tag":50,"props":51,"children":52},"blockquote",{},[53],{"type":42,"tag":54,"props":55,"children":56},"p",{},[57,63,65,74,76,81,83,90],{"type":42,"tag":58,"props":59,"children":60},"strong",{},[61],{"type":47,"value":62},"Recommended",{"type":47,"value":64},": Use the ",{"type":42,"tag":66,"props":67,"children":71},"a",{"href":68,"rel":69},"https:\u002F\u002Fdocs.aws.amazon.com\u002Faws-mcp\u002Flatest\u002Fuserguide\u002Fwhat-is-mcp-server.html",[70],"nofollow",[72],{"type":47,"value":73},"AWS MCP Server",{"type":47,"value":75}," with SES permissions for sandboxed execution and CloudTrail audit logging.\n",{"type":42,"tag":58,"props":77,"children":78},{},[79],{"type":47,"value":80},"Without MCP",{"type":47,"value":82},": All operations use standard AWS CLI syntax (",{"type":42,"tag":84,"props":85,"children":87},"code",{"className":86},[],[88],{"type":47,"value":89},"aws sesv2 ...",{"type":47,"value":91},").",{"type":42,"tag":93,"props":94,"children":96},"h2",{"id":95},"overview",[97],{"type":47,"value":98},"Overview",{"type":42,"tag":54,"props":100,"children":101},{},[102],{"type":47,"value":103},"This skill helps developers and DevOps engineers configure Amazon SES for production email sending. It targets users who are not email authentication experts — guiding them through complete domain setup following AWS best practices without requiring deep knowledge of DKIM, SPF, or DMARC.",{"type":42,"tag":93,"props":105,"children":107},{"id":106},"routing",[108],{"type":47,"value":109},"Routing",{"type":42,"tag":111,"props":112,"children":113},"table",{},[114,133],{"type":42,"tag":115,"props":116,"children":117},"thead",{},[118],{"type":42,"tag":119,"props":120,"children":121},"tr",{},[122,128],{"type":42,"tag":123,"props":124,"children":125},"th",{},[126],{"type":47,"value":127},"If the user wants to...",{"type":42,"tag":123,"props":129,"children":130},{},[131],{"type":47,"value":132},"Read",{"type":42,"tag":134,"props":135,"children":136},"tbody",{},[137],{"type":42,"tag":119,"props":138,"children":139},{},[140,146],{"type":42,"tag":141,"props":142,"children":143},"td",{},[144],{"type":47,"value":145},"Set up a domain for sending, configure email authentication, or troubleshoot DKIM",{"type":42,"tag":141,"props":147,"children":148},{},[149],{"type":42,"tag":66,"props":150,"children":152},{"href":151},"references\u002Fsetting-up-ses-domain-identity.md",[153],{"type":47,"value":154},"Setting up SES domain identity",{"type":42,"tag":93,"props":156,"children":158},{"id":157},"security",[159],{"type":47,"value":160},"Security",{"type":42,"tag":162,"props":163,"children":164},"ul",{},[165,171,176,181,202],{"type":42,"tag":166,"props":167,"children":168},"li",{},[169],{"type":47,"value":170},"Use IAM roles with ephemeral credentials (STS) — never long-lived access keys",{"type":42,"tag":166,"props":172,"children":173},{},[174],{"type":47,"value":175},"Scope IAM permissions to specific SES actions per workflow (see reference files for required permissions)",{"type":42,"tag":166,"props":177,"children":178},{},[179],{"type":47,"value":180},"Enable CloudTrail for SES API call auditing",{"type":42,"tag":166,"props":182,"children":183},{},[184,186,192,194,200],{"type":47,"value":185},"DMARC ",{"type":42,"tag":84,"props":187,"children":189},{"className":188},[],[190],{"type":47,"value":191},"p=none",{"type":47,"value":193}," is monitoring only — plan progression to ",{"type":42,"tag":84,"props":195,"children":197},{"className":196},[],[198],{"type":47,"value":199},"p=quarantine",{"type":47,"value":201}," after confirming alignment",{"type":42,"tag":166,"props":203,"children":204},{},[205],{"type":47,"value":206},"Never hardcode credentials, endpoints, or secrets in examples",{"type":42,"tag":93,"props":208,"children":210},{"id":209},"critical-rules",[211],{"type":47,"value":212},"Critical Rules",{"type":42,"tag":162,"props":214,"children":215},{},[216,226,235,251,260,269,279],{"type":42,"tag":166,"props":217,"children":218},{},[219,224],{"type":42,"tag":58,"props":220,"children":221},{},[222],{"type":47,"value":223},"MUST",{"type":47,"value":225}," create a domain identity (not email identity) for production sending",{"type":42,"tag":166,"props":227,"children":228},{},[229,233],{"type":42,"tag":58,"props":230,"children":231},{},[232],{"type":47,"value":223},{"type":47,"value":234}," configure custom MAIL FROM subdomain for SPF alignment",{"type":42,"tag":166,"props":236,"children":237},{},[238,242,244,249],{"type":42,"tag":58,"props":239,"children":240},{},[241],{"type":47,"value":223},{"type":47,"value":243}," configure DMARC TXT record (",{"type":42,"tag":84,"props":245,"children":247},{"className":246},[],[248],{"type":47,"value":191},{"type":47,"value":250}," minimum) for domain alignment",{"type":42,"tag":166,"props":252,"children":253},{},[254,258],{"type":42,"tag":58,"props":255,"children":256},{},[257],{"type":47,"value":223},{"type":47,"value":259}," present all DNS records together in one batch",{"type":42,"tag":166,"props":261,"children":262},{},[263,267],{"type":42,"tag":58,"props":264,"children":265},{},[266],{"type":47,"value":223},{"type":47,"value":268}," ask user for preferred MAIL FROM subdomain (do not assume a default)",{"type":42,"tag":166,"props":270,"children":271},{},[272,277],{"type":42,"tag":58,"props":273,"children":274},{},[275],{"type":47,"value":276},"SHOULD",{"type":47,"value":278}," check if Route 53 hosts the domain and offer automatic DNS creation",{"type":42,"tag":166,"props":280,"children":281},{},[282,287],{"type":42,"tag":58,"props":283,"children":284},{},[285],{"type":47,"value":286},"SHOULD NOT",{"type":47,"value":288}," claim 72-hour wait — verification typically completes in minutes once DNS propagates",{"type":42,"tag":93,"props":290,"children":292},{"id":291},"additional-resources",[293],{"type":47,"value":294},"Additional Resources",{"type":42,"tag":162,"props":296,"children":297},{},[298,308,318,328],{"type":42,"tag":166,"props":299,"children":300},{},[301],{"type":42,"tag":66,"props":302,"children":305},{"href":303,"rel":304},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fcreating-identities.html",[70],[306],{"type":47,"value":307},"SES Domain Verification",{"type":42,"tag":166,"props":309,"children":310},{},[311],{"type":42,"tag":66,"props":312,"children":315},{"href":313,"rel":314},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fsend-email-authentication-dkim.html",[70],[316],{"type":47,"value":317},"DKIM in SES",{"type":42,"tag":166,"props":319,"children":320},{},[321],{"type":42,"tag":66,"props":322,"children":325},{"href":323,"rel":324},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fmail-from.html",[70],[326],{"type":47,"value":327},"Custom MAIL FROM",{"type":42,"tag":166,"props":329,"children":330},{},[331],{"type":42,"tag":66,"props":332,"children":335},{"href":333,"rel":334},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fses\u002Flatest\u002Fdg\u002Fsend-email-authentication-dmarc.html",[70],[336],{"type":47,"value":337},"DMARC Authentication",{"items":339,"total":441},[340,357,372,387,402,412,425],{"slug":341,"name":341,"fn":342,"description":343,"org":344,"tags":345,"stars":24,"repoUrl":25,"updatedAt":356},"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\", \"payments middleware for my agent\", \"integrate x402 payments with the agent I'm building\", \"enable my agent project with x402 payments\". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI\u002Fdev-server errors: use agents-debug. Runtime x402 payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[346,349,352,353],{"name":347,"slug":348,"type":15},"Agents","agents",{"name":350,"slug":351,"type":15},"Automation","automation",{"name":20,"slug":8,"type":15},{"name":354,"slug":355,"type":15},"Engineering","engineering","2026-08-07T04:38:08.981896",{"slug":358,"name":358,"fn":359,"description":360,"org":361,"tags":362,"stars":24,"repoUrl":25,"updatedAt":371},"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},[363,364,367,370],{"name":347,"slug":348,"type":15},{"name":365,"slug":366,"type":15},"API Development","api-development",{"name":368,"slug":369,"type":15},"Authentication","authentication",{"name":20,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":373,"name":373,"fn":374,"description":375,"org":376,"tags":377,"stars":24,"repoUrl":25,"updatedAt":386},"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},[378,379,380,383],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":381,"slug":382,"type":15},"Debugging","debugging",{"name":384,"slug":385,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":388,"name":388,"fn":389,"description":390,"org":391,"tags":392,"stars":24,"repoUrl":25,"updatedAt":401},"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},[393,394,395,398],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":396,"slug":397,"type":15},"CI\u002FCD","ci-cd",{"name":399,"slug":400,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":403,"name":403,"fn":404,"description":405,"org":406,"tags":407,"stars":24,"repoUrl":25,"updatedAt":411},"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},[408,409,410],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":399,"slug":400,"type":15},"2026-07-12T08:42:51.963247",{"slug":413,"name":413,"fn":414,"description":415,"org":416,"tags":417,"stars":24,"repoUrl":25,"updatedAt":424},"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},[418,419,420,423],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":421,"slug":422,"type":15},"Best Practices","best-practices",{"name":160,"slug":157,"type":15},"2026-07-16T06:00:42.174705",{"slug":426,"name":426,"fn":427,"description":428,"org":429,"tags":430,"stars":24,"repoUrl":25,"updatedAt":440},"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},[431,432,433,436,437],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":434,"slug":435,"type":15},"Evals","evals",{"name":384,"slug":385,"type":15},{"name":438,"slug":439,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",120,{"items":443,"total":564},[444,451,458,465,472,478,485,493,507,524,537,549],{"slug":341,"name":341,"fn":342,"description":343,"org":445,"tags":446,"stars":24,"repoUrl":25,"updatedAt":356},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[447,448,449,450],{"name":347,"slug":348,"type":15},{"name":350,"slug":351,"type":15},{"name":20,"slug":8,"type":15},{"name":354,"slug":355,"type":15},{"slug":358,"name":358,"fn":359,"description":360,"org":452,"tags":453,"stars":24,"repoUrl":25,"updatedAt":371},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[454,455,456,457],{"name":347,"slug":348,"type":15},{"name":365,"slug":366,"type":15},{"name":368,"slug":369,"type":15},{"name":20,"slug":8,"type":15},{"slug":373,"name":373,"fn":374,"description":375,"org":459,"tags":460,"stars":24,"repoUrl":25,"updatedAt":386},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[461,462,463,464],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":381,"slug":382,"type":15},{"name":384,"slug":385,"type":15},{"slug":388,"name":388,"fn":389,"description":390,"org":466,"tags":467,"stars":24,"repoUrl":25,"updatedAt":401},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[468,469,470,471],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":396,"slug":397,"type":15},{"name":399,"slug":400,"type":15},{"slug":403,"name":403,"fn":404,"description":405,"org":473,"tags":474,"stars":24,"repoUrl":25,"updatedAt":411},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[475,476,477],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":399,"slug":400,"type":15},{"slug":413,"name":413,"fn":414,"description":415,"org":479,"tags":480,"stars":24,"repoUrl":25,"updatedAt":424},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[481,482,483,484],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":421,"slug":422,"type":15},{"name":160,"slug":157,"type":15},{"slug":426,"name":426,"fn":427,"description":428,"org":486,"tags":487,"stars":24,"repoUrl":25,"updatedAt":440},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[488,489,490,491,492],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":434,"slug":435,"type":15},{"name":384,"slug":385,"type":15},{"name":438,"slug":439,"type":15},{"slug":494,"name":494,"fn":495,"description":496,"org":497,"tags":498,"stars":24,"repoUrl":25,"updatedAt":506},"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},[499,500,501,504],{"name":347,"slug":348,"type":15},{"name":350,"slug":351,"type":15},{"name":502,"slug":503,"type":15},"Payments","payments",{"name":505,"slug":505,"type":15},"x402","2026-08-10T04:16:31.844309",{"slug":508,"name":508,"fn":509,"description":510,"org":511,"tags":512,"stars":24,"repoUrl":25,"updatedAt":523},"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},[513,514,517,520],{"name":20,"slug":8,"type":15},{"name":515,"slug":516,"type":15},"Database","database",{"name":518,"slug":519,"type":15},"MySQL","mysql",{"name":521,"slug":522,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":525,"name":525,"fn":526,"description":527,"org":528,"tags":529,"stars":24,"repoUrl":25,"updatedAt":536},"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},[530,531,532,535],{"name":20,"slug":8,"type":15},{"name":515,"slug":516,"type":15},{"name":533,"slug":534,"type":15},"PostgreSQL","postgresql",{"name":521,"slug":522,"type":15},"2026-07-16T06:00:34.789624",{"slug":538,"name":538,"fn":539,"description":540,"org":541,"tags":542,"stars":24,"repoUrl":25,"updatedAt":548},"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},[543,544,545],{"name":347,"slug":348,"type":15},{"name":20,"slug":8,"type":15},{"name":546,"slug":547,"type":15},"LLM","llm","2026-08-07T04:38:13.03499",{"slug":550,"name":550,"fn":551,"description":552,"org":553,"tags":554,"stars":24,"repoUrl":25,"updatedAt":563},"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},[555,556,557,560],{"name":20,"slug":8,"type":15},{"name":515,"slug":516,"type":15},{"name":558,"slug":559,"type":15},"MongoDB","mongodb",{"name":561,"slug":562,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",122]