AWS Advisor
diegosouzapw/awesome-omni-skills
AWS Advisor workflow skill. An agent skill from diegosouzapw/awesome-omni-skills.
Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment.
Install Connecting Lambda To API Gateway
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-lambda-to-api-gateway --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway .claude/skills/connecting-lambda-to-api-gateway && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "connecting-lambda-to-api-gateway" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway into .claude/skills/connecting-lambda-to-api-gateway/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-lambda-to-api-gateway", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gatewayType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-lambda-to-api-gateway --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway .agents/skills/connecting-lambda-to-api-gateway && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "connecting-lambda-to-api-gateway" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway into .agents/skills/connecting-lambda-to-api-gateway/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-lambda-to-api-gateway", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-lambda-to-api-gateway --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway .cursor/skills/connecting-lambda-to-api-gateway && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "connecting-lambda-to-api-gateway" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway into .cursor/skills/connecting-lambda-to-api-gateway/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-lambda-to-api-gateway", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws/agent-toolkit-for-aws.git --path skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-lambda-to-api-gateway --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway .gemini/skills/connecting-lambda-to-api-gateway && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "connecting-lambda-to-api-gateway" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway into .gemini/skills/connecting-lambda-to-api-gateway/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-lambda-to-api-gateway", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws/agent-toolkit-for-aws connecting-lambda-to-api-gatewayInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway .github/skills/connecting-lambda-to-api-gateway && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "connecting-lambda-to-api-gateway" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway into .github/skills/connecting-lambda-to-api-gateway/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-lambda-to-api-gateway", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws connecting-lambda-to-api-gateway --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway .opencode/skills/connecting-lambda-to-api-gateway && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "connecting-lambda-to-api-gateway" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway into .opencode/skills/connecting-lambda-to-api-gateway/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connecting-lambda-to-api-gateway", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
connecting-lambda-to-api-gateway- GitHub stars
- 2.8k
- Token cost
- ~422 tokens
- SKILL.md length
- 168 words
- Files
- 2 (incl. references)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment.
- Connecting Lambda to API Gateway — it handles CORS
- SKILL.md covers Overview, Connect a Lambda function to… and Troubleshooting
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Production security hardening that are easy to miss
What it does
Connecting Lambda To API Gateway is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment. Always use this skill when connecting Lambda to API Gateway — it handles CORS, throttling, access logging, and production security hardening that are easy to miss.
Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/lambda-gateway-api.md`).
It sits in Backend & APIs, covering Microservices, Serverless and REST APIs. It works with AWS Lambda and Amazon Web Services. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.
When your agent uses it
- Connecting Lambda to API Gateway — it handles CORS
- Production security hardening that are easy to miss
Example prompts
- “Use the connecting-lambda-to-api-gateway skill to connect an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with…”
- “/connecting-lambda-to-api-gateway”
What it can do on your machine
Read from SKILL.md and the folder at commit 188af2f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Connecting Lambda To API Gateway loads about 422 tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 168 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws/agent-toolkit-for-aws at commit 188af2f, republished under its Apache-2.0 licence (© aws). 168 words, ~422 tokens.
Download SKILL.mdSave it as
.claude/skills/connecting-lambda-to-api-gateway/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- connecting-lambda-to-api-gateway
- description
- Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment. Always use this skill when connecting Lambda to API Gateway — it handles CORS, throttling, access logging, and production security hardening that are easy to miss.
- version
- 1
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.
Permission denied invoking Lambda
Ensure lambda:InvokeFunction permission was added with the correct API Gateway
source ARN. See the full procedure for details.
CORS errors in browser
Verify enable_cors was set to true, the OPTIONS method was created, and CORS
headers are configured in both method and integration responses.
© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway of aws/agent-toolkit-for-aws.
- SKILL.md
- references/lambda-gateway-api.md
Open the folder on GitHubat commit 188af2f
Compare with similar skills
Connecting Lambda To API Gateway next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Connecting Lambda To API Gateway this skillaws/agent-toolkit-for-aws | 2.8k | — | ~422 | Automated safety check: Pass | Apache-2.0 | |
| AWS Advisordiegosouzapw/awesome-omni-skills | 159 | — | ~4.3k | Automated safety check: Pass | MIT | |
| AWS Serverless Edazxkane/aws-skills | 367 | 4 repos | ~3.2k | Automated safety check: Pass | MIT | |
| AWS Lambda Durable Functionsawslabs/agent-plugins | 915 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| AWS Lambda Java Integrationgiuseppe-trisciuoglio/developer-kit | 355 | — | ~1.9k | Automated safety check: Notes | MIT | |
| AWS Lambda Php Integrationgiuseppe-trisciuoglio/developer-kit | 355 | — | ~2.3k | Automated safety check: Notes | MIT |
Similar skills
AWS Serverless Eda
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
- Official
AWS Lambda Durable Functions
awslabs/agent-plugins
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.
AWS Lambda Java Integration
giuseppe-trisciuoglio/developer-kit
Provides AWS Lambda integration patterns for Java with cold start optimization.
AWS Lambda Php Integration
giuseppe-trisciuoglio/developer-kit
Provides AWS Lambda integration patterns for PHP with Symfony using the Bref framework.
AWS Lambda Python Integration
giuseppe-trisciuoglio/developer-kit
Provides AWS Lambda integration patterns for Python with cold start optimization.
More from aws/agent-toolkit-for-aws
All 138 skills in this repo- Official
Agent Advisor
aws/agent-toolkit-for-aws
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
- Official
Launch With AWS
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
- Official
Processing S3 Uploads With Step Functions
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
- Official
Agents Pay
aws/agent-toolkit-for-aws
A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.
Related
Works with
Categories
Questions about Connecting Lambda To API Gateway
What does Connecting Lambda To API Gateway do?
Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment. Connecting Lambda To API Gateway is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment.
When should I use Connecting Lambda To API Gateway?
Connecting Lambda To API Gateway fits situations like: connecting Lambda to API Gateway — it handles CORS; production security hardening that are easy to miss.
How do I install Connecting Lambda To API Gateway in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a claude-code`. Or copy the skill folder (skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway in aws/agent-toolkit-for-aws) into .claude/skills/connecting-lambda-to-api-gateway in your project. Claude Code loads it when a task matches its description.
How do I install Connecting Lambda To API Gateway in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a codex`. Or copy the skill folder (skills/specialized-skills/serverless-skills/connecting-lambda-to-api-gateway in aws/agent-toolkit-for-aws) into .agents/skills/connecting-lambda-to-api-gateway in your project. Codex loads it when a task matches its description.
Can I use Connecting Lambda To API Gateway in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill connecting-lambda-to-api-gateway -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/connecting-lambda-to-api-gateway, .gemini/skills/connecting-lambda-to-api-gateway, .github/skills/connecting-lambda-to-api-gateway and .opencode/skills/connecting-lambda-to-api-gateway in your project.
What does Connecting Lambda To API Gateway need to run?
SKILL.md names no scripts, command-line tools or credentials: Connecting Lambda To API Gateway is instructions for the agent only.
Does Connecting Lambda To API Gateway access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Connecting Lambda To API Gateway safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Connecting Lambda To API Gateway use?
Connecting Lambda To API Gateway is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Connecting Lambda To API Gateway use?
About 422 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Connecting Lambda To API Gateway?
Skills that share tags, products or a category with Connecting Lambda To API Gateway: AWS Advisor (diegosouzapw/awesome-omni-skills, 159 stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars), AWS Lambda Durable Functions (awslabs/agent-plugins, 915 stars) and AWS Lambda Java Integration (giuseppe-trisciuoglio/developer-kit, 355 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Connecting Lambda To API Gateway?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,825 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.
Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.