AWS category
Serverless
Generated July 9, 2026
Event-driven compute, APIs, workflows, storage, and integrations without server management.
Serverless services
12 entries| Service | Category | Production use | Before production | Link |
|---|---|---|---|---|
Build, deploy, and manage APIs | Serverless | Expose REST, HTTP, or WebSocket APIs for production apps. | Use stages, custom domains, auth, throttling, request validation, logging, WAF where needed, and canary deployments. | Docs |
Choose a modern application development approach | Serverless | Use for event-driven APIs, background processing, workflows, and apps without server management. | Design idempotency, concurrency limits, retries/DLQs, observability, cold-start needs, IAM boundaries, and deployment aliases. | Docs |
Managed NoSQL database | Serverless | Run low-latency NoSQL tables for serverless and high-scale applications. | Design keys carefully, enable PITR, autoscaling/on-demand capacity, GSIs, TTL, streams if needed, alarms for throttles, and access policies. | Docs |
Serverless event bus for SaaS apps and AWS services | Serverless | Build event-driven production integrations across services and SaaS apps. | Define schemas, DLQs, retries, event archive/replay, bus permissions, and alarms on failed invocations. | Docs |
Serverless compute for containers | Serverless | Use for event-driven APIs, background processing, workflows, and apps without server management. | Design idempotency, concurrency limits, retries/DLQs, observability, cold-start needs, IAM boundaries, and deployment aliases. | Docs |
Run code without thinking about servers | Serverless | Run event-driven APIs, scheduled jobs, webhooks, stream processors, and lightweight backend logic. | Use versions/aliases, reserved concurrency, retries/DLQ, structured logs, tracing, secrets from managed stores, and alarms on errors/throttles/duration. | Docs |
Introduction to core serverless concepts and services in the AWS Cloud | Serverless | Use for event-driven APIs, background processing, workflows, and apps without server management. | Design idempotency, concurrency limits, retries/DLQs, observability, cold-start needs, IAM boundaries, and deployment aliases. | Docs |
Pub/sub, SMS, email, and mobile push notifications | Serverless | Fan out production notifications to queues, functions, HTTP endpoints, SMS, or email. | Use topic policies, retries/DLQs, filtering, encryption, delivery logs, and subscription confirmation controls. | Docs |
Object storage built to retrieve any amount of data from anywhere | Serverless | Store static assets, uploads, backups, data lakes, logs, artifacts, and serverless event sources. | Block public access by default, enable encryption/versioning/lifecycle, use bucket policies, CloudFront for public assets, and replication where needed. | Docs |
Coordinate components for distributed applications | Serverless | Orchestrate multi-step production workflows and long-running business processes. | Use retries/catches, timeouts, idempotent tasks, execution history retention, versioning, and alarms on failures. | Docs |
Accelerate app development with fully-managed, scalable GraphQL APIs | Serverless | Use for event-driven APIs, background processing, workflows, and apps without server management. | Design idempotency, concurrency limits, retries/DLQs, observability, cold-start needs, IAM boundaries, and deployment aliases. | Docs |
Managed message queues | Serverless | Buffer work between services and absorb production traffic spikes. | Use DLQs, visibility timeout, idempotent consumers, encryption, backlog alarms, and redrive procedures. | Docs |
No matching service guidance found.