Amazon SNS and SQS: notifications and message queues

When an order is paid, Baobab Market's shop notifies preparation, sends the customer a confirmation, then calls accounting, one after the other. The day accounting crashed for ten minutes, not a single payment went through. Awa asks you to decouple all of this: the shop announces only once that an order is paid, and each team receives it at its own pace. This sixth lab of the preparation path for the AWS Certified Cloud Practitioner certification starts with what the exam asks about decoupling: synchronous or asynchronous, SNS that pushes or SQS that keeps, EventBridge, and the fan-out pattern to several queues, on an architecture diagram. You create an SNS topic, after a first denial triggered on purpose, then subscribe your email address to it, and not someone else's, as a second denial shows. You create two SQS queues, connect them to the topic, and publish an order only once: it lands in your inbox and in both queues. You read the received message and its SNS envelope, discover the visibility timeout, filter what accounting receives, and set aside failing messages in a dead-letter queue. Everything happens in the real AWS console. The guide is illustrated with screenshots of the console and a diagram, explains standard and FIFO queues, and ends with a ten-question practice exam.