[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-waf":3,"mdc-n7r0vc-key":35,"related-repo-aws-waf":728,"related-org-aws-waf":832},{"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},"waf","configure AWS WAF traffic filtering","Configures AWS WAF to filter web traffic: creating web access control lists (web ACLs) on CloudFront, Application Load Balancers, API Gateway, and AppSync; AWS Managed Rules tuned in Count mode; rate-based rules for HTTP floods; IP set and geographic match rules; Bot Control (Common and Targeted); turning bot labels into a confidence signal; stripping spoofed inbound x-amzn-waf-* headers; recovering the real client IP behind a CDN; Fraud Control (account takeover and account creation fraud prevention); and logging and request sampling. Use when the user wants to protect a web application or API from common exploits, bots, credential stuffing, fake-account creation, or HTTP floods at the application layer (layer 7). Routes to the right per-task procedure in references. Do NOT use for L3\u002FL4 DDoS protection (shieldadvanced skill), multi-account WAF rollout (firewallmanager skill), CloudFront configuration (cloudfront skill), or Route 53 health checks or records (route53 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,22],{"name":13,"slug":14,"type":15},"Security","security","tag",{"name":17,"slug":18,"type":15},"Networking","networking",{"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:39.932063",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\u002Fwaf","---\nname: waf\ndescription: >-\n  Configures AWS WAF to filter web traffic: creating web access control lists (web ACLs) on\n  CloudFront, Application Load Balancers, API Gateway, and AppSync; AWS Managed Rules tuned in Count\n  mode; rate-based rules for HTTP floods; IP set and geographic match rules; Bot Control (Common and\n  Targeted); turning bot labels into a confidence signal; stripping spoofed inbound x-amzn-waf-*\n  headers; recovering the real client IP behind a CDN; Fraud Control (account takeover and account\n  creation fraud prevention); and logging and request sampling. Use when the user wants to protect a\n  web application or API from common exploits, bots, credential stuffing, fake-account creation, or\n  HTTP floods at the application layer (layer 7). Routes to the right per-task procedure in\n  references. Do NOT use for L3\u002FL4 DDoS protection (shieldadvanced skill), multi-account WAF rollout\n  (firewallmanager skill), CloudFront configuration (cloudfront skill), or Route 53 health checks or\n  records (route53 skill).\nversion: 1\n---\n\n# AWS WAF\n\n## Overview\n\nDomain expertise for configuring AWS WAF, the web application firewall that filters HTTP and HTTPS\ntraffic to CloudFront distributions, Application Load Balancers, API Gateway REST APIs, and AppSync\nGraphQL APIs. Covers web ACL creation and association, AWS Managed Rules, rate-based rules, match\nrules (IP set and geographic), Bot Control and the signal-forwarding workflows built on top of it,\nFraud Control for logins and signups, AI and LLM crawler management, and the logging that every\ntuning workflow depends on.\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. A web ACL's scope is fixed at creation: a\nCloudFront web ACL must be created in `us-east-1` with `CLOUDFRONT` scope, while a regional web ACL\n(Application Load Balancer, API Gateway, AppSync) is created in the resource's Region with\n`REGIONAL` scope.\n\n## Which WAF task do you need?\n\n| Goal | Reference |\n| --- | --- |\n| Create a web ACL and attach it to a resource | [creating a web ACL and associating it with a resource](references\u002Fcreating-a-web-acl-and-associating-it-with-a-resource.md) |\n| Set up logging and sampling before tuning anything | [setting up logging and request sampling](references\u002Fsetting-up-logging-and-request-sampling.md) |\n| Add AWS Managed Rules and tune false positives | [adding managed rules and tuning with count mode](references\u002Fadding-managed-rules-and-tuning-with-count-mode.md) |\n| Throttle HTTP floods and brute force | [adding rate-based rules](references\u002Fadding-rate-based-rules.md) |\n| Allow or block by IP range or country | [using ip sets and geographic match rules](references\u002Fusing-ip-sets-and-geographic-match-rules.md) |\n| Detect and control bots (the on-ramp) | [protecting against bots with bot control](references\u002Fprotecting-against-bots-with-bot-control.md) |\n| Collapse bot labels into one confidence signal | [turning bot control labels into a confidence signal](references\u002Fturning-bot-control-labels-into-a-confidence-signal.md) |\n| Forward all signals to the origin with one rule | [forwarding signals with dynamic label interpolation](references\u002Fforwarding-signals-with-dynamic-label-interpolation.md) |\n| Decide what the app does with the forwarded signal | [adaptive mitigation playbook for forwarded signals](references\u002Fadaptive-mitigation-playbook-for-forwarded-signals.md) |\n| Stop attackers from spoofing forwarded headers | [stripping inbound waf headers before trusting them](references\u002Fstripping-inbound-waf-headers-before-trusting-them.md) |\n| Recover the real client IP behind a CDN | [recovering the real client ip behind a cdn](references\u002Frecovering-the-real-client-ip-behind-a-cdn.md) |\n| Protect logins and signups from fraud | [protecting logins and signups with fraud control](references\u002Fprotecting-logins-and-signups-with-fraud-control.md) |\n| See and manage AI and LLM crawler traffic | [seeing and managing ai crawler traffic](references\u002Fseeing-and-managing-ai-crawler-traffic.md) |\n\n## Routing notes\n\n- **Logging comes before tuning.** Every Count-mode tuning workflow assumes logging and request\n  sampling are on. If the customer has not set up logging, run that reference first; otherwise\n  Count-mode tuning has nothing to read.\n- **Web ACL scope is fixed at creation.** A CloudFront web ACL is `CLOUDFRONT` scope in\n  `us-east-1`; a regional resource needs a `REGIONAL` web ACL in its own Region. Scope cannot be\n  changed later, so the creating reference settles it before anything is built.\n- **Bot Control is a chain, not one task.** Protecting against bots is the on-ramp (turn on, choose\n  Common vs Targeted, observe). Turning labels into a confidence signal, forwarding that signal,\n  and deciding what the application does with it are three separate references that build on it in\n  that order. The header-stripping reference is the mandatory safety companion whenever a signal is\n  forwarded to the origin.\n- **Common vs Targeted is not a soft choice.** Common only catches self-identifying bots and\n  known-bad IPs. For login, checkout, or any high-value endpoint facing evasive bots, Targeted with\n  the application integration SDK is required. The bots reference pushes Targeted for real bot\n  threats rather than presenting it as optional.\n- **Rate limiting vs Fraud Control.** Rate-based rules blunt volumetric HTTP floods. Credential\n  stuffing and fake-account creation are account-based abuse that rate limiting misses; those go to\n  the Fraud Control reference (ATP and ACFP), not the rate-based reference.\n- **Forwarded headers need the strip rule.** Any time the customer forwards a signal or the client\n  IP to the origin in `x-amzn-waf-*` headers, the inbound-header-stripping reference is required to\n  prevent spoofing. The confidence-signal, interpolation, and client-IP references all point at it.\n- **What lives in other skills.** L3\u002FL4 DDoS protection and Shield cost-protection credits are the\n  shieldadvanced skill. Multi-account WAF rollout is the firewallmanager skill. CloudFront and\n  Application Load Balancer configuration are their own skills. This skill builds the WAF rules; it\n  does not configure the resources it protects.\n\n## Security Considerations\n\nAWS WAF is itself a security control, so misconfiguration directly weakens an application's defenses.\nApply these across every reference:\n\n- **Least-privilege IAM.** You MUST grant only the specific `wafv2:` actions a task needs (for\n  example `wafv2:CreateWebACL`, `wafv2:GetWebACL`, `wafv2:UpdateWebACL`, `wafv2:AssociateWebACL`,\n  `wafv2:PutLoggingConfiguration`) rather than `wafv2:*` or the `AWSWAFFullAccess` managed policy.\n- **Ephemeral credentials.** You MUST use IAM roles with temporary credentials (such as an EC2\n  instance profile, SSO session, or `aws sts assume-role`) rather than long-lived IAM user access\n  keys when running these WAF CLI commands.\n- **Monitor configuration changes.** You SHOULD enable AWS CloudTrail on `wafv2` management events\n  and set CloudWatch alarms on critical web ACL configuration changes (such as `DeleteWebACL` and\n  `UpdateWebACL` rule removals) and on the web ACL's `BlockedRequests` and `CountedRequests`\n  metrics, so rule changes and sudden spikes in blocked or counted traffic are detected.\n- **Misconfiguration opens access.** A web ACL that is created but never associated, or one whose\n  default action is left at `Allow` with no enforcing rules, filters nothing. You MUST confirm the\n  web ACL is associated and that its posture matches the intended default (block vs allow) before\n  reporting setup complete.\n- **Protect log destinations.** Logs can capture credentials and session data. You MUST redact\n  sensitive fields (such as the `authorization` header and `cookie`) and MUST enable encryption at\n  rest on the log destination (CloudWatch Logs, Amazon S3, or Amazon Data Firehose).\n- **Header-spoofing risk.** Any `x-amzn-waf-*` signal forwarded to the origin can be forged inbound.\n  You MUST add the inbound-header-stripping rule whenever a signal or client IP is forwarded (see\n  stripping-inbound-waf-headers-before-trusting-them).\n\n## Additional Resources\n\n- [AWS WAF Developer Guide](https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fwaf-chapter.html)\n- [How AWS WAF works (AWS WAF Developer Guide)](https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fhow-aws-waf-works.html)\n- [AWS WAF pricing](https:\u002F\u002Faws.amazon.com\u002Fwaf\u002Fpricing\u002F)\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,50,57,63,77,106,112,362,368,473,479,484,688,694],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"aws-waf",[47],{"type":48,"value":49},"text","AWS WAF",{"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 AWS WAF, the web application firewall that filters HTTP and HTTPS\ntraffic to CloudFront distributions, Application Load Balancers, API Gateway REST APIs, and AppSync\nGraphQL APIs. Covers web ACL creation and association, AWS Managed Rules, rate-based rules, match\nrules (IP set and geographic), Bot Control and the signal-forwarding workflows built on top of it,\nFraud Control for logins and signups, AI and LLM crawler management, and the logging that every\ntuning workflow depends on.",{"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,90,96,98,104],{"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. A web ACL's scope is fixed at creation: a\nCloudFront web ACL must be created in ",{"type":42,"tag":69,"props":83,"children":85},{"className":84},[],[86],{"type":48,"value":87},"us-east-1",{"type":48,"value":89}," with ",{"type":42,"tag":69,"props":91,"children":93},{"className":92},[],[94],{"type":48,"value":95},"CLOUDFRONT",{"type":48,"value":97}," scope, while a regional web ACL\n(Application Load Balancer, API Gateway, AppSync) is created in the resource's Region with\n",{"type":42,"tag":69,"props":99,"children":101},{"className":100},[],[102],{"type":48,"value":103},"REGIONAL",{"type":48,"value":105}," scope.",{"type":42,"tag":51,"props":107,"children":109},{"id":108},"which-waf-task-do-you-need",[110],{"type":48,"value":111},"Which WAF task do you need?",{"type":42,"tag":113,"props":114,"children":115},"table",{},[116,135],{"type":42,"tag":117,"props":118,"children":119},"thead",{},[120],{"type":42,"tag":121,"props":122,"children":123},"tr",{},[124,130],{"type":42,"tag":125,"props":126,"children":127},"th",{},[128],{"type":48,"value":129},"Goal",{"type":42,"tag":125,"props":131,"children":132},{},[133],{"type":48,"value":134},"Reference",{"type":42,"tag":136,"props":137,"children":138},"tbody",{},[139,158,175,192,209,226,243,260,277,294,311,328,345],{"type":42,"tag":121,"props":140,"children":141},{},[142,148],{"type":42,"tag":143,"props":144,"children":145},"td",{},[146],{"type":48,"value":147},"Create a web ACL and attach it to a resource",{"type":42,"tag":143,"props":149,"children":150},{},[151],{"type":42,"tag":152,"props":153,"children":155},"a",{"href":154},"references\u002Fcreating-a-web-acl-and-associating-it-with-a-resource.md",[156],{"type":48,"value":157},"creating a web ACL and associating it with a resource",{"type":42,"tag":121,"props":159,"children":160},{},[161,166],{"type":42,"tag":143,"props":162,"children":163},{},[164],{"type":48,"value":165},"Set up logging and sampling before tuning anything",{"type":42,"tag":143,"props":167,"children":168},{},[169],{"type":42,"tag":152,"props":170,"children":172},{"href":171},"references\u002Fsetting-up-logging-and-request-sampling.md",[173],{"type":48,"value":174},"setting up logging and request sampling",{"type":42,"tag":121,"props":176,"children":177},{},[178,183],{"type":42,"tag":143,"props":179,"children":180},{},[181],{"type":48,"value":182},"Add AWS Managed Rules and tune false positives",{"type":42,"tag":143,"props":184,"children":185},{},[186],{"type":42,"tag":152,"props":187,"children":189},{"href":188},"references\u002Fadding-managed-rules-and-tuning-with-count-mode.md",[190],{"type":48,"value":191},"adding managed rules and tuning with count mode",{"type":42,"tag":121,"props":193,"children":194},{},[195,200],{"type":42,"tag":143,"props":196,"children":197},{},[198],{"type":48,"value":199},"Throttle HTTP floods and brute force",{"type":42,"tag":143,"props":201,"children":202},{},[203],{"type":42,"tag":152,"props":204,"children":206},{"href":205},"references\u002Fadding-rate-based-rules.md",[207],{"type":48,"value":208},"adding rate-based rules",{"type":42,"tag":121,"props":210,"children":211},{},[212,217],{"type":42,"tag":143,"props":213,"children":214},{},[215],{"type":48,"value":216},"Allow or block by IP range or country",{"type":42,"tag":143,"props":218,"children":219},{},[220],{"type":42,"tag":152,"props":221,"children":223},{"href":222},"references\u002Fusing-ip-sets-and-geographic-match-rules.md",[224],{"type":48,"value":225},"using ip sets and geographic match rules",{"type":42,"tag":121,"props":227,"children":228},{},[229,234],{"type":42,"tag":143,"props":230,"children":231},{},[232],{"type":48,"value":233},"Detect and control bots (the on-ramp)",{"type":42,"tag":143,"props":235,"children":236},{},[237],{"type":42,"tag":152,"props":238,"children":240},{"href":239},"references\u002Fprotecting-against-bots-with-bot-control.md",[241],{"type":48,"value":242},"protecting against bots with bot control",{"type":42,"tag":121,"props":244,"children":245},{},[246,251],{"type":42,"tag":143,"props":247,"children":248},{},[249],{"type":48,"value":250},"Collapse bot labels into one confidence signal",{"type":42,"tag":143,"props":252,"children":253},{},[254],{"type":42,"tag":152,"props":255,"children":257},{"href":256},"references\u002Fturning-bot-control-labels-into-a-confidence-signal.md",[258],{"type":48,"value":259},"turning bot control labels into a confidence signal",{"type":42,"tag":121,"props":261,"children":262},{},[263,268],{"type":42,"tag":143,"props":264,"children":265},{},[266],{"type":48,"value":267},"Forward all signals to the origin with one rule",{"type":42,"tag":143,"props":269,"children":270},{},[271],{"type":42,"tag":152,"props":272,"children":274},{"href":273},"references\u002Fforwarding-signals-with-dynamic-label-interpolation.md",[275],{"type":48,"value":276},"forwarding signals with dynamic label interpolation",{"type":42,"tag":121,"props":278,"children":279},{},[280,285],{"type":42,"tag":143,"props":281,"children":282},{},[283],{"type":48,"value":284},"Decide what the app does with the forwarded signal",{"type":42,"tag":143,"props":286,"children":287},{},[288],{"type":42,"tag":152,"props":289,"children":291},{"href":290},"references\u002Fadaptive-mitigation-playbook-for-forwarded-signals.md",[292],{"type":48,"value":293},"adaptive mitigation playbook for forwarded signals",{"type":42,"tag":121,"props":295,"children":296},{},[297,302],{"type":42,"tag":143,"props":298,"children":299},{},[300],{"type":48,"value":301},"Stop attackers from spoofing forwarded headers",{"type":42,"tag":143,"props":303,"children":304},{},[305],{"type":42,"tag":152,"props":306,"children":308},{"href":307},"references\u002Fstripping-inbound-waf-headers-before-trusting-them.md",[309],{"type":48,"value":310},"stripping inbound waf headers before trusting them",{"type":42,"tag":121,"props":312,"children":313},{},[314,319],{"type":42,"tag":143,"props":315,"children":316},{},[317],{"type":48,"value":318},"Recover the real client IP behind a CDN",{"type":42,"tag":143,"props":320,"children":321},{},[322],{"type":42,"tag":152,"props":323,"children":325},{"href":324},"references\u002Frecovering-the-real-client-ip-behind-a-cdn.md",[326],{"type":48,"value":327},"recovering the real client ip behind a cdn",{"type":42,"tag":121,"props":329,"children":330},{},[331,336],{"type":42,"tag":143,"props":332,"children":333},{},[334],{"type":48,"value":335},"Protect logins and signups from fraud",{"type":42,"tag":143,"props":337,"children":338},{},[339],{"type":42,"tag":152,"props":340,"children":342},{"href":341},"references\u002Fprotecting-logins-and-signups-with-fraud-control.md",[343],{"type":48,"value":344},"protecting logins and signups with fraud control",{"type":42,"tag":121,"props":346,"children":347},{},[348,353],{"type":42,"tag":143,"props":349,"children":350},{},[351],{"type":48,"value":352},"See and manage AI and LLM crawler traffic",{"type":42,"tag":143,"props":354,"children":355},{},[356],{"type":42,"tag":152,"props":357,"children":359},{"href":358},"references\u002Fseeing-and-managing-ai-crawler-traffic.md",[360],{"type":48,"value":361},"seeing and managing ai crawler traffic",{"type":42,"tag":51,"props":363,"children":365},{"id":364},"routing-notes",[366],{"type":48,"value":367},"Routing notes",{"type":42,"tag":369,"props":370,"children":371},"ul",{},[372,384,415,425,435,445,463],{"type":42,"tag":373,"props":374,"children":375},"li",{},[376,382],{"type":42,"tag":377,"props":378,"children":379},"strong",{},[380],{"type":48,"value":381},"Logging comes before tuning.",{"type":48,"value":383}," Every Count-mode tuning workflow assumes logging and request\nsampling are on. If the customer has not set up logging, run that reference first; otherwise\nCount-mode tuning has nothing to read.",{"type":42,"tag":373,"props":385,"children":386},{},[387,392,394,399,401,406,408,413],{"type":42,"tag":377,"props":388,"children":389},{},[390],{"type":48,"value":391},"Web ACL scope is fixed at creation.",{"type":48,"value":393}," A CloudFront web ACL is ",{"type":42,"tag":69,"props":395,"children":397},{"className":396},[],[398],{"type":48,"value":95},{"type":48,"value":400}," scope in\n",{"type":42,"tag":69,"props":402,"children":404},{"className":403},[],[405],{"type":48,"value":87},{"type":48,"value":407},"; a regional resource needs a ",{"type":42,"tag":69,"props":409,"children":411},{"className":410},[],[412],{"type":48,"value":103},{"type":48,"value":414}," web ACL in its own Region. Scope cannot be\nchanged later, so the creating reference settles it before anything is built.",{"type":42,"tag":373,"props":416,"children":417},{},[418,423],{"type":42,"tag":377,"props":419,"children":420},{},[421],{"type":48,"value":422},"Bot Control is a chain, not one task.",{"type":48,"value":424}," Protecting against bots is the on-ramp (turn on, choose\nCommon vs Targeted, observe). Turning labels into a confidence signal, forwarding that signal,\nand deciding what the application does with it are three separate references that build on it in\nthat order. The header-stripping reference is the mandatory safety companion whenever a signal is\nforwarded to the origin.",{"type":42,"tag":373,"props":426,"children":427},{},[428,433],{"type":42,"tag":377,"props":429,"children":430},{},[431],{"type":48,"value":432},"Common vs Targeted is not a soft choice.",{"type":48,"value":434}," Common only catches self-identifying bots and\nknown-bad IPs. For login, checkout, or any high-value endpoint facing evasive bots, Targeted with\nthe application integration SDK is required. The bots reference pushes Targeted for real bot\nthreats rather than presenting it as optional.",{"type":42,"tag":373,"props":436,"children":437},{},[438,443],{"type":42,"tag":377,"props":439,"children":440},{},[441],{"type":48,"value":442},"Rate limiting vs Fraud Control.",{"type":48,"value":444}," Rate-based rules blunt volumetric HTTP floods. Credential\nstuffing and fake-account creation are account-based abuse that rate limiting misses; those go to\nthe Fraud Control reference (ATP and ACFP), not the rate-based reference.",{"type":42,"tag":373,"props":446,"children":447},{},[448,453,455,461],{"type":42,"tag":377,"props":449,"children":450},{},[451],{"type":48,"value":452},"Forwarded headers need the strip rule.",{"type":48,"value":454}," Any time the customer forwards a signal or the client\nIP to the origin in ",{"type":42,"tag":69,"props":456,"children":458},{"className":457},[],[459],{"type":48,"value":460},"x-amzn-waf-*",{"type":48,"value":462}," headers, the inbound-header-stripping reference is required to\nprevent spoofing. The confidence-signal, interpolation, and client-IP references all point at it.",{"type":42,"tag":373,"props":464,"children":465},{},[466,471],{"type":42,"tag":377,"props":467,"children":468},{},[469],{"type":48,"value":470},"What lives in other skills.",{"type":48,"value":472}," L3\u002FL4 DDoS protection and Shield cost-protection credits are the\nshieldadvanced skill. Multi-account WAF rollout is the firewallmanager skill. CloudFront and\nApplication Load Balancer configuration are their own skills. This skill builds the WAF rules; it\ndoes not configure the resources it protects.",{"type":42,"tag":51,"props":474,"children":476},{"id":475},"security-considerations",[477],{"type":48,"value":478},"Security Considerations",{"type":42,"tag":58,"props":480,"children":481},{},[482],{"type":48,"value":483},"AWS WAF is itself a security control, so misconfiguration directly weakens an application's defenses.\nApply these across every reference:",{"type":42,"tag":369,"props":485,"children":486},{},[487,559,577,627,645,671],{"type":42,"tag":373,"props":488,"children":489},{},[490,495,497,503,505,511,513,519,520,526,527,533,535,541,543,549,551,557],{"type":42,"tag":377,"props":491,"children":492},{},[493],{"type":48,"value":494},"Least-privilege IAM.",{"type":48,"value":496}," You MUST grant only the specific ",{"type":42,"tag":69,"props":498,"children":500},{"className":499},[],[501],{"type":48,"value":502},"wafv2:",{"type":48,"value":504}," actions a task needs (for\nexample ",{"type":42,"tag":69,"props":506,"children":508},{"className":507},[],[509],{"type":48,"value":510},"wafv2:CreateWebACL",{"type":48,"value":512},", ",{"type":42,"tag":69,"props":514,"children":516},{"className":515},[],[517],{"type":48,"value":518},"wafv2:GetWebACL",{"type":48,"value":512},{"type":42,"tag":69,"props":521,"children":523},{"className":522},[],[524],{"type":48,"value":525},"wafv2:UpdateWebACL",{"type":48,"value":512},{"type":42,"tag":69,"props":528,"children":530},{"className":529},[],[531],{"type":48,"value":532},"wafv2:AssociateWebACL",{"type":48,"value":534},",\n",{"type":42,"tag":69,"props":536,"children":538},{"className":537},[],[539],{"type":48,"value":540},"wafv2:PutLoggingConfiguration",{"type":48,"value":542},") rather than ",{"type":42,"tag":69,"props":544,"children":546},{"className":545},[],[547],{"type":48,"value":548},"wafv2:*",{"type":48,"value":550}," or the ",{"type":42,"tag":69,"props":552,"children":554},{"className":553},[],[555],{"type":48,"value":556},"AWSWAFFullAccess",{"type":48,"value":558}," managed policy.",{"type":42,"tag":373,"props":560,"children":561},{},[562,567,569,575],{"type":42,"tag":377,"props":563,"children":564},{},[565],{"type":48,"value":566},"Ephemeral credentials.",{"type":48,"value":568}," You MUST use IAM roles with temporary credentials (such as an EC2\ninstance profile, SSO session, or ",{"type":42,"tag":69,"props":570,"children":572},{"className":571},[],[573],{"type":48,"value":574},"aws sts assume-role",{"type":48,"value":576},") rather than long-lived IAM user access\nkeys when running these WAF CLI commands.",{"type":42,"tag":373,"props":578,"children":579},{},[580,585,587,593,595,601,603,609,611,617,619,625],{"type":42,"tag":377,"props":581,"children":582},{},[583],{"type":48,"value":584},"Monitor configuration changes.",{"type":48,"value":586}," You SHOULD enable AWS CloudTrail on ",{"type":42,"tag":69,"props":588,"children":590},{"className":589},[],[591],{"type":48,"value":592},"wafv2",{"type":48,"value":594}," management events\nand set CloudWatch alarms on critical web ACL configuration changes (such as ",{"type":42,"tag":69,"props":596,"children":598},{"className":597},[],[599],{"type":48,"value":600},"DeleteWebACL",{"type":48,"value":602}," and\n",{"type":42,"tag":69,"props":604,"children":606},{"className":605},[],[607],{"type":48,"value":608},"UpdateWebACL",{"type":48,"value":610}," rule removals) and on the web ACL's ",{"type":42,"tag":69,"props":612,"children":614},{"className":613},[],[615],{"type":48,"value":616},"BlockedRequests",{"type":48,"value":618}," and ",{"type":42,"tag":69,"props":620,"children":622},{"className":621},[],[623],{"type":48,"value":624},"CountedRequests",{"type":48,"value":626},"\nmetrics, so rule changes and sudden spikes in blocked or counted traffic are detected.",{"type":42,"tag":373,"props":628,"children":629},{},[630,635,637,643],{"type":42,"tag":377,"props":631,"children":632},{},[633],{"type":48,"value":634},"Misconfiguration opens access.",{"type":48,"value":636}," A web ACL that is created but never associated, or one whose\ndefault action is left at ",{"type":42,"tag":69,"props":638,"children":640},{"className":639},[],[641],{"type":48,"value":642},"Allow",{"type":48,"value":644}," with no enforcing rules, filters nothing. You MUST confirm the\nweb ACL is associated and that its posture matches the intended default (block vs allow) before\nreporting setup complete.",{"type":42,"tag":373,"props":646,"children":647},{},[648,653,655,661,663,669],{"type":42,"tag":377,"props":649,"children":650},{},[651],{"type":48,"value":652},"Protect log destinations.",{"type":48,"value":654}," Logs can capture credentials and session data. You MUST redact\nsensitive fields (such as the ",{"type":42,"tag":69,"props":656,"children":658},{"className":657},[],[659],{"type":48,"value":660},"authorization",{"type":48,"value":662}," header and ",{"type":42,"tag":69,"props":664,"children":666},{"className":665},[],[667],{"type":48,"value":668},"cookie",{"type":48,"value":670},") and MUST enable encryption at\nrest on the log destination (CloudWatch Logs, Amazon S3, or Amazon Data Firehose).",{"type":42,"tag":373,"props":672,"children":673},{},[674,679,681,686],{"type":42,"tag":377,"props":675,"children":676},{},[677],{"type":48,"value":678},"Header-spoofing risk.",{"type":48,"value":680}," Any ",{"type":42,"tag":69,"props":682,"children":684},{"className":683},[],[685],{"type":48,"value":460},{"type":48,"value":687}," signal forwarded to the origin can be forged inbound.\nYou MUST add the inbound-header-stripping rule whenever a signal or client IP is forwarded (see\nstripping-inbound-waf-headers-before-trusting-them).",{"type":42,"tag":51,"props":689,"children":691},{"id":690},"additional-resources",[692],{"type":48,"value":693},"Additional Resources",{"type":42,"tag":369,"props":695,"children":696},{},[697,708,718],{"type":42,"tag":373,"props":698,"children":699},{},[700],{"type":42,"tag":152,"props":701,"children":705},{"href":702,"rel":703},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fwaf-chapter.html",[704],"nofollow",[706],{"type":48,"value":707},"AWS WAF Developer Guide",{"type":42,"tag":373,"props":709,"children":710},{},[711],{"type":42,"tag":152,"props":712,"children":715},{"href":713,"rel":714},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwaf\u002Flatest\u002Fdeveloperguide\u002Fhow-aws-waf-works.html",[704],[716],{"type":48,"value":717},"How AWS WAF works (AWS WAF Developer Guide)",{"type":42,"tag":373,"props":719,"children":720},{},[721],{"type":42,"tag":152,"props":722,"children":725},{"href":723,"rel":724},"https:\u002F\u002Faws.amazon.com\u002Fwaf\u002Fpricing\u002F",[704],[726],{"type":48,"value":727},"AWS WAF pricing",{"items":729,"total":831},[730,747,762,777,792,802,815],{"slug":731,"name":731,"fn":732,"description":733,"org":734,"tags":735,"stars":24,"repoUrl":25,"updatedAt":746},"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},[736,739,742,743],{"name":737,"slug":738,"type":15},"Agents","agents",{"name":740,"slug":741,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},{"name":744,"slug":745,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":748,"name":748,"fn":749,"description":750,"org":751,"tags":752,"stars":24,"repoUrl":25,"updatedAt":761},"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},[753,754,757,760],{"name":737,"slug":738,"type":15},{"name":755,"slug":756,"type":15},"API Development","api-development",{"name":758,"slug":759,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":763,"name":763,"fn":764,"description":765,"org":766,"tags":767,"stars":24,"repoUrl":25,"updatedAt":776},"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},[768,769,770,773],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":771,"slug":772,"type":15},"Debugging","debugging",{"name":774,"slug":775,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":778,"name":778,"fn":779,"description":780,"org":781,"tags":782,"stars":24,"repoUrl":25,"updatedAt":791},"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},[783,784,785,788],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":786,"slug":787,"type":15},"CI\u002FCD","ci-cd",{"name":789,"slug":790,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":793,"name":793,"fn":794,"description":795,"org":796,"tags":797,"stars":24,"repoUrl":25,"updatedAt":801},"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},[798,799,800],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":789,"slug":790,"type":15},"2026-07-12T08:42:51.963247",{"slug":803,"name":803,"fn":804,"description":805,"org":806,"tags":807,"stars":24,"repoUrl":25,"updatedAt":814},"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},[808,809,810,813],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":811,"slug":812,"type":15},"Best Practices","best-practices",{"name":13,"slug":14,"type":15},"2026-07-16T06:00:42.174705",{"slug":816,"name":816,"fn":817,"description":818,"org":819,"tags":820,"stars":24,"repoUrl":25,"updatedAt":830},"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},[821,822,823,826,827],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":824,"slug":825,"type":15},"Evals","evals",{"name":774,"slug":775,"type":15},{"name":828,"slug":829,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",114,{"items":833,"total":950},[834,841,848,855,862,868,875,883,900,913,925,940],{"slug":731,"name":731,"fn":732,"description":733,"org":835,"tags":836,"stars":24,"repoUrl":25,"updatedAt":746},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[837,838,839,840],{"name":737,"slug":738,"type":15},{"name":740,"slug":741,"type":15},{"name":23,"slug":8,"type":15},{"name":744,"slug":745,"type":15},{"slug":748,"name":748,"fn":749,"description":750,"org":842,"tags":843,"stars":24,"repoUrl":25,"updatedAt":761},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[844,845,846,847],{"name":737,"slug":738,"type":15},{"name":755,"slug":756,"type":15},{"name":758,"slug":759,"type":15},{"name":23,"slug":8,"type":15},{"slug":763,"name":763,"fn":764,"description":765,"org":849,"tags":850,"stars":24,"repoUrl":25,"updatedAt":776},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[851,852,853,854],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":771,"slug":772,"type":15},{"name":774,"slug":775,"type":15},{"slug":778,"name":778,"fn":779,"description":780,"org":856,"tags":857,"stars":24,"repoUrl":25,"updatedAt":791},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[858,859,860,861],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":786,"slug":787,"type":15},{"name":789,"slug":790,"type":15},{"slug":793,"name":793,"fn":794,"description":795,"org":863,"tags":864,"stars":24,"repoUrl":25,"updatedAt":801},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[865,866,867],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":789,"slug":790,"type":15},{"slug":803,"name":803,"fn":804,"description":805,"org":869,"tags":870,"stars":24,"repoUrl":25,"updatedAt":814},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[871,872,873,874],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":811,"slug":812,"type":15},{"name":13,"slug":14,"type":15},{"slug":816,"name":816,"fn":817,"description":818,"org":876,"tags":877,"stars":24,"repoUrl":25,"updatedAt":830},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[878,879,880,881,882],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":824,"slug":825,"type":15},{"name":774,"slug":775,"type":15},{"name":828,"slug":829,"type":15},{"slug":884,"name":884,"fn":885,"description":886,"org":887,"tags":888,"stars":24,"repoUrl":25,"updatedAt":899},"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},[889,890,893,896],{"name":23,"slug":8,"type":15},{"name":891,"slug":892,"type":15},"Database","database",{"name":894,"slug":895,"type":15},"MySQL","mysql",{"name":897,"slug":898,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":901,"name":901,"fn":902,"description":903,"org":904,"tags":905,"stars":24,"repoUrl":25,"updatedAt":912},"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},[906,907,908,911],{"name":23,"slug":8,"type":15},{"name":891,"slug":892,"type":15},{"name":909,"slug":910,"type":15},"PostgreSQL","postgresql",{"name":897,"slug":898,"type":15},"2026-07-16T06:00:34.789624",{"slug":914,"name":914,"fn":915,"description":916,"org":917,"tags":918,"stars":24,"repoUrl":25,"updatedAt":924},"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},[919,920,921],{"name":737,"slug":738,"type":15},{"name":23,"slug":8,"type":15},{"name":922,"slug":923,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":926,"name":926,"fn":927,"description":928,"org":929,"tags":930,"stars":24,"repoUrl":25,"updatedAt":939},"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},[931,932,933,936],{"name":23,"slug":8,"type":15},{"name":891,"slug":892,"type":15},{"name":934,"slug":935,"type":15},"MongoDB","mongodb",{"name":937,"slug":938,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":941,"name":941,"fn":942,"description":943,"org":944,"tags":945,"stars":24,"repoUrl":25,"updatedAt":949},"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},[946,947,948],{"name":23,"slug":8,"type":15},{"name":891,"slug":892,"type":15},{"name":937,"slug":938,"type":15},"2026-07-16T06:00:37.690386",115]