Trigger e integrazioni di Lambda
Colleghi le funzioni Lambda a vari servizi AWS, come S3, DynamoDB e API Gateway, per creare workflow potenti e guidati dagli eventi.
Trigger e integrazioni di Lambda è una lezione AWS for Backend Developers (EC2, S3, RDS, Lambda) gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento AWS for Backend Developers (EC2, S3, RDS, Lambda), e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso AWS for Backend Developers (EC2, S3, RDS, Lambda) include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Events Bring Lambda to Life
Welcome to the heart of serverless architecture: Lambda Triggers! These are the events that tell your Lambda function when to run. Instead of constantly running a server, your function springs into action only when needed.
Think of it like a doorbell for your code. Someone presses the button (an event occurs), and your function responds.
How Triggers Work: Push vs. Pull
Lambda triggers come in two main flavors:
- Push-based: The event source (like S3 or SNS) directly invokes your Lambda function when an event happens. Lambda receives the event and runs your code.
- Pull-based: Lambda itself polls an event source (like SQS queues or DynamoDB Streams) for new items. When new data is found, Lambda retrieves it and invokes your function.
Understanding this helps you design efficient event-driven workflows.
S3 Event Triggers: React to Storage
One of the most common and powerful triggers is Amazon S3. You can configure an S3 bucket to automatically invoke a Lambda function whenever specific events occur, such as:
- New object created (e.g., an image upload)
- Object deleted
- Object restored
This is perfect for tasks like image resizing, data validation, or generating thumbnails as soon as a file is uploaded.
S3 Trigger Demo: Logging Uploads
Here's a basic Python Lambda function that would be triggered by an S3 object creation event. It simply logs the bucket and object key from the event data.
Try running the simulated event:
import json
def lambda_handler(event, context):
"""
Simulated Lambda handler for S3 events.
Logs the details of the S3 event.
"""
print("--- S3 Event Received ---")
for record in event.get('Records', []):
bucket_name = record['s3']['bucket']['name']
object_key = record['s3']['object']['key']
event_name = record['eventName']
print(f"Bucket: {bucket_name}")
print(f"Object: {object_key}")
print(f"Event: {event_name}")
print("-------------------------")
return {
'statusCode': 200,
'body': json.dumps('S3 event logged!')
}
if __name__ == "__main__":
# Simulate an S3 PUT event
mock_event = {
"Records": [
{
"eventSource": "aws:s3",
"eventName": "ObjectCreated:Put",
"s3": {
"bucket": {"name": "my-cool-bucket"},
"object": {"key": "my-new-file.txt"}
}
}
]
}
lambda_handler(mock_event, None)DynamoDB Streams: Database Changes
Amazon DynamoDB Streams provide a time-ordered sequence of item-level modifications in a DynamoDB table. When you enable a stream, every create, update, or delete operation is captured.
Lambda can be configured to read from these streams, allowing you to react to database changes in real-time. Use cases include:
- Data replication across tables
- Auditing changes
- Triggering downstream workflows
DynamoDB Stream Demo: Processing Updates
This Python Lambda function simulates processing events from a DynamoDB Stream. It logs the event type (INSERT, MODIFY, REMOVE) and the keys/new image of the affected item.
Run it to see how a database change event looks:
import json
def lambda_handler(event, context):
"""
Simulated Lambda handler for DynamoDB Stream events.
Logs the details of the changed records.
"""
print("--- DynamoDB Stream Event Received ---")
for record in event.get('Records', []):
event_name = record['eventName']
keys = record['dynamodb']['Keys']
new_image = record['dynamodb'].get('NewImage', {})
print(f"Event: {event_name}")
print(f"Keys: {json.dumps(keys)}")
print(f"New Image: {json.dumps(new_image)}")
print("------------------------------------")
return {
'statusCode': 200,
'body': json.dumps('DynamoDB stream processed!')
}
if __name__ == "__main__":
# Simulate a DynamoDB INSERT event
mock_event = {
"Records": [
{
"eventID": "1",
"eventName": "INSERT",
"dynamodb": {
"Keys": {"id": {"S": "123"}},
"NewImage": {"id": {"S": "123"}, "name": {"S": "Alice"}},
"StreamViewType": "NEW_AND_OLD_IMAGES"
}
}
]
}
lambda_handler(mock_event, None)API Gateway: Serverless API Endpoints
Amazon API Gateway acts as a 'front door' for applications to access backend services, including Lambda functions. It handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls.
By integrating API Gateway with Lambda, you can build powerful, scalable, and secure RESTful APIs without managing any servers. Users make an HTTP request, API Gateway routes it to your Lambda, and your Lambda returns a response.
API Gateway Demo: Your Serverless API
This Lambda function shows how to respond to an API Gateway request. It receives event data about the HTTP request and returns a JSON response, which API Gateway then sends back to the client.
Run the simulation to see the expected output:
import json
def lambda_handler(event, context):
"""
Simulated Lambda handler for API Gateway events.
Returns a simple JSON response.
"""
print("--- API Gateway Event Received ---")
print(f"HTTP Method: {event.get('httpMethod')}")
print(f"Path: {event.get('path')}")
print("----------------------------------")
response_body = {
"message": "Hello from your serverless API!",
"input": event
}
return {
'statusCode': 200,
'headers': {
'Content-Type': 'application/json'
},
'body': json.dumps(response_body)
}
if __name__ == "__main__":
# Simulate an API Gateway GET request event
mock_event = {
"resource": "/",
"path": "/",
"httpMethod": "GET",
"headers": {
"Accept": "text/html"
},
"queryStringParameters": None,
"pathParameters": None,
"body": None,
"isBase64Encoded": False
}
response = lambda_handler(mock_event, None)
print("\n--- API Response ---")
print(json.dumps(response, indent=2))More Powerful Integrations
Lambda can integrate with many other AWS services to build incredibly flexible architectures:
- Amazon SQS: Process messages from a queue for asynchronous tasks.
- Amazon SNS: Respond to notifications (e.g., sending emails or SMS).
- CloudWatch Events/EventBridge: Trigger Lambda functions on a schedule, or in response to AWS service events (e.g., an EC2 instance state change).
- Kinesis: Process real-time streaming data.
These integrations form the backbone of modern, event-driven applications.
Quick Check
Test your knowledge of Lambda triggers!
Recap: The Heart of Serverless Workflows
You've learned that Lambda functions are powerful, but they need triggers to come to life! These triggers are events from other AWS services that automatically invoke your function.
We explored how S3, DynamoDB Streams, and API Gateway can act as direct event sources, enabling you to build responsive, event-driven applications without managing servers. Understanding triggers is key to unlocking the full potential of serverless architecture!
Domande Frequenti
La lezione «Trigger e integrazioni di Lambda» è gratuita?
Sì — il testo completo di «Trigger e integrazioni di Lambda» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso AWS for Backend Developers (EC2, S3, RDS, Lambda), passa a CoddyKit PRO. Il corso AWS for Backend Developers (EC2, S3, RDS, Lambda) include 4 lezioni in totale.
Cosa imparerò in «Trigger e integrazioni di Lambda»?
Colleghi le funzioni Lambda a vari servizi AWS, come S3, DynamoDB e API Gateway, per creare workflow potenti e guidati dagli eventi. Eserciti AWS for Backend Developers (EC2, S3, RDS, Lambda) con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare AWS for Backend Developers (EC2, S3, RDS, Lambda)?
Non è richiesta alcuna esperienza precedente. AWS for Backend Developers (EC2, S3, RDS, Lambda) su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Trigger e integrazioni di Lambda»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione AWS for Backend Developers (EC2, S3, RDS, Lambda)?
Sì. Ogni lezione AWS for Backend Developers (EC2, S3, RDS, Lambda) include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Che cos'è AWS Lambda?
- Creazione della prima funzione Lambda
- Trigger e integrazioni di Lambda
- Monitoraggio e debugging delle funzioni Lambda