apigateway

Manage Amazon API Gateway resources, deployments, and stages via AWS CLI.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/david-2814/claw-aws --skill apigateway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apigateway
Source: https://github.com/david-2814/claw-aws/tree/main/skills/apigateway
Command: npx skills add https://github.com/david-2814/claw-aws --skill apigateway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Amazon API Gateway resources (REST, HTTP, WebSocket), deployments, and stages via AWS CLI can be tedious and error-prone, especially across multiple APIs and environments.

Core Features & Use Cases

  • Create, configure, and deploy REST, HTTP, and WebSocket APIs, including resources, methods, integrations, and stages.
  • List, inspect, and manage APIs, deployments, stages, and authorizers to maintain visibility and control across environments.
  • Use cases include quickly provisioning new APIs for microservices, updating deployments for production readiness, and automating stage management for dev/stage/prod workflows.

Quick Start

Create a new HTTP API with a Lambda integration and deploy it to a prod stage.

Frequently Asked Questions about apigateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate API Gateway deployments using AWS CLI?

Automate API Gateway deployments using AWS CLI by programmatically managing REST, HTTP, and WebSocket APIs, including resources, methods, integrations, and stages across multiple environments. This enables consistent API lifecycle workflows for development, staging, and production without manual console configuration.

Can I manage WebSocket APIs through AWS CLI commands?

Yes, you can manage WebSocket APIs through AWS CLI commands alongside REST and HTTP APIs. The skill supports creating, configuring, and deploying WebSocket APIs, handling resources, methods, integrations, and stage management programmatically for consistent automated provisioning across environments.

What's the best way to provision new APIs for microservices across dev and prod environments?

Provision new APIs for microservices across dev and prod environments by automating stage management through AWS CLI commands. This approach maintains visibility and control over deployments and authorizers, ensuring consistent configuration updates for production readiness across multiple APIs and teams.

Does this approach support listing and inspecting existing API Gateway authorizers and stages?

Yes, this approach supports listing, inspecting, and managing existing API Gateway authorizers and stages. You can query deployed REST, HTTP, and WebSocket APIs via AWS CLI to maintain visibility and control over your API configurations across different environments.

How do I deploy an HTTP API with Lambda integration to a production stage?

Deploy an HTTP API with Lambda integration to a production stage by executing AWS CLI commands that create the API, configure the integration, and manage the stage. This automates the deployment workflow, ensuring production readiness without manual console intervention.

Why does managing API Gateway resources manually become error-prone across multiple APIs?

Managing API Gateway resources manually becomes error-prone across multiple APIs due to repetitive configuration of resources, methods, integrations, and stages. Automating these operations via AWS CLI eliminates human error and ensures consistent API lifecycle workflows across all environments.