AWS for Backend Developers (EC2, S3, RDS, Lambda) · 课时

构建您的第一个 Lambda 函数

编写并部署一个简单的 Lambda 函数，配置其运行时、内存和执行角色。

构建您的第一个 Lambda 函数 是 CoddyKit 上的免费 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 AWS for Backend Developers (EC2, S3, RDS, Lambda) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Your First Lambda Function

Time to build your first serverless function! In this lesson, we'll write a simple AWS Lambda function that runs your code without managing servers.

We'll cover its basic structure, how to choose a runtime, and essential configurations like memory and execution roles. Get ready to deploy!

The Core: Your Lambda Handler

Every Lambda function needs a 'handler' function. This is the entry point where AWS Lambda starts executing your code. It typically receives two arguments:

event: Contains the data that triggered the invocation.
context: Provides runtime information about the invocation, function, and execution environment.

Think of the handler as the 'main' method for your serverless code.

Pick Your Language: Lambda Runtimes

AWS Lambda supports many programming languages, called 'runtimes.' You choose the one your function code is written in. The runtime determines the execution environment and how your handler is called.

Python: Great for scripting, data processing, and machine learning.
Node.js: Ideal for real-time applications, APIs, and microservices.
Java: Good for enterprise applications, high performance, and existing JVM ecosystems.
Go, C#, Ruby, Custom Runtimes: More options for diverse needs and specific use cases.

Hello Lambda: A Basic Python Example

Let's write a very simple Python Lambda function. This function will take an input name from the event and return a greeting. Try running it to see the output!

import json

def lambda_handler(event, context):
    # event is a dictionary containing invocation data
    # context provides runtime info (e.g., function name, memory limit)

    # We expect 'name' in the event payload
    name = event.get('name', 'World')
    message = f"Hello, {name}!"

    # Lambda functions often return a dictionary, which AWS converts to JSON
    return {
        'statusCode': 200,
        'body': json.dumps(message)
    }

# --- Local Test Simulation ---
if __name__ == "__main__":
    # Simulate an event payload
    test_event = {"name": "CoddyKit User"}
    
    # Simulate a dummy context object
    class Context:
        def __init__(self):
            self.function_name = "my-test-function"
            self.memory_limit_in_mb = 128
            self.invoked_function_arn = "arn:aws:lambda:us-east-1:123456789012:function:my-test-function"
            self.aws_request_id = "test-request-id-123"

    test_context = Context()

    # Call the handler
    response = lambda_handler(test_event, test_context)
    
    # Print the response for local verification
    print(f"Status Code: {response['statusCode']}")
    print(f"Body: {json.loads(response['body'])}")

    # Test without a name
    test_event_no_name = {}
    response_no_name = lambda_handler(test_event_no_name, test_context)
    print(f"\nStatus Code (no name): {response_no_name['statusCode']}")
    print(f"Body (no name): {json.loads(response_no_name['body'])}")

Your Function's Input: The Event

The event object is a Python dictionary (or JSON object in other runtimes) that contains the data passed to your function. This data comes from the service that triggered your Lambda.

If triggered by an API Gateway: It contains HTTP method, headers, body.
If triggered by S3: It contains details about the S3 bucket and object.
If invoked directly: It contains whatever JSON payload you passed.

Your function processes this input to perform its task.

Runtime Details: The Context

The context object provides information about the invocation, function, and execution environment. It's useful for logging and making runtime decisions.

function_name: The name of your Lambda function.
aws_request_id: A unique ID for the invocation.
memory_limit_in_mb: The memory allocated to the function.
get_remaining_time_in_millis(): How much time is left before the function times out.

You can use this for advanced error handling or logging within your function.

Permissions with IAM Execution Roles

A Lambda function needs permission to interact with other AWS services. This is managed by an IAM Role, specifically called the "execution role."

The role defines what actions your Lambda can perform (e.g., write logs to CloudWatch, read from S3).
You attach policies to this role, specifying permissions.
Without the correct permissions, your function will fail when trying to access other AWS resources.

Always follow the principle of least privilege, granting only the necessary permissions.

Fine-Tuning: Memory & Timeout

When you create a Lambda function, you configure several settings that impact its performance and cost:

Memory: Defines the RAM allocated (e.g., 128MB to 10GB). More memory often means more CPU power too.
Timeout: The maximum time your function can run (e.g., 3 seconds to 15 minutes). If it exceeds this, Lambda stops it.
Environment Variables: Key-value pairs accessible to your code, great for configuration without changing code.

Choosing appropriate settings is crucial for efficiency and cost optimization.

Getting Your Function Live

Once your code is ready, you deploy it to AWS Lambda. Here's a high-level overview:

Package your code: Zip your code and any dependencies into a deployment package.
Upload: Use the AWS Console, AWS CLI, or an Infrastructure as Code (IaC) tool like AWS SAM or CloudFormation.
Test: Invoke your function directly from the Lambda console with test events, or trigger it via an integrated service like API Gateway or S3.

The console provides a quick way to get started and test your function immediately.

Quick Check: Lambda Handler

Consider the basic structure of a Python Lambda handler:

def lambda_handler(event, context):
    # ... your code ...
    return response

What is the primary purpose of the event parameter?

Recap: Your First Serverless Step

Great job! You've learned the fundamentals of building a Lambda function:

Every Lambda needs a handler function as its entry point.
You choose a runtime (like Python) for your code.
The event object carries input data, and context provides runtime info.
An IAM execution role grants your function necessary permissions.
You configure settings like memory and timeout for performance and cost.

This is your foundation for building powerful serverless applications!

常见问题解答

「构建您的第一个 Lambda 函数」课时是免费的吗？

是的 — 「构建您的第一个 Lambda 函数」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程的其余内容，请升级到 CoddyKit PRO。 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程共包含 4 节课。

「构建您的第一个 Lambda 函数」这节课中我会学到什么？

编写并部署一个简单的 Lambda 函数，配置其运行时、内存和执行角色。你通过在浏览器中直接运行的动手代码来练习 AWS for Backend Developers (EC2, S3, RDS, Lambda)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 AWS for Backend Developers (EC2, S3, RDS, Lambda) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「构建您的第一个 Lambda 函数」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课中编写并运行代码吗？

能。每节 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 AWS for Backend Developers (EC2, S3, RDS, Lambda)