Lambda integration in AWS - Time & Space Complexity

Time Complexity: Lambda integration

O(n)

Understanding Time Complexity

When we connect AWS Lambda to other services, it's important to know how the time to complete tasks grows as we add more work.

We want to understand how the number of Lambda calls changes when the input size changes.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

# For each item in a list, invoke a Lambda function
for item in items:
    lambda.invoke(
        FunctionName='ProcessItem',
        Payload=json.dumps(item)
    )

This code calls a Lambda function once for each item in a list to process them individually.

Identify Repeating Operations

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

• Primary operation: Lambda function invocation API call
• How many times: Once per item in the input list

How Execution Grows With Input

Each new item causes one more Lambda call, so the total calls grow directly with the number of items.

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 increases evenly as the input size increases.

Final Time Complexity

Time Complexity: O(n)

This means the total Lambda calls grow in direct proportion to the number of items to process.

Common Mistake

[X] Wrong: "Calling Lambda once with all items is the same as calling it once per item."

[OK] Correct: Calling Lambda once per item means many separate calls, so time grows with items. One call with all items is just one call, so time does not grow the same way.

Interview Connect

Understanding how Lambda calls scale helps you design systems that handle growing workloads smoothly and shows you can think about costs and performance clearly.

Self-Check

"What if we batch multiple items into a single Lambda call? How would the time complexity change?"

Practice

1. What is the main purpose of Lambda integration in AWS API Gateway?

easy

A. To create virtual machines in the cloud

B. To store data permanently in AWS

C. To connect API Gateway to Lambda functions so they run code on requests

D. To monitor network traffic between AWS services

Solution

1. Step 1: Understand Lambda integration role

   Lambda integration allows API Gateway to trigger Lambda functions when an API request is made.

2. Step 2: Compare options with this role

   Only To connect API Gateway to Lambda functions so they run code on requests describes connecting API Gateway to Lambda to run code on requests.

3. Final Answer:

   To connect API Gateway to Lambda functions so they run code on requests -> Option C

4. Quick Check:

   Lambda integration = connect API Gateway to Lambda [OK]

Hint: Lambda integration runs code on API requests [OK]

Common Mistakes:

• Confusing Lambda integration with data storage
• Thinking it creates virtual machines
• Mixing it with monitoring services

2. Which of the following is the correct way to specify Lambda integration in an API Gateway method using AWS CLI?

easy

A. --integration-type HTTP --integration-uri http://example.com

B. --integration-type AWS_PROXY --integration-uri arn:aws:lambda:region:account-id:function:function-name

C. --integration-type MOCK --integration-uri arn:aws:s3:::bucket/key

D. --integration-type AWS --integration-uri arn:aws:ec2:region:account-id:instance/instance-id

Solution

1. Step 1: Identify Lambda integration syntax

   Lambda integration uses type AWS_PROXY and the Lambda function ARN as URI.

2. Step 2: Match options with correct syntax

   --integration-type AWS_PROXY --integration-uri arn:aws:lambda:region:account-id:function:function-name correctly uses AWS_PROXY and Lambda ARN format.

3. Final Answer:

   --integration-type AWS_PROXY --integration-uri arn:aws:lambda:region:account-id:function:function-name -> Option B

4. Quick Check:

   AWS_PROXY + Lambda ARN = correct syntax [OK]

Hint: AWS_PROXY + Lambda ARN = Lambda integration syntax [OK]

Common Mistakes:

• Using HTTP or MOCK integration types for Lambda
• Incorrect ARN format for Lambda function
• Confusing AWS integration with EC2 ARN

3. Given this AWS SAM template snippet, what will happen when the API Gateway endpoint is called?

{
  "Resources": {
    "MyFunction": {
      "Type": "AWS::Serverless::Function",
      "Properties": {
        "Handler": "index.handler",
        "Runtime": "nodejs18.x",
        "Events": {
          "ApiEvent": {
            "Type": "Api",
            "Properties": {
              "Path": "/hello",
              "Method": "get"
            }
          }
        }
      }
    }
  }
}

medium

A. API Gateway triggers the Lambda function on GET /hello requests

B. API Gateway returns a static response without calling Lambda

C. Lambda function is triggered only on POST requests

D. The template will fail to deploy due to missing integration

Solution

1. Step 1: Analyze the SAM template event

   The event defines an API trigger on path /hello with GET method linked to the Lambda function.

2. Step 2: Understand behavior on API call

   Calling GET /hello triggers the Lambda function as defined.

3. Final Answer:

   API Gateway triggers the Lambda function on GET /hello requests -> Option A

4. Quick Check:

   API event with GET triggers Lambda [OK]

Hint: API event with GET method triggers Lambda [OK]

Common Mistakes:

• Assuming static response without Lambda call
• Confusing HTTP methods for trigger
• Thinking deployment fails without explicit integration

4. You set up API Gateway with Lambda integration but get a 403 Forbidden error when calling the API. What is the most likely cause?

medium

A. API Gateway lacks permission to invoke the Lambda function

B. The API Gateway endpoint URL is incorrect

C. The Lambda function code has syntax errors

D. The Lambda function timeout is too short

Solution

1. Step 1: Understand 403 Forbidden meaning

   403 means access denied, often due to missing permissions.

2. Step 2: Check Lambda invoke permissions

   API Gateway must have permission to invoke Lambda; missing this causes 403 errors.

3. Final Answer:

   API Gateway lacks permission to invoke the Lambda function -> Option A

4. Quick Check:

   403 Forbidden = missing invoke permission [OK]

Hint: 403 Forbidden means missing invoke permission [OK]

Common Mistakes:

• Blaming Lambda code errors for 403
• Assuming wrong URL causes 403
• Thinking timeout causes 403 instead of 504

5. You want API Gateway to forward the full client request (headers, query, body) to your Lambda function and receive the Lambda response directly. Which integration type and setup should you use?

hard

A. Use AWS integration type with manual mapping templates

B. Use MOCK integration type and configure static responses

C. Use HTTP integration type pointing to Lambda's REST endpoint

D. Use AWS_PROXY integration type with Lambda and grant invoke permissions

Solution

1. Step 1: Identify integration type for full request forwarding

   AWS_PROXY integration forwards the entire client request to Lambda and returns Lambda's response directly.

2. Step 2: Confirm permissions and setup

   Granting API Gateway permission to invoke Lambda is required for this integration to work.

3. Final Answer:

   Use AWS_PROXY integration type with Lambda and grant invoke permissions -> Option D

4. Quick Check:

   AWS_PROXY + invoke permission = full request forwarding [OK]

Hint: AWS_PROXY forwards full request and response [OK]

Common Mistakes:

• Using MOCK for dynamic Lambda calls
• Using HTTP integration which doesn't call Lambda directly
• Using AWS integration without proxy causing manual mapping