You open your todo list · Lambda + DynamoDB

10 steps from your browser to the database and back.

Runs on

EC2 ECS on Fargate Lambda

Database

RDS MySQL DynamoDB

Action

Add-ons

Background job Live updates

Text version of this diagram.

What sits where:

AWS Region · us-east-1: A Region is a part of the world where AWS has data centers. Most things you build live in one Region. us-east-1 is in northern Virginia. contains:
- API Gateway (HTTP API · front door): The front door for the app's web requests: it receives each one and hands it to your code. An HTTP API is its simple kind for ordinary requests.
- CloudWatch Logs (app log lines): Collects the lines your app writes about what it's doing (its logs), so you can search them later.
- Lambda function (runs once per request): Code that AWS runs only when a request arrives. No server to look after, and you pay per request.
- DynamoDB (Todo.io's tables): AWS's serverless NoSQL database: you store and fetch items by key, and it scales by itself with no server to manage.
Your browser (on the internet)
IAM (global · who can do what): Identity and Access Management: decides who (and which app) may do what in AWS. It's global, the same in every Region.

Steps, in order:

You open your todo list. Path: Your browser. Your browser sends GET /todos over HTTPS.
Into the front door. Path: Your browser → API Gateway. The request arrives at API Gateway, a managed HTTPS front door. There's no server or firewall for you to look after.
Wake up the function. Path: API Gateway → Lambda function. API Gateway invokes your Lambda function and hands it the request as an event. Checks: iam: Lambda resource policy: API Gateway may invoke todo-api → allow.
Who are you?. Path: Lambda function. The app checks your signed session cookie and finds your user id, u-123. This is the app's own login, not AWS.
Get AWS credentials. Path: Lambda function. The app gets temporary credentials for its IAM role (the execution role) which Lambda already put in its environment variables. No keys are stored in the code.
Call DynamoDB. Path: Lambda function → DynamoDB. The function calls Query on the DynamoDB API over HTTPS, signed with those credentials.
Is this allowed?. Path: DynamoDB → IAM. DynamoDB checks with IAM: may todo-app-lambda-role do dynamodb:Query here? The policy on the role allows it on the table's ARN. Checks: iam: todo-app-lambda-role: dynamodb:Query on table/Todos → allow.
DynamoDB answers. Path: DynamoDB → Lambda function. DynamoDB returns your 3 todo items.
Back to you. Path: Lambda function → API Gateway → Your browser. You get 200 OK with your todos, and the list appears.
Leave a note. Path: Lambda function → CloudWatch Logs. Lambda sends what the function printed to CloudWatch Logs, so Todo.io's engineers can see what happened.

Step 1 of 10

Your browser sends GET /todos over HTTPS.

Show me the real thing

The HTTP request

GET /todos HTTP/1.1
Host: abc123.execute-api.us-east-1.amazonaws.com
Cookie: session=eyJ1c2VySWQiOiJ1LTEyMyJ9.Zm9v

The request arrives at API Gateway, a managed HTTPS front door. There's no server or firewall for you to look after.
API Gateway invokes your Lambda function and hands it the request as an event.
- 🔑IAM Lambda resource policy: API Gateway may invoke todo-apiAllowed
Show me the real thing
Resource-based policy on the function: who may call it
```
{
  "Effect": "Allow",
  "Principal": {
    "Service": "apigateway.amazonaws.com"
  },
  "Action": "lambda:InvokeFunction",
  "Resource": "arn:aws:lambda:us-east-1:111122223333:function:todo-api",
  "Condition": {
    "ArnLike": {
      "AWS:SourceArn": "arn:aws:execute-api:us-east-1:111122223333:abc123/*"
    }
  }
}
```
Exam tipThis is a resource-based policy. It lives on the function and says who may call it, the opposite of a policy attached to a role.
The app checks your signed session cookie and finds your user id, u-123. This is the app's own login, not AWS.
The app gets temporary credentials for its IAM role (the execution role) which Lambda already put in its environment variables. No keys are stored in the code.
Show me the real thing
Trust policy on todo-app-lambda-role: who may use this role
```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "lambda.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}
```
Exam tipEvery Lambda function has exactly one execution role. Its permissions are everything your code can do in AWS.
The function calls Query on the DynamoDB API over HTTPS, signed with those credentials.
Show me the real thing
The Query request body
```
{
  "TableName": "Todos",
  "KeyConditionExpression": "userId = :u",
  "ExpressionAttributeValues": {
    ":u": {
      "S": "u-123"
    }
  }
}
```
Exam tipThis function isn't attached to a VPC, so it reaches DynamoDB directly. No VPC, no security groups.

DynamoDB checks with IAM: may todo-app-lambda-role do dynamodb:Query here? The policy on the role allows it on the table's ARN.

🔑IAM todo-app-lambda-role: dynamodb:Query on table/TodosAllowed

Show me the real thing

Permissions policy on todo-app-lambda-role

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "dynamodb:GetItem",
        "dynamodb:Query",
        "dynamodb:PutItem",
        "dynamodb:UpdateItem",
        "dynamodb:DeleteItem"
      ],
      "Resource": [
        "arn:aws:dynamodb:us-east-1:111122223333:table/Users",
        "arn:aws:dynamodb:us-east-1:111122223333:table/Todos"
      ]
    }
  ]
}

Exam tipIAM starts from deny. A request is only allowed if some policy explicitly allows it and nothing explicitly denies it.

DynamoDB returns your 3 todo items.
You get 200 OK with your todos, and the list appears.
Show me the real thing
The HTTP response
```
HTTP/1.1 200 OK
```
Lambda sends what the function printed to CloudWatch Logs, so Todo.io's engineers can see what happened.
Show me the real thing
The log line
```
2026-10-11T18:42:07Z INFO GET /todos user=u-123 status=200 14ms
```
Exam tipLambda sends whatever your function prints to CloudWatch Logs automatically, as long as the execution role allows logs:PutLogEvents.

What to notice

There is no server at all. API Gateway takes the request and Lambda runs your code only when one arrives.
IAM approved every database call, using a role. There's no database password anywhere.
DynamoDB isn't in your VPC. It's a public AWS service called over HTTPS.
You, the customer, were never an IAM user. IAM controls the app, not its customers.