Lambda function concept in AWS - Step-by-Step Execution

Process Flow - Lambda function concept

Event triggers Lambda

↓

Lambda receives event

↓

Lambda runs code

↓

Code processes event

↓

Lambda returns result

↓

Result sent back or action taken

This flow shows how a Lambda function is triggered by an event, runs code, processes the event, and returns a result or takes action.

Execution Sample

AWS

def lambda_handler(event, context):
    name = event.get('name', 'World')
    return f"Hello, {name}!"

A simple Lambda function that greets a name from the event or says 'Hello, World!' if no name is given.

Process Table

Step	Action	Input Event	Code Execution	Output
1	Lambda triggered	{"name": "Alice"}	lambda_handler called with event	Waiting for code to run
2	Extract 'name'	{"name": "Alice"}	name = 'Alice'	name set to 'Alice'
3	Return greeting	{"name": "Alice"}	return 'Hello, Alice!'	'Hello, Alice!'
4	Lambda completes	{"name": "Alice"}	Function ends	Output sent: 'Hello, Alice!'

💡 Lambda finishes after returning the greeting string.

Status Tracker

Variable	Start	After Step 2	Final
event	{"name": "Alice"}	{"name": "Alice"}	{"name": "Alice"}
name	undefined	"Alice"	"Alice"
output	undefined	undefined	"Hello, Alice!"

Key Moments - 2 Insights

Why does the Lambda function need an 'event' parameter?

The 'event' parameter carries the input data that triggers the Lambda. Without it, the function wouldn't know what to process. See execution_table step 1 where the event is passed in.

What happens if the event does not contain the 'name' key?

The code uses a default value 'World' if 'name' is missing, so the function still returns a greeting. This is shown in the code line with event.get('name', 'World').

Visual Quiz - 3 Questions

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

A "Alice"

B "World"

C undefined

D null

💡 Hint

Check the 'Code Execution' and 'Output' columns at step 2 in execution_table.

At which step does the Lambda function return the greeting?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for the 'Return greeting' action in the execution_table.

If the event was empty {}, what would the output be?

A "Hello, Alice!"

B "Hello, World!"

C Error

D No output

💡 Hint

Refer to the code line using event.get('name', 'World') in execution_sample.

Concept Snapshot

AWS Lambda runs code in response to events.
It receives an 'event' input and a 'context'.
Code processes the event and returns a result.
No server management needed.
Ideal for small, quick tasks triggered by events.

Full Transcript

AWS Lambda is a service that runs your code when something happens, like a file upload or a web request. The code you write is called a Lambda function. It always receives an input called 'event' that contains information about what triggered it. The function runs your code using this event data and then returns a result or performs an action. You don't have to manage servers; AWS handles that for you. This example shows a simple Lambda function that greets a name from the event or says 'Hello, World!' if no name is provided.

Practice

1. What is the main purpose of an AWS Lambda function?

easy

A. To store large amounts of data

B. To run code automatically without managing servers

C. To create virtual machines

D. To manage user permissions

Solution

1. Step 1: Understand Lambda's role

   AWS Lambda runs your code without needing you to manage servers.

2. Step 2: Compare options

   Options A, C, and D describe other AWS services, not Lambda.

3. Final Answer:

   To run code automatically without managing servers -> Option B

4. Quick Check:

   Lambda = serverless code execution [OK]

Hint: Lambda runs code without servers, not storage or VMs [OK]

Common Mistakes:

• Confusing Lambda with storage services
• Thinking Lambda creates virtual machines
• Assuming Lambda manages user permissions

2. Which of the following is the correct way to define a simple AWS Lambda function handler in Python?

easy

A. lambda handler(event): print('Hello World')

B. function handler(event) { return 'Hello World'; }

C. def handler(event, context): return 'Hello World'

D. def handler(): print('Hello World')

Solution

1. Step 1: Identify correct Python Lambda handler syntax

   Lambda handlers in Python must accept two parameters: event and context.

