What a Solutions Architect Does
Module 1 · The Role and the Exam

What a Solutions Architect Does

The Solutions Architect role on AWS: working backwards from the business, turning requirements into design choices, weighing trade-offs, and writing decisions down.

The Job in One Sentence

A Solutions Architect (SA) decides how a system should be built so that it meets the business’s needs, and explains why. SAs rarely write most of the code. They decide which services to use, how the pieces connect, how the system fails and recovers, and what it will cost to run.

The title shows up in three common places:

WhereWho the SA works forTypical work
AWS itselfAWS customers, as part of the account teamDesign reviews, proofs of concept, workshops, migration plans, Well-Architected reviews
AWS partners and consultanciesClients on a projectDesign and often build a workload, then hand it over
In-houseTheir own companySet standards, review designs from product teams, own the cloud architecture

The skills are the same in all three. You listen for requirements, translate them into an architecture, and defend the trade-offs.


Working Backwards

Amazon’s habit of working backwards applies directly here. Start from what the customer needs, not from the service you’d like to use.

  1. 1 Discover

    Business goal, users, workloads

  2. 2 Constrain

    Availability, RPO/RTO, compliance, budget

  3. 3 Options

    Two or three designs, not one

  4. 4 Decide

    Pick one; write down why

  5. 5 Validate

    Proof of concept, load test, review

  6. 6 Hand off

    Docs, runbooks, owners

Validation results and production metrics send you back to the requirements step.

Functional vs non-functional requirements

Functional requirements say what the system does: “users can upload a photo and share a link.” Non-functional requirements say how well it must do it, and they drive almost every architecture decision:

  • Availability: how much downtime is acceptable (99.9% allows about 8.8 hours a year; 99.99% allows about 53 minutes)
  • Recovery: RTO (how long you can be down) and RPO (how much data you can lose)
  • Performance: latency targets, peak requests per second, data volume
  • Security and compliance: data residency, encryption, audit requirements, who may access what
  • Cost: a monthly budget, or a target cost per transaction
  • Operations: the team’s skills, and how much infrastructure they’re willing to manage

Each requirement pushes the design in a specific direction:

RequirementDesign consequence99.9% availabilityMulti-AZ behind a load balancerRPO of 5 minutesContinuous backups or replicationCustomer data must stay in the EUEU Region; SCP denies other RegionsTraffic spikes 20× at launchAuto Scaling, queues, cachingSmall team, no ops staffManaged and serverless services

Everything Is a Trade-Off

There is almost never a single right architecture. There is the one that best fits these requirements. Common tensions:

  • Availability vs cost. Multi-Region active/active is very resilient and very expensive.
  • Managed vs control. Aurora removes database operations work; self-managed databases on EC2 give you every knob.
  • Consistency vs latency. Global users want local reads; strongly consistent writes need coordination.
  • Speed of delivery vs long-term fit. A quick lift-and-shift ships this quarter; a rearchitecture pays off later.

Where a service sits on this spectrum decides how much work your team takes on. It’s the main thing behind the exam’s “least operational overhead” questions:

Amazon EC2ECS on FargateAWS LambdaYour codeYou manageYou manageYou manageRuntime or containerYou manageYou manageAWS managesOS and patchingYou manageAWS managesAWS managesScaling and capacityYou manageYou manageAWS managesHardwareAWS managesAWS managesAWS managesMore controlLess operational overhead

The AWS Well-Architected Framework gives you a checklist for these conversations. It has six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. The SAA-C03 exam focuses on four of them: security, reliability (resilience), performance, and cost.

Write the decision down

Good SAs record important choices in an architecture decision record (ADR): a short note with the context, the options considered, the decision, and its consequences. Six months later, when someone asks “why didn’t we use DynamoDB?”, the answer is on the page.

⚠️ Common Pitfall: Starting From the Service

Common mistake: an architect opens with “let’s use Kubernetes and DynamoDB” before asking how many users there are, what the data looks like, or who will run it.

Service-first designs fit the architect’s favorite tools, not the problem. Ask about requirements and constraints first. If you can’t say which requirement a component satisfies, you probably don’t need it.


What This Course Covers

ModuleTopicSAA-C03 domain
1The role and the exam—
2Secure architecturesDomain 1 (30%)
3Resilient architecturesDomain 2 (26%)
4High-performing architecturesDomain 3 (24%)
5Cost-optimized architecturesDomain 4 (20%)
6Case study and study planAll four

You’ll get the most out of it with an AWS account to experiment in. Use the Free Tier, set a budget alert on day one, and delete what you build when you’re done.


Key Takeaway

A Solutions Architect turns requirements into design choices and can explain each one. Start from the business, pin down the non-functional requirements (availability, RPO/RTO, compliance, performance, cost, operations), compare options, and write down why you chose one.

🧪 Try It: Requirements Interview

A friend runs an online bakery. Today it’s a single WordPress server on one EC2 instance. They want to “move it to the cloud properly.”

Write eight questions you’d ask before drawing anything. Cover availability, data loss, traffic patterns, compliance (they take card payments), budget, and who will maintain it.

Then, for two of your questions, write how two different answers would change the design. For example: “If they can tolerate a day of downtime, a single instance with nightly backups is fine. If an outage during the holiday rush costs them $10,000 an hour, they need Multi-AZ.”

🧠 Knowledge Check

1. Which of these is a non-functional requirement?

2. A business says it can lose at most 15 minutes of data. Which value is that?

3. What does 'working backwards' mean for an architect?

4. What is the purpose of an architecture decision record (ADR)?