connecting-lambda-to-api-gateway

What problem does it solve?

Connecting an existing AWS Lambda function to API Gateway is easy to get wrong, often leaving out critical production settings like permissions, CORS handling, throttling, and access logging.

Core Features & Use Cases

• Lambda proxy integration setup: Wires API Gateway to invoke Lambda using AWS_PROXY with the correct integration URI format.
• Authorization, API keys, and CORS: Supports NONE/AWS_IAM/COGNITO_USER_POOLS/CUSTOM, optional API key enforcement, and conditional CORS configuration including OPTIONS support.
• Production security hardening: Guides recommended controls such as throttling/usage plans and access logging, plus notes on deployment risks and troubleshooting common integration failures.
• Use case: Expose an internal “create-order” Lambda endpoint behind an API Gateway REST API for frontend consumption with proper browser CORS behavior and hardened production controls.

Quick Start

Use this skill to connect your existing Lambda function to a new API Gateway REST API by providing the required Lambda name and API name, then deploy to your chosen stage.