2. Step 2: Check each option

   def handler(event, context): return 'Hello World' correctly defines a Python function with event and context parameters and returns a string. function handler(event) { return 'Hello World'; } is JavaScript syntax. lambda handler(event): print('Hello World') misuses lambda keyword. def handler(): print('Hello World') lacks required parameters.

3. Final Answer:

   def handler(event, context): return 'Hello World' -> Option C

4. Quick Check:

   Python Lambda handler needs event and context [OK]

Hint: Python Lambda handlers always have (event, context) parameters [OK]

Common Mistakes:

• Using JavaScript syntax in Python Lambda
• Omitting event or context parameters
• Misusing lambda keyword for handler

3. Given this AWS Lambda Python code:

def handler(event, context):
    name = event.get('name', 'Guest')
    return f"Hello, {name}!"

What will be the output if the event is {}?

medium

A. "Hello, Guest!"

B. "Hello, None!"

C. Error: 'name' key missing

D. "Hello, !"

Solution

1. Step 1: Analyze event input and code behavior

   The event is an empty dictionary, so event.get('name', 'Guest') returns the default 'Guest'.

2. Step 2: Determine return value

   The function returns the string "Hello, Guest!" because 'name' is not in event.

3. Final Answer:

   "Hello, Guest!" -> Option A

4. Quick Check:

   Missing key uses default value 'Guest' [OK]

Hint: event.get with default returns default if key missing [OK]

Common Mistakes:

• Assuming missing key causes error
• Thinking None is returned instead of default
• Ignoring default value in get()

4. You wrote this AWS Lambda function in Python:

def handler(event, context):
    return event['message']

When triggered with event {}, it throws a KeyError. How can you fix it?

medium

A. Use event.get('message', 'No message') instead of event['message']

B. Remove the return statement

C. Add a print statement before return

D. Change function name to lambda_handler

Solution

1. Step 1: Identify cause of KeyError

   Accessing event['message'] when 'message' key is missing causes KeyError.

2. Step 2: Use safe access method

   Replacing event['message'] with event.get('message', 'No message') avoids error by providing default.

3. Final Answer:

   Use event.get('message', 'No message') instead of event['message'] -> Option A

4. Quick Check:

   Use get() to avoid KeyError on missing keys [OK]

Hint: Use get() with default to prevent KeyError [OK]

Common Mistakes:

• Ignoring missing key causes error
• Thinking print fixes KeyError
• Assuming function name affects key access

5. You want an AWS Lambda function to process image uploads to S3 and resize them. Which combination of AWS services and Lambda features is best suited for this task?

hard

A. Use Lambda to create EC2 instances that resize images

B. Run Lambda on a schedule to scan S3 and resize images manually

C. Upload images directly to Lambda storage for resizing

D. Use S3 event trigger on object creation to invoke Lambda, which resizes images and saves back to S3

Solution

1. Step 1: Understand event-driven processing

   S3 can trigger Lambda automatically when new objects are created, ideal for immediate processing.

2. Step 2: Evaluate options for image resizing

   Use S3 event trigger on object creation to invoke Lambda, which resizes images and saves back to S3 uses S3 event triggers and Lambda to resize and save images back to S3, which is efficient and serverless. Run Lambda on a schedule to scan S3 and resize images manually delays processing and requires scanning. Use Lambda to create EC2 instances that resize images misuses Lambda to create servers. Upload images directly to Lambda storage for resizing is invalid as Lambda has no persistent storage for uploads.

3. Final Answer:

   Use S3 event trigger on object creation to invoke Lambda, which resizes images and saves back to S3 -> Option D

4. Quick Check:

   S3 event triggers + Lambda = best for image processing [OK]

Hint: Use S3 event triggers to run Lambda on uploads [OK]

Common Mistakes:

• Thinking Lambda can store files persistently
• Using scheduled scans instead of event triggers
• Misusing Lambda to create servers