Connecting Lambda To Api Gateway

If you've ever wired up Lambda to API Gateway manually and forgotten the invoke permission or botched the CORS setup, this walks you through the complete procedure. It handles REST API creation, resource and method configuration, Lambda proxy integration, and the security bits that are easy to skip like throttling and access logging. Supports different auth types including IAM, Cognito, and custom authorizers. The troubleshooting section covers the usual gotchas like 502 errors from malformed proxy responses and permission denied issues. Honestly most useful as a checklist to make sure you didn't miss something rather than learning this from scratch.

skills.sh installs: 7K
GitHub stars: 3.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway --agent claude-code

Installs into .claude/skills of the current project.

Files

Connecting Lambda to API Gateway

Overview

Domain expertise for creating Amazon API Gateway REST APIs and connecting them to existing Lambda functions. Covers API creation, resource and method setup, Lambda proxy integration, CORS configuration, security controls, deployment, and testing.

Connect a Lambda function to API Gateway

To create a REST API and wire it to a Lambda function, follow the procedure exactly. See Lambda to API Gateway connection procedure.

The procedure supports configurable authorization types (NONE, AWS_IAM, COGNITO_USER_POOLS, CUSTOM), optional API key requirements, CORS setup, and production security hardening including throttling and access logging.

Troubleshooting

502 Bad Gateway

The Lambda function must return a proxy-compatible response with statusCode, headers, and a stringified body. See the full procedure for format details.