AWS
AWS Serverless API Architecture
This AWS serverless architecture diagram shows a small HTTP API. Internet traffic reaches Amazon API Gateway, which invokes AWS Lambda. The function reads or writes data in Amazon DynamoDB, handles files in Amazon S3 and sends logs to Amazon CloudWatch. It is a clear starting point for teams documenting an API without servers or a separate application tier.
Make this diagram your own.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
CASE ANALYSIS
Scenario
A serverless HTTP API on AWS.
Key decisions
- Public endpoint: API Gateway receives HTTPS requests.
- Compute: Lambda handles the API logic.
- Managed services: DynamoDB, S3 and CloudWatch provide data, files and logs.
When to reuse this
Use this diagram for a small serverless API that reads data, stores files and writes logs.
FAQ
Frequently asked questions
What receives the HTTP request?
Amazon API Gateway is the public HTTPS endpoint in this example.
Where does the API logic run?
AWS Lambda runs the API logic after API Gateway receives a request.
What is DynamoDB used for?
Amazon DynamoDB is the managed database shown for application data.
Open this example in the editor →
Tweak it with chat, export PNG/SVG, or fork it for your own use case.
network-aws-serverless-api-architecture