In Day 07, I start with the most important clarification: “serverless” doesn’t mean servers don’t exist. Servers are still running behind the scenes, but you are not managing them—no OS patching, no scaling setup, no worrying about instances going down. I explain it with a simple analogy: renting a house vs staying in a hotel. With serverless, you focus on code + triggers, and in AWS Lambda you generally pay per request and execution time, and you don’t pay when your code is not running. Then I take you hands-on inside the AWS Console and create our first AWS Lambda function using a blueprint (Hello World). I show you how the execution role gets created, how to test the function using test events, and how to expose it using a Lambda Function URL. When we hit it from Postman, I also explain why returning a “proper HTTP-style response” (statusCode, headers, body) matters. Finally, I introduce Amazon API Gateway and why it’s the production-grade approach compared to a Function URL—better auth options, rate limiting, custom domains, and request/response mapping. We build a REST API, create a /contact resource, deploy a dev stage, and connect it to Lambda. I also show how AWS Toolkit in VS Code helps you edit and deploy Lambda faster without constantly switching back to the console.