AWS Lambda Fundamentals

# CHAPTER 3

AWS Lambda Fundamentals #

1. Introduction #

2. Learning Objectives #

• Navigate the AWS Lambda Management Console.

• Configure Lambda Memory and understand its impact on CPU power.

• Configure Timeout settings to prevent runaway billing.

• Understand Synchronous vs. Asynchronous invocation.

• Deploy and test a Node.js Lambda function.

3. Beginner-Friendly Explanation #

• The Code (The Candy): You provide the candy (your Node.js or Python code).

• The Memory (The Motor): You decide how strong the vending machine's motor should be. If your code does heavy math, you give it a big motor (1024 MB). If it just says "Hello," you give it a small motor (128 MB).

• The Timeout (The Safety Switch): You tell the machine: "If the candy gets stuck and the motor runs for more than 10 seconds, cut the power." This prevents the machine from running forever and draining your bank account.

4. Configuration: Memory and CPU #

5. Configuration: Timeouts #

6. Invocation Methods #

1. 1. Synchronous (Push): The user waits for the answer. Example: A user clicks "Login" on a website. The API Gateway triggers Lambda, Lambda checks the database, and returns "Success" directly to the user's browser.

1. 2. Asynchronous (Event): Fire and forget. Example: A user uploads a video. An event triggers Lambda to process the video. The user doesn't wait; Lambda runs in the background and sends an email when it's done.

7. Mini Project: Create Your First Lambda Function #

Step-by-Step Tutorial: *(Assumption: You have logged into the AWS Console).*

1. 1. Search for Lambda and click Create function.

1. 2. Choose Author from scratch.

1. 3. Function name: MyHelloWorldAPI.

1. 4. Runtime: Select Node.js 20.x.

1. 5. Architecture: x86_64 (Standard intel).

1. 6. Click Create function.

1. 7. Scroll down to the Code source editor. You will see this default code:

export const handler = async (event) => {
  const response = {
    statusCode: 200,
    body: JSON.stringify('Hello from Lambda!'),
  };
  return response;
};

1. 8. Change the text to 'Hello from the Cloud!'.

1. 9. Click the Deploy button (crucial step, or your changes aren't saved).

1. 10. Click the blue Test button.

1. 11. Create a new test event (name it TestEvent), leave the JSON as default, and click Save.

1. 12. Click Test again.

1. 13. A green box will appear. Expand the Execution result. You will see your output: Hello from the Cloud! You have successfully executed serverless compute!

8. Real-World Scenarios #

9. Best Practices #

• Variables Outside the Handler: If your function needs to connect to a database, initialize the connection *outside* the handler function. Code outside the handler runs during the Cold Start. When the container stays warm, the database connection is preserved, making subsequent invocations significantly faster.

const db = new DatabaseConnection(); // Runs once per Cold Start

export const handler = async (event) => {
    // Runs on every single request. Reuses the 'db' connection above!
};

10. Cost Optimization Tips #

• The AWS Free Tier: AWS offers a permanent, non-expiring free tier for Lambda: 1 Million free requests per month and 400,000 GB-seconds of compute time per month. For most learning and personal projects, you will never pay a dime for Lambda.

11. Exercises #

1. 1. If an AWS Lambda function is executing a CPU-intensive mathematical calculation very slowly, how can you increase its CPU power without rewriting the code?

1. 2. Explain the purpose of the Timeout setting. Why is setting it to the 15-minute maximum a dangerous practice for simple API calls?

12. FAQs #

13. Interview Questions #

• Q: Explain the relationship between Memory allocation and CPU provisioning within AWS Lambda. How does this relationship impact cost optimization strategies?

• Q: Differentiate between Synchronous and Asynchronous Lambda invocations. Provide an architectural use case for each.

14. Summary #

15. Next Chapter Recommendation #