Command Palette

Search for a command to run...

Hectal
Phase 6Intermediate7 of 9 in AWS

Messaging & Monitoring

SQS, SNS, and EventBridge to decouple services; CloudWatch, X-Ray, and CloudTrail to see what they're doing and who changed what.

Once a system has more than a couple of services, two things decide whether it survives production: whether components can fail and slow down independently (messaging), and whether you can tell what's happening when they do (monitoring). This phase covers AWS's queue, pub/sub, and event-bus services, then the metrics, logs, alarms, traces, and audit trail you need to operate them.

0/4 · 0%
4 topics ~52 min 11 code blocks & diagrams
Start with the first topic
1
6.1

SQS: Queues, Visibility Timeouts & DLQs

SQS is a fully managed queue that lets a producer hand off work and move on while consumers process it at their own pace; visibility timeouts, dead-letter queues, and idempotent consumers are what make it reliable.

13 min 1 diagram 1 code practice

2
6.2

SNS & EventBridge: Fan-Out and Event Routing

SNS pushes one message to many subscribers at once; EventBridge is an event bus that routes events to targets based on their content — together with SQS they let services react to each other without direct calls.

13 min 1 diagram 2 code practice

3
6.3

CloudWatch: Metrics, Logs & Alarms

CloudWatch collects metrics from every AWS service and your apps, stores and queries logs, and raises alarms — the default observability layer for anything running on AWS.

13 min 3 code practice

4
6.4

X-Ray Tracing & CloudTrail Auditing

Distributed tracing with X-Ray (via OpenTelemetry) shows where time goes across services in a single request; CloudTrail records every API call made in your account, answering 'who changed what, and when?'

13 min 1 diagram 2 code practice