Lambda runs code in response to invocations. Choose the invocation path first, then configure retries, permissions, runtime resources, and release routing for that path.
Lambda basics
AWS Lambda runs your code when an event happens, with no servers for you to manage.
How it works
- Write a function and choose a trigger.
- When the event happens, Lambda runs the function.
- Lambda scales the number of runs with the events.
Exam cues
- If the question says run code on an event without managing servers, think Lambda.
Remember
- Serverless: no servers to provision or patch.
Trap: Lambda is serverless compute for event-driven code; long-running servers you control are EC2.
Da documentação da AWS (4)
- AWS Lambda runs code without provisioning or managing servers; AWS handles capacity, scaling and patching.
- A Lambda function runs in response to events or API calls from triggers such as API Gateway, Amazon S3, Amazon SQS and EventBridge.
- AWS Lambda runs code without servers to provision or manage; AWS handles server maintenance, capacity provisioning and scaling, and you pay only for the resources used.
- Other AWS services, such as Amazon S3 and Amazon DynamoDB, can invoke Lambda functions with events.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 4 flashcards em lista
A small piece of code must run each time a file lands in an S3 bucket, with no servers to manage. Which service fits?
AWS Lambda, triggered by the S3 event.
Who patches and scales the servers that run AWS Lambda functions?
AWS. Lambda is serverless; you supply only the code.
A company wants to run code in response to new uploads to an Amazon S3 bucket, with no servers to manage. Which service fits?
AWS Lambda, triggered by S3 events.
AWS manages the servers, capacity and scaling.
Who patches and scales the servers that run AWS Lambda functions?
AWS. Lambda is serverless; you manage only your code.