OnCallReadyStart learning

AWS VI: Architecting on AWS & the exams

Designing on AWS the way the Solutions Architect exam and a design review expect: decoupling with SQS, SNS and EventBridge, serverless with Lambda and API Gateway, containers on ECS Fargate, workflows with Step Functions, streaming ingestion with Kinesis and Firehose, caching layers, DR strategies against an RPO and RTO, least privilege and encryption across services, cost-optimized design and purchase options, a Well-Architected review in practice - and the SAA-C03 and SOA-C03 exams themselves.

In plain words

Earlier chapters taught you the individual tools in a workshop: the saw, the drill, the glue. This chapter is about building furniture that does not wobble. Which joints should be loose so the table survives a knock (queues and topics), which parts you rent instead of own (serverless and containers), where to keep a spare leg in another room (disaster recovery), and how to build it without wasting wood (cost). At the end come the two exams that check whether you can make those choices quickly, from a short description, with four plausible answers on the screen.

Why it matters on call

Job interviews and the Solutions Architect exam rarely ask how to type a command; they ask which design meets a requirement and why the others do not. On call, the same judgement decides how bad an incident gets: a queue without a DLQ, a function without a timeout, a service in one Availability Zone. This chapter builds the common AWS application patterns hands-on - decoupling, Lambda behind queues and APIs, ECS on Fargate, Step Functions, Kinesis and Firehose - then reviews them for resilience, security and cost, and closes with the SAA-C03 and SOA-C03 exams.

Lessons

  1. 39.1Decoupling: queues, topics and the event bus
  2. 39.5Lambda: functions, cold starts, the REPORT line and concurrency
  3. 39.6Lambda behind a queue: event source mappings, partial batches and destinations
  4. 39.12API Gateway: putting an API in front of functions
  5. 39.15Containers on AWS: ECR, ECS on Fargate, and when to use what
  6. 39.20Step Functions: workflows with retries, catches and compensation
  7. 39.23Streaming and data ingestion: Kinesis, Firehose and the analytics map
  8. 39.26Caching layers: where to cache and what it costs you
  9. 39.27Designing for resilience: AZs, Regions and DR strategies
  10. 39.29Designing for security: least privilege across services, encryption, segmentation, identity
  11. 39.31Cost-optimized design: purchase options, right-sizing and the shape of the bill
  12. 39.34A Well-Architected review in practice
  13. 39.36Migrating to AWS: the Cloud Adoption Framework, the 7 Rs and the tools
  14. 39.38The SAA-C03 exam: AWS Certified Solutions Architect - Associate
  15. 39.42The SOA-C03 exam: AWS Certified CloudOps Engineer - Associate

30 hands-on labs (missions, incidents and drills) run in the terminal.

Open this chapter in the terminal Free, in your browser - a real Ubuntu terminal to try it in, with missions that check your work.

Questions people ask

Do I need AWS I-V before this chapter?

Yes, mostly. The labs use IAM roles and policies, the CLI with --query, VPCs and security groups, load balancers, CloudWatch alarms and logs, and Cost Explorer from the earlier AWS chapters. Data stores, Route 53, CloudFront and backups belong to AWS V; this chapter references them in design lessons without teaching them again.

Is this chapter only exam preparation?

No. Every lesson runs real commands against the simulated account and every pattern comes with the incident it causes when it is built badly: the queue backlog behind a throttled function, the poison message, the Fargate service that never starts, the API that times out under load. The exam lessons at the end turn that experience into exam technique.

Which parts are simulated and which are only concepts?

SQS, SNS, Lambda (Node.js and a Python subset really run), API Gateway, ECR, ECS on Fargate, Step Functions, Kinesis and Firehose are simulated with real output formats and errors. Glue, Athena, EMR, Lake Formation, Cognito sign-in flows, App Runner and the Well-Architected Tool are concepts, and the lessons say so.

Would these labs cost money on a real account?

A little. Lambda, SQS, SNS and Step Functions stay inside the free tier at lab volumes, but Fargate tasks, load balancers, NAT gateways, interface endpoints and Kinesis shards bill by the hour. On a real account, set a budget first, run the labs in an afternoon, and delete services, load balancers, endpoints and streams afterwards.

Which exam should I take after this chapter?

The Solutions Architect - Associate (SAA-C03) if you are heading towards design or platform roles, the CloudOps Engineer - Associate (SOA-C03) if your job is running production and being on call. They share about a third of their content. The exam lessons explain both formats, the domains and a study plan with the course's mocks and cards.