Creating a Lambda function in AWS - Performance & Efficiency

Time Complexity: Creating a Lambda function

O(n)

Understanding Time Complexity

When creating a Lambda function, it's important to understand how the time to complete the setup grows as you add more resources or configurations.

We want to know how the number of steps or API calls changes as we create more Lambda functions.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

# Create a Lambda function
aws lambda create-function \
  --function-name MyFunction \
  --runtime python3.12 \
  --role arn:aws:iam::123456789012:role/lambda-role \
  --handler lambda_function.lambda_handler \
  --zip-file fileb://function.zip
    

This sequence creates one Lambda function with specified runtime, role, handler, and code package.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: The create-function API call to provision a Lambda function.
• How many times: Once per Lambda function created.

How Execution Grows With Input

Each Lambda function requires one API call to create it, so the total calls grow directly with the number of functions.

Input Size (n)	Approx. Api Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The number of API calls increases one-to-one with the number of Lambda functions created.

Final Time Complexity

Time Complexity: O(n)

This means the time to create Lambda functions grows linearly with how many you create.

Common Mistake

[X] Wrong: "Creating multiple Lambda functions can be done with a single API call, so time stays the same."

[OK] Correct: Each Lambda function requires its own create call; there is no batch create API, so time grows with the number of functions.

Interview Connect

Understanding how API calls scale when creating cloud resources shows you can plan for growth and manage deployment time effectively.

Self-Check

"What if we used a deployment tool that creates multiple Lambda functions in parallel? How would the time complexity change?"

Practice

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

easy

A. To run code without managing servers

B. To store large amounts of data

C. To create virtual machines

D. To manage user permissions

Solution

1. Step 1: Understand Lambda's role

   AWS Lambda lets you run code without needing to manage servers or infrastructure.

2. Step 2: Compare options

   The incorrect options describe other AWS services such as user permissions (IAM), data storage (S3), and virtual machines (EC2).

3. Final Answer:

   To run code without managing servers -> Option A

4. Quick Check:

   Lambda = serverless code execution [OK]

Hint: Lambda runs code without servers [OK]

Common Mistakes:

• Confusing Lambda with storage services
• Thinking Lambda manages servers
• Mixing Lambda with user management

2. Which of the following is the correct way to specify the handler when creating a Lambda function in AWS?

easy

A. handler.index

B. index.handler

C. lambda.handler

D. handler.lambda

Solution

1. Step 1: Understand handler format

   The handler is specified as filename.functionname. Commonly, the file is index and function is handler.

2. Step 2: Match options

   Only index.handler matches the correct format; others reverse or misuse parts.

3. Final Answer:

   index.handler -> Option B

4. Quick Check:

   Handler = filename.function [OK]

Hint: Handler format is filename.functionname [OK]

Common Mistakes:

• Swapping filename and function name
• Using invalid handler names
• Confusing handler with runtime

3. Given this AWS Lambda function code snippet in Python:

def handler(event, context):
    return event.get('key', 'default')

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

medium

A. "default"

B. None

C. Error

D. "key"

Solution

1. Step 1: Analyze the handler function

   The function returns the value of 'key' from event, or 'default' if 'key' is missing.

2. Step 2: Check the event input

   The event is an empty dictionary, so 'key' is not present, so it returns 'default'.

3. Final Answer:

   "default" -> Option A

4. Quick Check:

   Missing key returns default [OK]

Hint: Missing dict key returns default value [OK]

Common Mistakes:

• Assuming missing key returns None
• Expecting an error on missing key
• Confusing key name with value

4. You created a Lambda function but it fails with a permissions error when invoked. What is the most likely cause?

medium

A. The deployment package is too large

B. The handler name is incorrect

C. The runtime is not supported

D. The Lambda execution role lacks necessary permissions

Solution

1. Step 1: Understand permissions in Lambda

   Lambda functions need an IAM role with permissions to run and access resources.

2. Step 2: Identify cause of permissions error

   A permissions error usually means the execution role is missing required permissions.

3. Final Answer:

   The Lambda execution role lacks necessary permissions -> Option D

4. Quick Check:

   Permissions error = missing IAM role rights [OK]

Hint: Check IAM role permissions for Lambda [OK]

Common Mistakes:

• Blaming handler name for permissions error
• Ignoring IAM role setup
• Assuming runtime causes permissions error

5. You want to create a Lambda function that processes images uploaded to an S3 bucket. Which combination of settings is required to ensure the Lambda runs automatically when a new image is uploaded?

hard

A. Set Lambda runtime to Node.js and upload images directly to Lambda

B. Manually invoke Lambda after uploading images to S3

C. Set S3 event trigger on bucket for 'ObjectCreated' and assign Lambda execution role with S3 read permissions

D. Create an EC2 instance to monitor S3 and call Lambda

Solution

1. Step 1: Configure S3 event trigger

   To run Lambda automatically on uploads, configure S3 to trigger Lambda on 'ObjectCreated' events.

2. Step 2: Assign correct IAM role permissions

   Lambda needs an execution role with permissions to read from S3 to process images.

3. Final Answer:

   Set S3 event trigger on bucket for 'ObjectCreated' and assign Lambda execution role with S3 read permissions -> Option C

4. Quick Check:

   S3 trigger + IAM role = automatic Lambda run [OK]

Hint: Use S3 event triggers with proper IAM role [OK]

Common Mistakes:

• Thinking manual invocation is automatic
• Confusing runtime with event triggers
• Using EC2 unnecessarily for Lambda triggers