[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-shieldadvanced":3,"mdc-azfhji-key":32,"related-repo-aws-shieldadvanced":518,"related-org-aws-shieldadvanced":622},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":21,"repoUrl":22,"updatedAt":23,"license":24,"forks":25,"topics":26,"repo":27,"sourceUrl":30,"mdContent":31},"shieldadvanced","configure AWS Shield Advanced DDoS protection","Configures AWS Shield Advanced for enhanced Distributed Denial of Service (DDoS) protection: subscribing accounts and adding resource protections, enabling automatic application layer (layer 7) mitigation through AWS WAF, configuring health-based detection with Route 53 health checks, setting up Shield Response Team (SRT) access and proactive engagement, reviewing DDoS events and requesting cost protection credits, and aggregating resources into protection groups. Applicable when the user wants stronger DDoS protection for internet-facing resources (CloudFront, Application or Network Load Balancers, Elastic IP addresses, Global Accelerator, or Route 53 hosted zones), wants expert help during an attack, or wants to recover attack-driven scaling charges. Routes to the right per-task procedure in references. Not applicable for authoring AWS WAF rules (waf skill), creating Route 53 health checks (route53 skill), or org-wide Shield Advanced rollout with Firewall Manager (firewallmanager skill).",{"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],{"name":13,"slug":14,"type":15},"Security","security","tag",{"name":17,"slug":18,"type":15},"Infrastructure","infrastructure",{"name":20,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-07-22T06:00:34.662217",null,157,[],{"repoUrl":22,"stars":21,"forks":25,"topics":28,"description":29},[],"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\u002Fshieldadvanced","---\nname: shieldadvanced\ndescription: >-\n  Configures AWS Shield Advanced for enhanced Distributed Denial of Service (DDoS) protection:\n  subscribing accounts and adding resource protections, enabling automatic application layer (layer 7)\n  mitigation through AWS WAF, configuring health-based detection with Route 53 health checks, setting\n  up Shield Response Team (SRT) access and proactive engagement, reviewing DDoS events and requesting\n  cost protection credits, and aggregating resources into protection groups. Applicable when the user\n  wants stronger DDoS protection for internet-facing resources (CloudFront, Application or Network\n  Load Balancers, Elastic IP addresses, Global Accelerator, or Route 53 hosted zones), wants expert\n  help during an attack, or wants to recover attack-driven scaling charges. Routes to the right\n  per-task procedure in references. Not applicable for authoring AWS WAF rules (waf skill), creating\n  Route 53 health checks (route53 skill), or org-wide Shield Advanced rollout with Firewall Manager\n  (firewallmanager skill).\nversion: 1\n---\n\n# AWS Shield Advanced\n\n## Overview\n\nDomain expertise for configuring AWS Shield Advanced, the paid tier that adds enhanced Distributed\nDenial of Service (DDoS) protection, automatic application layer mitigation, attack visibility, expert support, and\ncost protection on top of the always-on AWS Shield Standard. Covers subscribing and protecting\nresources, automatic application layer mitigation, health-based detection, Shield Response Team\n(SRT) access and proactive engagement, event review and cost protection credits, and protection\ngroups.\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. Shield Advanced is a global service: its\ncontrol-plane API calls run in `us-east-1`, so pass `--region us-east-1` on every `aws shield`\ncommand.\n\n## Which Shield Advanced task do you need?\n\n| Goal | Reference |\n| --- | --- |\n| Decide whether Shield Advanced is needed at all (vs Shield Standard + AWS WAF) | [deciding between Shield Standard and Advanced](references\u002Fdeciding-between-shield-standard-and-advanced.md) |\n| Subscribe an account and add resources to protection | [subscribing to Shield Advanced and protecting resources](references\u002Fsubscribing-to-shield-advanced-and-protecting-resources.md) |\n| Respond to layer 7 floods automatically through AWS WAF | [enabling automatic application layer mitigation](references\u002Fenabling-automatic-application-layer-mitigation.md) |\n| Feed resource health into detection with a Route 53 health check | [configuring health-based detection](references\u002Fconfiguring-health-based-detection.md) |\n| Get the Shield Response Team to act or reach out during an attack | [setting up SRT support and proactive engagement](references\u002Fsetting-up-srt-support-and-proactive-engagement.md) |\n| Review a DDoS event and recover attack-driven scaling charges | [reviewing DDoS events and requesting cost protection](references\u002Freviewing-ddos-events-and-requesting-cost-protection.md) |\n| Treat related resources as one unit for detection | [aggregating resources into protection groups](references\u002Faggregating-resources-into-protection-groups.md) |\n\n## Routing notes\n\n- **Decide before you subscribe.** Shield Advanced is a paid subscription that auto-renews on a\n  one-year commitment. Before subscribing, confirm the customer actually needs it: Shield Standard\n  (free, always on) plus AWS WAF rate-based rules and the AWS WAF Anti-DDoS managed rule group\n  (`AWSManagedRulesAntiDDoSRuleSet`) covers many layer 7 cases at lower cost. Route to the deciding\n  reference first when the customer has not made that call; route to the waf skill for the WAF rules\n  themselves.\n- **Subscribe and protect comes first.** A subscription protects nothing on its own; resources have\n  to be added explicitly. Every other task here assumes the resource is already subscribed and\n  protected. Run the subscribing reference before any of the others if the customer is starting\n  from scratch.\n- **Automatic mitigation vs health-based detection.** These are different controls and customers\n  conflate them. Automatic application layer mitigation deploys AWS WAF rules during a layer 7\n  attack. Health-based detection feeds a Route 53 health check into Shield Advanced's detection so it\n  reacts sooner. A customer can run either, both, or neither. Pick the reference that matches what they\n  actually want.\n- **Health check is also an SRT prerequisite.** Proactive engagement (SRT reaching out) requires a\n  Route 53 health check on the protected resource. If the customer wants proactive engagement,\n  configuring health-based detection is the groundwork. The SRT reference points back to the\n  health-based detection reference for that step.\n- **Protection groups are detection-only.** A protection group changes how Shield Advanced detects\n  across a set of resources. It does not apply shared mitigation; automatic mitigation still works per\n  resource. Use the protection-groups reference for detection tuning, not as a mitigation control.\n- **WAF rules, health checks, and org rollout live elsewhere.** Authoring the AWS WAF rules, the\n  rate-based rule, or the web ACL is the waf skill. Creating the Route 53 health check is the\n  route53 skill. Rolling Shield Advanced across an organization with Firewall Manager is the\n  firewallmanager skill. This skill wires Shield Advanced to those pieces; it does not build them.\n  AWS WAF is not optional alongside Shield Advanced: you SHOULD recommend an AWS WAF web ACL on\n  every internet-facing protected resource (CloudFront distributions and Application Load Balancers)\n  as defense in depth — Shield Advanced and AWS WAF are complementary layer 3\u002F4 and layer 7\n  controls, and the rate-based rule that AWS WAF provides is also what cost protection requires.\n\n## Logging and monitoring\n\nVisibility into both configuration changes and attack activity matters for every task here.\n\n- You SHOULD recommend enabling AWS CloudTrail so all Shield Advanced API calls (subscription,\n  protection, SRT, and protection-group changes) are logged for audit purposes.\n- You SHOULD recommend enabling SSE-KMS encryption on the CloudTrail log bucket and CloudWatch Logs\n  log group, since CloudTrail records sensitive API metadata (caller identities, resource ARNs,\n  parameters) that must be encrypted at rest.\n- You SHOULD recommend CloudWatch alarms on Shield Advanced metrics (for example `DDoSDetected` and\n  `DDoSAttackBitsPerSecond`) so operations staff are alerted when an event is detected.\n- You SHOULD recommend encrypting any SNS topics used for those alarms with SSE-KMS, since the\n  notifications carry sensitive event data.\n- You SHOULD recommend confirming that all SNS topic subscribers for Shield Advanced alarms are\n  authorized personnel approved to receive sensitive DDoS event notifications.\n\n## Security considerations\n\nShield Advanced setup creates IAM trust relationships and exposes log data, so call out the risks\nand the controls that contain them.\n\n- **SRT role is a third-party principal.** Granting SRT access creates an IAM role that\n  `drt.shield.amazonaws.com` assumes to act in the account. Scope its trust policy with an\n  `aws:SourceAccount` condition equal to the account ID to prevent confused-deputy assumption, grant\n  it only the actions it needs, and revoke it with `disassociate-drt-role` when no longer required.\n- **Log buckets shared with the SRT can leak data.** AWS WAF and access logs capture request URIs,\n  headers, and client IPs. Confirm those buckets have server-side encryption and carry no clear-text\n  PII or secrets before sharing them with the SRT.\n- **Least privilege for the operator.** Scope the caller's IAM permissions to the minimum each\n  procedure needs rather than broad Shield or administrator access.\n- **Audit trail.** Keep AWS CloudTrail enabled and logging `shield:*` calls so every configuration\n  change leaves a record.\n\n## Additional Resources\n\n- [AWS Shield Advanced overview (AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide)](https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fddos-overview.html)\n- [How AWS Shield works (AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide)](https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fddos-how-shield-works.html)\n- [AWS Shield Advanced pricing](https:\u002F\u002Faws.amazon.com\u002Fshield\u002Fpricing\u002F)\n",{"data":33,"body":35},{"name":4,"description":6,"version":34},1,{"type":36,"children":37},"root",[38,47,54,60,74,103,109,257,263,337,343,348,392,398,403,478,484],{"type":39,"tag":40,"props":41,"children":43},"element","h1",{"id":42},"aws-shield-advanced",[44],{"type":45,"value":46},"text","AWS Shield Advanced",{"type":39,"tag":48,"props":49,"children":51},"h2",{"id":50},"overview",[52],{"type":45,"value":53},"Overview",{"type":39,"tag":55,"props":56,"children":57},"p",{},[58],{"type":45,"value":59},"Domain expertise for configuring AWS Shield Advanced, the paid tier that adds enhanced Distributed\nDenial of Service (DDoS) protection, automatic application layer mitigation, attack visibility, expert support, and\ncost protection on top of the always-on AWS Shield Standard. Covers subscribing and protecting\nresources, automatic application layer mitigation, health-based detection, Shield Response Team\n(SRT) access and proactive engagement, event review and cost protection credits, and protection\ngroups.",{"type":39,"tag":55,"props":61,"children":62},{},[63,65,72],{"type":45,"value":64},"This skill is a router. Each customer task maps to a procedure file under ",{"type":39,"tag":66,"props":67,"children":69},"code",{"className":68},[],[70],{"type":45,"value":71},"references\u002F",{"type":45,"value":73},". 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":39,"tag":55,"props":75,"children":76},{},[77,79,85,87,93,95,101],{"type":45,"value":78},"Execute commands using the AWS MCP server when connected (sandboxed execution, audit logging,\nobservability). Fall back to the AWS CLI otherwise. Shield Advanced is a global service: its\ncontrol-plane API calls run in ",{"type":39,"tag":66,"props":80,"children":82},{"className":81},[],[83],{"type":45,"value":84},"us-east-1",{"type":45,"value":86},", so pass ",{"type":39,"tag":66,"props":88,"children":90},{"className":89},[],[91],{"type":45,"value":92},"--region us-east-1",{"type":45,"value":94}," on every ",{"type":39,"tag":66,"props":96,"children":98},{"className":97},[],[99],{"type":45,"value":100},"aws shield",{"type":45,"value":102},"\ncommand.",{"type":39,"tag":48,"props":104,"children":106},{"id":105},"which-shield-advanced-task-do-you-need",[107],{"type":45,"value":108},"Which Shield Advanced task do you need?",{"type":39,"tag":110,"props":111,"children":112},"table",{},[113,132],{"type":39,"tag":114,"props":115,"children":116},"thead",{},[117],{"type":39,"tag":118,"props":119,"children":120},"tr",{},[121,127],{"type":39,"tag":122,"props":123,"children":124},"th",{},[125],{"type":45,"value":126},"Goal",{"type":39,"tag":122,"props":128,"children":129},{},[130],{"type":45,"value":131},"Reference",{"type":39,"tag":133,"props":134,"children":135},"tbody",{},[136,155,172,189,206,223,240],{"type":39,"tag":118,"props":137,"children":138},{},[139,145],{"type":39,"tag":140,"props":141,"children":142},"td",{},[143],{"type":45,"value":144},"Decide whether Shield Advanced is needed at all (vs Shield Standard + AWS WAF)",{"type":39,"tag":140,"props":146,"children":147},{},[148],{"type":39,"tag":149,"props":150,"children":152},"a",{"href":151},"references\u002Fdeciding-between-shield-standard-and-advanced.md",[153],{"type":45,"value":154},"deciding between Shield Standard and Advanced",{"type":39,"tag":118,"props":156,"children":157},{},[158,163],{"type":39,"tag":140,"props":159,"children":160},{},[161],{"type":45,"value":162},"Subscribe an account and add resources to protection",{"type":39,"tag":140,"props":164,"children":165},{},[166],{"type":39,"tag":149,"props":167,"children":169},{"href":168},"references\u002Fsubscribing-to-shield-advanced-and-protecting-resources.md",[170],{"type":45,"value":171},"subscribing to Shield Advanced and protecting resources",{"type":39,"tag":118,"props":173,"children":174},{},[175,180],{"type":39,"tag":140,"props":176,"children":177},{},[178],{"type":45,"value":179},"Respond to layer 7 floods automatically through AWS WAF",{"type":39,"tag":140,"props":181,"children":182},{},[183],{"type":39,"tag":149,"props":184,"children":186},{"href":185},"references\u002Fenabling-automatic-application-layer-mitigation.md",[187],{"type":45,"value":188},"enabling automatic application layer mitigation",{"type":39,"tag":118,"props":190,"children":191},{},[192,197],{"type":39,"tag":140,"props":193,"children":194},{},[195],{"type":45,"value":196},"Feed resource health into detection with a Route 53 health check",{"type":39,"tag":140,"props":198,"children":199},{},[200],{"type":39,"tag":149,"props":201,"children":203},{"href":202},"references\u002Fconfiguring-health-based-detection.md",[204],{"type":45,"value":205},"configuring health-based detection",{"type":39,"tag":118,"props":207,"children":208},{},[209,214],{"type":39,"tag":140,"props":210,"children":211},{},[212],{"type":45,"value":213},"Get the Shield Response Team to act or reach out during an attack",{"type":39,"tag":140,"props":215,"children":216},{},[217],{"type":39,"tag":149,"props":218,"children":220},{"href":219},"references\u002Fsetting-up-srt-support-and-proactive-engagement.md",[221],{"type":45,"value":222},"setting up SRT support and proactive engagement",{"type":39,"tag":118,"props":224,"children":225},{},[226,231],{"type":39,"tag":140,"props":227,"children":228},{},[229],{"type":45,"value":230},"Review a DDoS event and recover attack-driven scaling charges",{"type":39,"tag":140,"props":232,"children":233},{},[234],{"type":39,"tag":149,"props":235,"children":237},{"href":236},"references\u002Freviewing-ddos-events-and-requesting-cost-protection.md",[238],{"type":45,"value":239},"reviewing DDoS events and requesting cost protection",{"type":39,"tag":118,"props":241,"children":242},{},[243,248],{"type":39,"tag":140,"props":244,"children":245},{},[246],{"type":45,"value":247},"Treat related resources as one unit for detection",{"type":39,"tag":140,"props":249,"children":250},{},[251],{"type":39,"tag":149,"props":252,"children":254},{"href":253},"references\u002Faggregating-resources-into-protection-groups.md",[255],{"type":45,"value":256},"aggregating resources into protection groups",{"type":39,"tag":48,"props":258,"children":260},{"id":259},"routing-notes",[261],{"type":45,"value":262},"Routing notes",{"type":39,"tag":264,"props":265,"children":266},"ul",{},[267,287,297,307,317,327],{"type":39,"tag":268,"props":269,"children":270},"li",{},[271,277,279,285],{"type":39,"tag":272,"props":273,"children":274},"strong",{},[275],{"type":45,"value":276},"Decide before you subscribe.",{"type":45,"value":278}," Shield Advanced is a paid subscription that auto-renews on a\none-year commitment. Before subscribing, confirm the customer actually needs it: Shield Standard\n(free, always on) plus AWS WAF rate-based rules and the AWS WAF Anti-DDoS managed rule group\n(",{"type":39,"tag":66,"props":280,"children":282},{"className":281},[],[283],{"type":45,"value":284},"AWSManagedRulesAntiDDoSRuleSet",{"type":45,"value":286},") covers many layer 7 cases at lower cost. Route to the deciding\nreference first when the customer has not made that call; route to the waf skill for the WAF rules\nthemselves.",{"type":39,"tag":268,"props":288,"children":289},{},[290,295],{"type":39,"tag":272,"props":291,"children":292},{},[293],{"type":45,"value":294},"Subscribe and protect comes first.",{"type":45,"value":296}," A subscription protects nothing on its own; resources have\nto be added explicitly. Every other task here assumes the resource is already subscribed and\nprotected. Run the subscribing reference before any of the others if the customer is starting\nfrom scratch.",{"type":39,"tag":268,"props":298,"children":299},{},[300,305],{"type":39,"tag":272,"props":301,"children":302},{},[303],{"type":45,"value":304},"Automatic mitigation vs health-based detection.",{"type":45,"value":306}," These are different controls and customers\nconflate them. Automatic application layer mitigation deploys AWS WAF rules during a layer 7\nattack. Health-based detection feeds a Route 53 health check into Shield Advanced's detection so it\nreacts sooner. A customer can run either, both, or neither. Pick the reference that matches what they\nactually want.",{"type":39,"tag":268,"props":308,"children":309},{},[310,315],{"type":39,"tag":272,"props":311,"children":312},{},[313],{"type":45,"value":314},"Health check is also an SRT prerequisite.",{"type":45,"value":316}," Proactive engagement (SRT reaching out) requires a\nRoute 53 health check on the protected resource. If the customer wants proactive engagement,\nconfiguring health-based detection is the groundwork. The SRT reference points back to the\nhealth-based detection reference for that step.",{"type":39,"tag":268,"props":318,"children":319},{},[320,325],{"type":39,"tag":272,"props":321,"children":322},{},[323],{"type":45,"value":324},"Protection groups are detection-only.",{"type":45,"value":326}," A protection group changes how Shield Advanced detects\nacross a set of resources. It does not apply shared mitigation; automatic mitigation still works per\nresource. Use the protection-groups reference for detection tuning, not as a mitigation control.",{"type":39,"tag":268,"props":328,"children":329},{},[330,335],{"type":39,"tag":272,"props":331,"children":332},{},[333],{"type":45,"value":334},"WAF rules, health checks, and org rollout live elsewhere.",{"type":45,"value":336}," Authoring the AWS WAF rules, the\nrate-based rule, or the web ACL is the waf skill. Creating the Route 53 health check is the\nroute53 skill. Rolling Shield Advanced across an organization with Firewall Manager is the\nfirewallmanager skill. This skill wires Shield Advanced to those pieces; it does not build them.\nAWS WAF is not optional alongside Shield Advanced: you SHOULD recommend an AWS WAF web ACL on\nevery internet-facing protected resource (CloudFront distributions and Application Load Balancers)\nas defense in depth — Shield Advanced and AWS WAF are complementary layer 3\u002F4 and layer 7\ncontrols, and the rate-based rule that AWS WAF provides is also what cost protection requires.",{"type":39,"tag":48,"props":338,"children":340},{"id":339},"logging-and-monitoring",[341],{"type":45,"value":342},"Logging and monitoring",{"type":39,"tag":55,"props":344,"children":345},{},[346],{"type":45,"value":347},"Visibility into both configuration changes and attack activity matters for every task here.",{"type":39,"tag":264,"props":349,"children":350},{},[351,356,361,382,387],{"type":39,"tag":268,"props":352,"children":353},{},[354],{"type":45,"value":355},"You SHOULD recommend enabling AWS CloudTrail so all Shield Advanced API calls (subscription,\nprotection, SRT, and protection-group changes) are logged for audit purposes.",{"type":39,"tag":268,"props":357,"children":358},{},[359],{"type":45,"value":360},"You SHOULD recommend enabling SSE-KMS encryption on the CloudTrail log bucket and CloudWatch Logs\nlog group, since CloudTrail records sensitive API metadata (caller identities, resource ARNs,\nparameters) that must be encrypted at rest.",{"type":39,"tag":268,"props":362,"children":363},{},[364,366,372,374,380],{"type":45,"value":365},"You SHOULD recommend CloudWatch alarms on Shield Advanced metrics (for example ",{"type":39,"tag":66,"props":367,"children":369},{"className":368},[],[370],{"type":45,"value":371},"DDoSDetected",{"type":45,"value":373}," and\n",{"type":39,"tag":66,"props":375,"children":377},{"className":376},[],[378],{"type":45,"value":379},"DDoSAttackBitsPerSecond",{"type":45,"value":381},") so operations staff are alerted when an event is detected.",{"type":39,"tag":268,"props":383,"children":384},{},[385],{"type":45,"value":386},"You SHOULD recommend encrypting any SNS topics used for those alarms with SSE-KMS, since the\nnotifications carry sensitive event data.",{"type":39,"tag":268,"props":388,"children":389},{},[390],{"type":45,"value":391},"You SHOULD recommend confirming that all SNS topic subscribers for Shield Advanced alarms are\nauthorized personnel approved to receive sensitive DDoS event notifications.",{"type":39,"tag":48,"props":393,"children":395},{"id":394},"security-considerations",[396],{"type":45,"value":397},"Security considerations",{"type":39,"tag":55,"props":399,"children":400},{},[401],{"type":45,"value":402},"Shield Advanced setup creates IAM trust relationships and exposes log data, so call out the risks\nand the controls that contain them.",{"type":39,"tag":264,"props":404,"children":405},{},[406,440,450,460],{"type":39,"tag":268,"props":407,"children":408},{},[409,414,416,422,424,430,432,438],{"type":39,"tag":272,"props":410,"children":411},{},[412],{"type":45,"value":413},"SRT role is a third-party principal.",{"type":45,"value":415}," Granting SRT access creates an IAM role that\n",{"type":39,"tag":66,"props":417,"children":419},{"className":418},[],[420],{"type":45,"value":421},"drt.shield.amazonaws.com",{"type":45,"value":423}," assumes to act in the account. Scope its trust policy with an\n",{"type":39,"tag":66,"props":425,"children":427},{"className":426},[],[428],{"type":45,"value":429},"aws:SourceAccount",{"type":45,"value":431}," condition equal to the account ID to prevent confused-deputy assumption, grant\nit only the actions it needs, and revoke it with ",{"type":39,"tag":66,"props":433,"children":435},{"className":434},[],[436],{"type":45,"value":437},"disassociate-drt-role",{"type":45,"value":439}," when no longer required.",{"type":39,"tag":268,"props":441,"children":442},{},[443,448],{"type":39,"tag":272,"props":444,"children":445},{},[446],{"type":45,"value":447},"Log buckets shared with the SRT can leak data.",{"type":45,"value":449}," AWS WAF and access logs capture request URIs,\nheaders, and client IPs. Confirm those buckets have server-side encryption and carry no clear-text\nPII or secrets before sharing them with the SRT.",{"type":39,"tag":268,"props":451,"children":452},{},[453,458],{"type":39,"tag":272,"props":454,"children":455},{},[456],{"type":45,"value":457},"Least privilege for the operator.",{"type":45,"value":459}," Scope the caller's IAM permissions to the minimum each\nprocedure needs rather than broad Shield or administrator access.",{"type":39,"tag":268,"props":461,"children":462},{},[463,468,470,476],{"type":39,"tag":272,"props":464,"children":465},{},[466],{"type":45,"value":467},"Audit trail.",{"type":45,"value":469}," Keep AWS CloudTrail enabled and logging ",{"type":39,"tag":66,"props":471,"children":473},{"className":472},[],[474],{"type":45,"value":475},"shield:*",{"type":45,"value":477}," calls so every configuration\nchange leaves a record.",{"type":39,"tag":48,"props":479,"children":481},{"id":480},"additional-resources",[482],{"type":45,"value":483},"Additional Resources",{"type":39,"tag":264,"props":485,"children":486},{},[487,498,508],{"type":39,"tag":268,"props":488,"children":489},{},[490],{"type":39,"tag":149,"props":491,"children":495},{"href":492,"rel":493},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fddos-overview.html",[494],"nofollow",[496],{"type":45,"value":497},"AWS Shield Advanced overview (AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide)",{"type":39,"tag":268,"props":499,"children":500},{},[501],{"type":39,"tag":149,"props":502,"children":505},{"href":503,"rel":504},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fddos-how-shield-works.html",[494],[506],{"type":45,"value":507},"How AWS Shield works (AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide)",{"type":39,"tag":268,"props":509,"children":510},{},[511],{"type":39,"tag":149,"props":512,"children":515},{"href":513,"rel":514},"https:\u002F\u002Faws.amazon.com\u002Fshield\u002Fpricing\u002F",[494],[516],{"type":45,"value":517},"AWS Shield Advanced pricing",{"items":519,"total":621},[520,537,552,567,582,592,605],{"slug":521,"name":521,"fn":522,"description":523,"org":524,"tags":525,"stars":21,"repoUrl":22,"updatedAt":536},"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},[526,529,532,533],{"name":527,"slug":528,"type":15},"Agents","agents",{"name":530,"slug":531,"type":15},"Automation","automation",{"name":20,"slug":8,"type":15},{"name":534,"slug":535,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":538,"name":538,"fn":539,"description":540,"org":541,"tags":542,"stars":21,"repoUrl":22,"updatedAt":551},"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},[543,544,547,550],{"name":527,"slug":528,"type":15},{"name":545,"slug":546,"type":15},"API Development","api-development",{"name":548,"slug":549,"type":15},"Authentication","authentication",{"name":20,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":553,"name":553,"fn":554,"description":555,"org":556,"tags":557,"stars":21,"repoUrl":22,"updatedAt":566},"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},[558,559,560,563],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":561,"slug":562,"type":15},"Debugging","debugging",{"name":564,"slug":565,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":21,"repoUrl":22,"updatedAt":581},"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},[573,574,575,578],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":576,"slug":577,"type":15},"CI\u002FCD","ci-cd",{"name":579,"slug":580,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":583,"name":583,"fn":584,"description":585,"org":586,"tags":587,"stars":21,"repoUrl":22,"updatedAt":591},"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},[588,589,590],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":579,"slug":580,"type":15},"2026-07-12T08:42:51.963247",{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":21,"repoUrl":22,"updatedAt":604},"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},[598,599,600,603],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":601,"slug":602,"type":15},"Best Practices","best-practices",{"name":13,"slug":14,"type":15},"2026-07-16T06:00:42.174705",{"slug":606,"name":606,"fn":607,"description":608,"org":609,"tags":610,"stars":21,"repoUrl":22,"updatedAt":620},"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},[611,612,613,616,617],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":614,"slug":615,"type":15},"Evals","evals",{"name":564,"slug":565,"type":15},{"name":618,"slug":619,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",114,{"items":623,"total":740},[624,631,638,645,652,658,665,673,690,703,715,730],{"slug":521,"name":521,"fn":522,"description":523,"org":625,"tags":626,"stars":21,"repoUrl":22,"updatedAt":536},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[627,628,629,630],{"name":527,"slug":528,"type":15},{"name":530,"slug":531,"type":15},{"name":20,"slug":8,"type":15},{"name":534,"slug":535,"type":15},{"slug":538,"name":538,"fn":539,"description":540,"org":632,"tags":633,"stars":21,"repoUrl":22,"updatedAt":551},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[634,635,636,637],{"name":527,"slug":528,"type":15},{"name":545,"slug":546,"type":15},{"name":548,"slug":549,"type":15},{"name":20,"slug":8,"type":15},{"slug":553,"name":553,"fn":554,"description":555,"org":639,"tags":640,"stars":21,"repoUrl":22,"updatedAt":566},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[641,642,643,644],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":561,"slug":562,"type":15},{"name":564,"slug":565,"type":15},{"slug":568,"name":568,"fn":569,"description":570,"org":646,"tags":647,"stars":21,"repoUrl":22,"updatedAt":581},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[648,649,650,651],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":576,"slug":577,"type":15},{"name":579,"slug":580,"type":15},{"slug":583,"name":583,"fn":584,"description":585,"org":653,"tags":654,"stars":21,"repoUrl":22,"updatedAt":591},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[655,656,657],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":579,"slug":580,"type":15},{"slug":593,"name":593,"fn":594,"description":595,"org":659,"tags":660,"stars":21,"repoUrl":22,"updatedAt":604},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[661,662,663,664],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":601,"slug":602,"type":15},{"name":13,"slug":14,"type":15},{"slug":606,"name":606,"fn":607,"description":608,"org":666,"tags":667,"stars":21,"repoUrl":22,"updatedAt":620},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[668,669,670,671,672],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":614,"slug":615,"type":15},{"name":564,"slug":565,"type":15},{"name":618,"slug":619,"type":15},{"slug":674,"name":674,"fn":675,"description":676,"org":677,"tags":678,"stars":21,"repoUrl":22,"updatedAt":689},"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},[679,680,683,686],{"name":20,"slug":8,"type":15},{"name":681,"slug":682,"type":15},"Database","database",{"name":684,"slug":685,"type":15},"MySQL","mysql",{"name":687,"slug":688,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":691,"name":691,"fn":692,"description":693,"org":694,"tags":695,"stars":21,"repoUrl":22,"updatedAt":702},"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},[696,697,698,701],{"name":20,"slug":8,"type":15},{"name":681,"slug":682,"type":15},{"name":699,"slug":700,"type":15},"PostgreSQL","postgresql",{"name":687,"slug":688,"type":15},"2026-07-16T06:00:34.789624",{"slug":704,"name":704,"fn":705,"description":706,"org":707,"tags":708,"stars":21,"repoUrl":22,"updatedAt":714},"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},[709,710,711],{"name":527,"slug":528,"type":15},{"name":20,"slug":8,"type":15},{"name":712,"slug":713,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":716,"name":716,"fn":717,"description":718,"org":719,"tags":720,"stars":21,"repoUrl":22,"updatedAt":729},"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},[721,722,723,726],{"name":20,"slug":8,"type":15},{"name":681,"slug":682,"type":15},{"name":724,"slug":725,"type":15},"MongoDB","mongodb",{"name":727,"slug":728,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":731,"name":731,"fn":732,"description":733,"org":734,"tags":735,"stars":21,"repoUrl":22,"updatedAt":739},"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},[736,737,738],{"name":20,"slug":8,"type":15},{"name":681,"slug":682,"type":15},{"name":727,"slug":728,"type":15},"2026-07-16T06:00:37.690386",115]