Lambda function concept in AWS - Time & Space Complexity

Time Complexity: Lambda function concept

O(n)

Understanding Time Complexity

We want to understand how the time to run a Lambda function changes as we increase the number of events it handles.

How does the number of events affect the total work Lambda does?

Scenario Under Consideration

Analyze the time complexity of invoking a Lambda function multiple times.

// Pseudocode for invoking Lambda multiple times
for (int i = 0; i < n; i++) {
  aws lambda invoke --function-name MyFunction --payload '{"key": "value"}' response.json
}
    

This sequence calls the same Lambda function n times, each with a small input.

Identify Repeating Operations

Look at what repeats as we increase n.

• Primary operation: Lambda function invocation API call
• How many times: Exactly n times, once per loop iteration

How Execution Grows With Input

Each new event causes one Lambda call, so the total calls grow directly with n.

Input Size (n)	Approx. API Calls/Operations
10	10 Lambda invocations
100	100 Lambda invocations
1000	1000 Lambda invocations

Pattern observation: The number of Lambda calls grows in a straight line as n increases.

Final Time Complexity

Time Complexity: O(n)

This means if you double the number of events, the total Lambda calls double too.

Common Mistake

[X] Wrong: "Calling Lambda multiple times is just one operation regardless of n."

[OK] Correct: Each Lambda call is a separate operation that takes time, so more calls mean more total work.

Interview Connect

Understanding how repeated Lambda calls add up helps you design systems that scale well and explain your reasoning clearly.

Self-Check

"What if we changed the Lambda function to process multiple events in one call? How would the time complexity change?"

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