AWS Lambda: process events without servers

Baobab Market's paid orders arrive in an SQS queue, but nobody processes them automatically. Rent a server that runs day and night for a few minutes of work a day? Awa does not want that. She asks you to write the program, and only that: for each order, it runs, records it in DynamoDB with the status "being prepared", then stops. This seventh lab of the preparation path for the AWS Certified Cloud Practitioner certification starts with what the exam asks about serverless computing: EC2, containers or Lambda, the 15-minute limit, billing per request and per millisecond, and the shared responsibility, on an architecture diagram. You create a Lambda function, after a denial triggered on purpose, with the provided execution role. You write and test its code in the console, read its logs in CloudWatch, then make it write to a DynamoDB table: a second denial makes you add the only permission it lacks, with least privilege. You connect the SQS queue to the function, after a third denial, and your orders get prepared on their own. You see what becomes of a message that makes the function fail, set the memory and the timeout, and work out what the function costs. Everything happens in the real AWS console. The code is provided and explained line by line: no programming knowledge is needed. The guide is illustrated with screenshots of the console and a diagram, and ends with a ten-question practice exam.