skills.rest
obispobruno
obispobrunoCOMMUNITY
Explore all skills by this author →
GitHub

aws-serverless

Builds, deploys, and troubleshoots AWS serverless applications using Lambda, API Gateway, and Step Functions.

1|Updated Aug 1, 2024
Search Tags:#troubleshooting#serverless#aws#api gateway#lambda#sam#step functions
One-click install
npx skills add https://github.com/obispobruno/dotfiles --skill aws-serverless-obispobruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-serverless
Source: https://github.com/obispobruno/dotfiles/tree/main/dot_agents/skills/aws-serverless
Command: npx skills add https://github.com/obispobruno/dotfiles --skill aws-serverless-obispobruno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aws-lambda-powertools, and includes references (resource) and assets (resource) components.

What problem does it solve? Building serverless applications on AWS involves dozens of non-obvious quotas, mutual-exclusivity rules, and error patterns (502 proxy responses, CORS misconfigurations, concurrency throttling, cold starts) that are easy to get wrong and hard to debug without deep platform experience. ## Core Features & Use Cases - Architecture and pattern selection: Route workloads to the right pattern (REST/HTTP API, event processing, orchestration, streaming, fan-out, scheduled jobs) with default-vs-alternative service choices. - Configuration and quota guidance: Exact values for Lambda memory/timeout, concurrency controls (reserved, provisioned, ESM Maximum Concurrency, Provisioned Mode), API Gateway throttling, and event source mapping parameters. - Error-driven troubleshooting: Exact error strings (502, 504, SnapStartException, States.DataLimitExceeded, Function URL 403) mapped to causes and CLI fixes, plus CloudWatch Logs Insights diagnostic queries. - Use Case: A developer's API Gateway endpoint returns 502 errors after connecting a Lambda function. The skill identifies the malformed proxy response shape, provides the corrected handler, and routes to the connecting-lambda-to-api-gateway procedure for CORS and throttling setup. ## Quick Start Ask the assistant to help build or debug an AWS serverless application, for example: help me connect my Lambda function to API Gateway with CORS and fix the 502 errors I'm seeing.

Frequently Asked Questions about aws-serverless

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

FAQPage Schema
How do I fix a 502 Bad Gateway error from API Gateway with Lambda?▼

A 502 under Lambda proxy integration means the response shape is malformed. The function must return an object with statusCode, headers, and a body that is a JSON-stringified string, not a raw object. The function itself ran fine; only the response format was wrong.

Should I use Step Functions or Lambda durable functions for workflow orchestration?▼

Use Step Functions when orchestration primarily calls AWS services directly, needs a visual auditable definition, or coordinates non-Lambda compute like ECS or Glue. Use Lambda durable functions for code-first orchestration inside an existing Lambda codebase with many fine-grained steps.

What is the difference between reserved and provisioned concurrency in Lambda?▼

Reserved concurrency caps and reserves capacity for a function, protecting downstream systems, but cold starts still occur. Provisioned concurrency pre-initializes environments to eliminate cold starts and is paid even when idle. Provisioned must be less than or equal to reserved when both are set.

Can I use SnapStart and Provisioned Concurrency together on one Lambda function?▼

No, SnapStart and Provisioned Concurrency are mutually exclusive on the same function. SnapStart supports Java 11+, Python 3.12+, and .NET 8+; for other runtimes or strict sub-50ms requirements, use Provisioned Concurrency instead.

Why does my public Lambda Function URL return 403 Forbidden?▼

Invoking a Function URL always requires both lambda:InvokeFunctionUrl and lambda:InvokeFunction permissions. With AuthType NONE, the resource-based policy must grant both actions via two separate add-permission calls, with the second scoped by the invoked-via-function-url condition.

When should I choose HTTP API versus REST API in API Gateway?▼

Default to HTTP API for lower latency, lower cost, native JWT authorization, and built-in CORS. Choose REST API only when you need API keys, usage plans, request validation, built-in caching, WAF, private endpoints, or edge-optimized deployment.

Related Skills

Explore More Software Engineering Skills→
librefanglibrefang
10

aws

Architect and deploy AWS infrastructure using CloudFormation, CDK, and the AWS CLI.

Official
Advanced
awslabsawslabs
15

observability

Design AWS observability solutions with CloudWatch metrics, logs, alarms, and X-Ray tracing.

Official
Advanced
wesleyosantos91wesleyosantos91
6

aws-iac-patterns

Implement secure multi-environment AWS infrastructure patterns with Terraform.

Community
Advanced
mauriciodelriomauriciodelrio
3

compute

Compare serverless, container, VM, and edge platforms for application workloads.

Community
Intermediate