Ihre erste Lambda-Funktion erstellen
Schreiben und deployen Sie eine einfache Lambda-Funktion und konfigurieren Sie deren Laufzeit, Speicher und Ausführungsrolle.
Ihre erste Lambda-Funktion erstellen ist eine kostenlose AWS for Backend Developers (EC2, S3, RDS, Lambda)-Lektion auf CoddyKit. Dies ist Lektion 2 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des AWS for Backend Developers (EC2, S3, RDS, Lambda)-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der AWS for Backend Developers (EC2, S3, RDS, Lambda)-Kurs umfasst insgesamt 4 Lektionen.
Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.
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 responseWhat 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
eventobject carries input data, andcontextprovides 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!
Häufig gestellte Fragen
Ist die Lektion „Ihre erste Lambda-Funktion erstellen“ kostenlos?
Ja — der vollständige Text von „Ihre erste Lambda-Funktion erstellen“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des AWS for Backend Developers (EC2, S3, RDS, Lambda)-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der AWS for Backend Developers (EC2, S3, RDS, Lambda)-Kurs umfasst insgesamt 4 Lektionen.
Was lerne ich in „Ihre erste Lambda-Funktion erstellen“?
Schreiben und deployen Sie eine einfache Lambda-Funktion und konfigurieren Sie deren Laufzeit, Speicher und Ausführungsrolle. Du übst AWS for Backend Developers (EC2, S3, RDS, Lambda) mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.
Brauche ich Erfahrung, um AWS for Backend Developers (EC2, S3, RDS, Lambda) zu starten?
Keine Vorkenntnisse erforderlich. AWS for Backend Developers (EC2, S3, RDS, Lambda) auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 2 von 4.
Wie lange dauert die Lektion „Ihre erste Lambda-Funktion erstellen“?
Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.
Kann ich in dieser AWS for Backend Developers (EC2, S3, RDS, Lambda)-Lektion Code schreiben und ausführen?
Ja. Jede AWS for Backend Developers (EC2, S3, RDS, Lambda)-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.
Alle Lektionen in diesem Kurs
- Was ist AWS Lambda?
- Ihre erste Lambda-Funktion erstellen
- Lambda-Trigger und Integrationen
- Lambda-Funktionen überwachen und debuggen