Lambda handler function structure in AWS - Step-by-Step Execution

Process Flow - Lambda handler function structure

Event received

↓

Lambda handler invoked

↓

Process event data

↓

Perform logic or call services

↓

Return response or error

↓

Lambda execution ends

This flow shows how AWS Lambda receives an event, runs the handler function, processes data, and returns a response.

Execution Sample

AWS

def lambda_handler(event, context):
    message = event.get('message', 'Hello')
    return {'statusCode': 200, 'body': message}

A simple Lambda handler that reads a message from the event and returns it with a 200 status.

Process Table

Step	Action	Input	Output	Notes
1	Lambda receives event	{"message": "Hi"}	Invoke lambda_handler	Event triggers function
2	Extract message	event.get('message', 'Hello')	"Hi"	Reads 'message' key from event
3	Prepare response	statusCode=200, body='Hi'	{"statusCode": 200, "body": "Hi"}	Response formatted as dict
4	Return response	response dict	Function returns response	Lambda execution ends

💡 Function returns response dict, Lambda execution completes

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
event	{"message": "Hi"}	{"message": "Hi"}	{"message": "Hi"}	{"message": "Hi"}
message	N/A	"Hi"	"Hi"	"Hi"
response	N/A	N/A	{"statusCode": 200, "body": "Hi"}	{"statusCode": 200, "body": "Hi"}

Key Moments - 3 Insights

Why do we use event.get('message', 'Hello') instead of event['message']?

Using event.get('message', 'Hello') safely returns 'Hello' if 'message' is missing, avoiding errors. See execution_table step 2 where message is extracted.

What is the role of the context parameter in the handler?

Context provides info about the Lambda execution environment but is not used here. The handler must accept it even if unused.

Why must the handler return a dictionary with statusCode and body?

This format is required for API Gateway integrations to understand the response. See execution_table step 3 for response preparation.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'message' after step 2?

A "Hello"

B None

C "Hi"

D Error

💡 Hint

Check the 'Output' column in step 2 of execution_table where message is extracted.

At which step does the Lambda function prepare the response dictionary?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Action' column in execution_table for response preparation.

If the event did not have a 'message' key, what would 'message' be after step 2?

A "Hi"

B "Hello"

C None

D Error

💡 Hint

Refer to the default value in event.get('message', 'Hello') in the code sample.

Concept Snapshot

AWS Lambda handler is a function with two parameters: event and context.
It processes the event data and returns a response dictionary.
Use event.get() to safely access event keys.
Return format often includes statusCode and body for API Gateway.
The context parameter provides runtime info but can be unused.

Full Transcript

AWS Lambda runs a handler function when triggered by an event. The handler takes two inputs: event and context. The event contains data that triggered the function. The handler processes this data, often extracting values safely using event.get(). It then prepares a response, usually a dictionary with statusCode and body keys, and returns it. The context parameter provides information about the execution environment but is optional to use. The function ends after returning the response.