creating-api-gateway-stage — Claude Code skill for API Gateway
Builds an API Gateway stage with CloudWatch logging, X-Ray tracing, throttling and WAF. Handy when a REST API ships to dev, test or production.
npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a claude-codeWhat creating-api-gateway-stage does
This skill hands the agent a fixed procedure for standing up an API Gateway stage. You get CloudWatch logging, X-Ray tracing, throttling, a WAF web ACL association, method-level settings and authorization choices. The package holds SKILL.md plus a reference file, references/create-api-gateway-stage.md, that spells out the steps in order. The agent follows that instead of improvising a stage.
Logging has to be switched on in two places: the stage and the individual methods. When nothing shows up in CloudWatch, the usual suspects are the CloudWatch role's permissions, a missing log group, or one of those two levels left off. Stage creation itself fails on a wrong REST API ID or deployment ID, thin IAM permissions, or a stage name that breaks AWS naming conventions.
WAF is the other common snag. It can block traffic you actually want, so you review the WAF logs and either loosen the rules or add exceptions; count mode helps while you test. Everything runs against a live AWS account, so IAM permissions and your API identifiers need to be in place first.
What it helps with
- create an API Gateway stage with logging and tracing
- split dev, test and production across separate stages
- attach a WAF web ACL to a REST API
- set throttling per method
- debug missing CloudWatch logs
Example prompts for the agent
- Create a production API Gateway stage with CloudWatch logging and X-Ray tracing
- Why are no CloudWatch logs showing up for my stage?
- WAF is blocking legitimate requests to my API — what should I change?
How to install creating-api-gateway-stage
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a claude-code2Manually: put the files in place
~/.claude/skills/creating-api-gateway-stage/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/creating-api-gateway-stage/
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a codex2Manually: put the files in place
.agents/skills/creating-api-gateway-stage/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a cursor2Manually: put the files in place
.cursor/skills/creating-api-gateway-stage/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aws/agent-toolkit-for-aws creating-api-gateway-stage2Manually: put the files in place
.github/skills/creating-api-gateway-stage/SKILL.md1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a gemini-cli2Platform CLI
gemini skills install https://github.com/aws/agent-toolkit-for-aws --path skills/specialized-skills/serverless-skills/creating-api-gateway-stageManually: put the files in place
.devin/skills/creating-api-gateway-stage/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about creating-api-gateway-stage
How do I install creating-api-gateway-stage in Claude Code?
Run npx skills add aws/agent-toolkit-for-aws --skill creating-api-gateway-stage -a claude-code. The skill lands at ~/.claude/skills/creating-api-gateway-stage/SKILL.md.
What does creating-api-gateway-stage do?
It walks the agent through creating an API Gateway stage: CloudWatch logging, X-Ray tracing, throttling, WAF and IAM roles. It also covers troubleshooting — missing logs, failed stage creation, WAF blocking traffic.
What do I need before using it?
An AWS account with IAM permissions for API Gateway and CloudWatch, plus your REST API ID and deployment ID. Without them stage creation fails.
Source text
SKILL.md · Apache-2.0
--- name: creating-api-gateway-stage description: Creates an API Gateway stage with CloudWatch logging, X-Ray tracing, throttling, WAF integration, and IAM roles following AWS best practices. Use when deploying a REST API to different environments such as dev, test, or production. version: 1 --- # Creating an API Gateway Stage ## Overview Domain expertise for creating and configuring API Gateway stages with comprehensive logging, monitoring, security, and throttling controls. Covers CloudWatch logging setup, X-Ray tracing, WAF web ACL association, method-level configuration, and authorization options. ## Create an API Gateway stage To create a fully configured API Gateway stage with logging, throttling, WAF, and authorization, follow the procedure exactly. See [API Gateway stage creation procedure](references/create-api-gateway-stage.md). ## Troubleshooting ### CloudWatch logs not appearing Verify the CloudWatch role permissions, log group existence, and that logging is enabled at both stage and method levels. See the [full procedure](references/create-api-gateway-stage.md) for details. ### Stage creation fails Check REST API ID, deployment ID, IAM permissions, and stage naming conventions. ### WAF blocking legitimate requests Review WAF logs, adjust rules or add exceptions, and consider count mode for testing.
© aws · Apache-2.0 · aws/agent-toolkit-for-aws