[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-enabling-lambda-vpc-internet-access":3,"mdc--b1dptr-key":35,"related-repo-aws-enabling-lambda-vpc-internet-access":149,"related-org-aws-enabling-lambda-vpc-internet-access":253},{"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},"enabling-lambda-vpc-internet-access","enable internet access for VPC Lambda functions","Enables internet access for AWS Lambda functions deployed in VPC subnets by creating NAT Gateway infrastructure, configuring public\u002Fprivate subnet routing, and updating security groups. Use when a VPC-attached Lambda function cannot reach the internet.",{"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-12T08:44:52.805638",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\u002Fenabling-lambda-vpc-internet-access","---\nname: enabling-lambda-vpc-internet-access\ndescription: Enables internet access for AWS Lambda functions deployed in VPC subnets by creating NAT Gateway infrastructure, configuring public\u002Fprivate subnet routing, and updating security groups. Use when a VPC-attached Lambda function cannot reach the internet.\nversion: 1\n---\n\n# Enabling Lambda VPC Internet Access\n\n## Overview\n\nDomain expertise for enabling internet access from AWS Lambda functions running inside VPC private subnets. Lambda functions in a VPC cannot receive public IP addresses, so outbound internet access requires NAT Gateway infrastructure that routes traffic from private subnets through a public subnet to an Internet Gateway.\n\n## Enable internet access for a VPC Lambda function\n\nTo set up NAT Gateway infrastructure and configure routing for a Lambda function that needs internet access, follow the procedure exactly.\nSee [Lambda VPC internet access setup procedure](references\u002Flambda-vpc-internet-access.md).\n\n## Troubleshooting\n\n### NAT Gateway not working\n\nVerify the route table associated with the Lambda subnets has a `0.0.0.0\u002F0` route pointing to the NAT Gateway. See the full procedure for details.\n\n### Lambda function timeout\n\nCheck that security group outbound rules allow the necessary ports and that both the NAT Gateway and Internet Gateway are properly configured.\n\n### Network changes not taking effect\n\nVPC networking changes can take 1–2 minutes to propagate. Wait before testing after creating a NAT Gateway or updating route tables.\n\n### Route table association issues\n\nConfirm the Lambda function's subnets are associated with the route table that has the `0.0.0.0\u002F0` route to the NAT Gateway.\n",{"data":36,"body":38},{"name":4,"description":6,"version":37},1,{"type":39,"children":40},"root",[41,49,56,62,68,82,88,95,109,115,120,126,131,137],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Enabling Lambda VPC Internet Access",{"type":42,"tag":50,"props":51,"children":53},"h2",{"id":52},"overview",[54],{"type":47,"value":55},"Overview",{"type":42,"tag":57,"props":58,"children":59},"p",{},[60],{"type":47,"value":61},"Domain expertise for enabling internet access from AWS Lambda functions running inside VPC private subnets. Lambda functions in a VPC cannot receive public IP addresses, so outbound internet access requires NAT Gateway infrastructure that routes traffic from private subnets through a public subnet to an Internet Gateway.",{"type":42,"tag":50,"props":63,"children":65},{"id":64},"enable-internet-access-for-a-vpc-lambda-function",[66],{"type":47,"value":67},"Enable internet access for a VPC Lambda function",{"type":42,"tag":57,"props":69,"children":70},{},[71,73,80],{"type":47,"value":72},"To set up NAT Gateway infrastructure and configure routing for a Lambda function that needs internet access, follow the procedure exactly.\nSee ",{"type":42,"tag":74,"props":75,"children":77},"a",{"href":76},"references\u002Flambda-vpc-internet-access.md",[78],{"type":47,"value":79},"Lambda VPC internet access setup procedure",{"type":47,"value":81},".",{"type":42,"tag":50,"props":83,"children":85},{"id":84},"troubleshooting",[86],{"type":47,"value":87},"Troubleshooting",{"type":42,"tag":89,"props":90,"children":92},"h3",{"id":91},"nat-gateway-not-working",[93],{"type":47,"value":94},"NAT Gateway not working",{"type":42,"tag":57,"props":96,"children":97},{},[98,100,107],{"type":47,"value":99},"Verify the route table associated with the Lambda subnets has a ",{"type":42,"tag":101,"props":102,"children":104},"code",{"className":103},[],[105],{"type":47,"value":106},"0.0.0.0\u002F0",{"type":47,"value":108}," route pointing to the NAT Gateway. See the full procedure for details.",{"type":42,"tag":89,"props":110,"children":112},{"id":111},"lambda-function-timeout",[113],{"type":47,"value":114},"Lambda function timeout",{"type":42,"tag":57,"props":116,"children":117},{},[118],{"type":47,"value":119},"Check that security group outbound rules allow the necessary ports and that both the NAT Gateway and Internet Gateway are properly configured.",{"type":42,"tag":89,"props":121,"children":123},{"id":122},"network-changes-not-taking-effect",[124],{"type":47,"value":125},"Network changes not taking effect",{"type":42,"tag":57,"props":127,"children":128},{},[129],{"type":47,"value":130},"VPC networking changes can take 1–2 minutes to propagate. Wait before testing after creating a NAT Gateway or updating route tables.",{"type":42,"tag":89,"props":132,"children":134},{"id":133},"route-table-association-issues",[135],{"type":47,"value":136},"Route table association issues",{"type":42,"tag":57,"props":138,"children":139},{},[140,142,147],{"type":47,"value":141},"Confirm the Lambda function's subnets are associated with the route table that has the ",{"type":42,"tag":101,"props":143,"children":145},{"className":144},[],[146],{"type":47,"value":106},{"type":47,"value":148}," route to the NAT Gateway.",{"items":150,"total":252},[151,168,183,198,213,223,236],{"slug":152,"name":152,"fn":153,"description":154,"org":155,"tags":156,"stars":24,"repoUrl":25,"updatedAt":167},"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},[157,160,163,164],{"name":158,"slug":159,"type":15},"Agents","agents",{"name":161,"slug":162,"type":15},"Automation","automation",{"name":23,"slug":8,"type":15},{"name":165,"slug":166,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":169,"name":169,"fn":170,"description":171,"org":172,"tags":173,"stars":24,"repoUrl":25,"updatedAt":182},"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},[174,175,178,181],{"name":158,"slug":159,"type":15},{"name":176,"slug":177,"type":15},"API Development","api-development",{"name":179,"slug":180,"type":15},"Authentication","authentication",{"name":23,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":184,"name":184,"fn":185,"description":186,"org":187,"tags":188,"stars":24,"repoUrl":25,"updatedAt":197},"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},[189,190,191,194],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":192,"slug":193,"type":15},"Debugging","debugging",{"name":195,"slug":196,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":199,"name":199,"fn":200,"description":201,"org":202,"tags":203,"stars":24,"repoUrl":25,"updatedAt":212},"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},[204,205,206,209],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":207,"slug":208,"type":15},"CI\u002FCD","ci-cd",{"name":210,"slug":211,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":214,"name":214,"fn":215,"description":216,"org":217,"tags":218,"stars":24,"repoUrl":25,"updatedAt":222},"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},[219,220,221],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":210,"slug":211,"type":15},"2026-07-12T08:42:51.963247",{"slug":224,"name":224,"fn":225,"description":226,"org":227,"tags":228,"stars":24,"repoUrl":25,"updatedAt":235},"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},[229,230,231,234],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":232,"slug":233,"type":15},"Best Practices","best-practices",{"name":13,"slug":14,"type":15},"2026-07-16T06:00:42.174705",{"slug":237,"name":237,"fn":238,"description":239,"org":240,"tags":241,"stars":24,"repoUrl":25,"updatedAt":251},"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},[242,243,244,247,248],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":245,"slug":246,"type":15},"Evals","evals",{"name":195,"slug":196,"type":15},{"name":249,"slug":250,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",114,{"items":254,"total":371},[255,262,269,276,283,289,296,304,321,334,346,361],{"slug":152,"name":152,"fn":153,"description":154,"org":256,"tags":257,"stars":24,"repoUrl":25,"updatedAt":167},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[258,259,260,261],{"name":158,"slug":159,"type":15},{"name":161,"slug":162,"type":15},{"name":23,"slug":8,"type":15},{"name":165,"slug":166,"type":15},{"slug":169,"name":169,"fn":170,"description":171,"org":263,"tags":264,"stars":24,"repoUrl":25,"updatedAt":182},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[265,266,267,268],{"name":158,"slug":159,"type":15},{"name":176,"slug":177,"type":15},{"name":179,"slug":180,"type":15},{"name":23,"slug":8,"type":15},{"slug":184,"name":184,"fn":185,"description":186,"org":270,"tags":271,"stars":24,"repoUrl":25,"updatedAt":197},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[272,273,274,275],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":192,"slug":193,"type":15},{"name":195,"slug":196,"type":15},{"slug":199,"name":199,"fn":200,"description":201,"org":277,"tags":278,"stars":24,"repoUrl":25,"updatedAt":212},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[279,280,281,282],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":207,"slug":208,"type":15},{"name":210,"slug":211,"type":15},{"slug":214,"name":214,"fn":215,"description":216,"org":284,"tags":285,"stars":24,"repoUrl":25,"updatedAt":222},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[286,287,288],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":210,"slug":211,"type":15},{"slug":224,"name":224,"fn":225,"description":226,"org":290,"tags":291,"stars":24,"repoUrl":25,"updatedAt":235},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[292,293,294,295],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":232,"slug":233,"type":15},{"name":13,"slug":14,"type":15},{"slug":237,"name":237,"fn":238,"description":239,"org":297,"tags":298,"stars":24,"repoUrl":25,"updatedAt":251},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[299,300,301,302,303],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":245,"slug":246,"type":15},{"name":195,"slug":196,"type":15},{"name":249,"slug":250,"type":15},{"slug":305,"name":305,"fn":306,"description":307,"org":308,"tags":309,"stars":24,"repoUrl":25,"updatedAt":320},"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},[310,311,314,317],{"name":23,"slug":8,"type":15},{"name":312,"slug":313,"type":15},"Database","database",{"name":315,"slug":316,"type":15},"MySQL","mysql",{"name":318,"slug":319,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":322,"name":322,"fn":323,"description":324,"org":325,"tags":326,"stars":24,"repoUrl":25,"updatedAt":333},"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},[327,328,329,332],{"name":23,"slug":8,"type":15},{"name":312,"slug":313,"type":15},{"name":330,"slug":331,"type":15},"PostgreSQL","postgresql",{"name":318,"slug":319,"type":15},"2026-07-16T06:00:34.789624",{"slug":335,"name":335,"fn":336,"description":337,"org":338,"tags":339,"stars":24,"repoUrl":25,"updatedAt":345},"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},[340,341,342],{"name":158,"slug":159,"type":15},{"name":23,"slug":8,"type":15},{"name":343,"slug":344,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":347,"name":347,"fn":348,"description":349,"org":350,"tags":351,"stars":24,"repoUrl":25,"updatedAt":360},"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},[352,353,354,357],{"name":23,"slug":8,"type":15},{"name":312,"slug":313,"type":15},{"name":355,"slug":356,"type":15},"MongoDB","mongodb",{"name":358,"slug":359,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":362,"name":362,"fn":363,"description":364,"org":365,"tags":366,"stars":24,"repoUrl":25,"updatedAt":370},"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},[367,368,369],{"name":23,"slug":8,"type":15},{"name":312,"slug":313,"type":15},{"name":358,"slug":359,"type":15},"2026-07-16T06:00:37.690386",115]