Exam Prep
Amazon Web Services · SAA-03

AWS Certified Solutions Architect - Associate

Validates the skills to design secure, resilient, high-performing, and cost-optimized architectures on AWS — covers access security, data protection, scalable and fault-tolerant design, storage and compute solutions, database selection, and network architecture.

Start Preparing

Free study references: Pages from Amazon Web Services for every objective

Should I Take the SAA-03?

You should work towards SAA-03 if you’re aiming for one of these careers:

  • Solutions architect — designing AWS workloads end to end — compute, storage, networking and database choices that meet security, performance and cost requirements.
  • Cloud engineer — building and maintaining the infrastructure that a solutions architect designs, often the next step for someone who already administers AWS resources.
  • Systems or infrastructure architect — translating an organization's on-premises systems and requirements into an AWS-based design.
  • Cloud consultant — advising clients on migrating workloads to AWS and recommending architectures across multiple customer environments.

SAA-C03 is also a foundation for AWS's professional-level Solutions Architect certification (SAP-C02), which goes deeper into the same design domains for candidates who already have hands-on AWS architecture experience.

Is the SAA-03 Worthwhile?

Here’s what we’d tell a friend:

  • It is the AWS certification employers ask for by name most often. AWS Solutions Architect Associate is the most in-demand certification with 45,000+ job postings." One tracker also found "Solutions Architect Associate has the most job postings by far (45,000+)." Source: Most In-Demand AWS Certifications 2026: Which Do Employers Want?
  • Pay figures vary widely by source, job title and employer type — treat any single number with caution. Surveys and job boards checked in 2026 quote very different figures for the same credential. ZipRecruiter's state-level data put the average at "$148,512 a year" in California as of March 2026, while its nationwide figure for the same month was lower, at "$145,963 a year" as of July 2026. Payscale's survey respondents averaged "$132k" based on 1,585 survey responses, and a Skillsoft-based industry guide reported "AWS Certified Solutions Architect – Associate holders average $99,410" worldwide. These differences reflect location, employer type (AWS partner versus the company that owns the workloads), and years of experience — not a single 'correct' salary. The certification alone will not set your pay; your role, employer and experience will. Source: Salary: Aws Certified Solutions Architect Associate in California, Aws Certified Solutions Architect Associate Salary: Hourly Rate, AWS (Amazon Web Services) Certified Solutions Architect - Associate Salary, AWS Solutions Architect Salary Guide 2026 - KORE1
  • Only a minority of solutions-architect postings actually require an AWS certification. A review of over a thousand solutions-architect-titled job postings found that "64 of 1,079 solutions architect postings name an AWS certification, and 14 of 1,079 say any certification is required." The credential helps a resume stand out, but most employers weigh it alongside experience rather than as a hard requirement. Source: Remote Solutions Architect Jobs: Pay by Seat Type (2026)
  • The role it names remains central to how AWS organizes its own workforce and hiring. Even AWS's own hiring reflects the title: one analysis counted "AWS's own 269 solutions architect postings separately" from comparable roles at other companies, underlining how specific and widely used the job title is across the industry. Source: Remote Solutions Architect Jobs: Pay by Seat Type (2026)

How Long Will I Have to Spend Studying for the SAA-03?

The honest answer is that it depends on how much you already know. AWS's own description of the candidate says the target candidate should have at least 1 year of hands-on experience designing cloud solutions that use AWS services. If that’s your background, you’ve got a good start.

In our plan, you pick the areas of SAA-03 that matter to you — for the exam and for your job — and build a study plan from our domain reviews. Then you take an initial exam, backed by Amazon Web Services’s own documentation, to see where you need to focus to meet your study plan’s goals (our exam review will show you that).

In our store, you can buy a single exam or, if you intend to stick with us, our standard package — which includes, for example, custom drills for the areas our review showed that you need to strengthen (both domain knowledge and exam-taking skills). Repeat with fresh exams, step up to a challenge exam, take advantage of Mentor, and walk into the real exam with your own two-page cheat sheet. See how it works.

How Hard Is the SAA-03 Exam?

Another honest answer: since Amazon Web Services doesn’t publish pass rates, no one knows (including us). What Amazon Web Services does publish: you need a score of 720 or greater to pass. That's a scaled score out of a 100-1,000 range, not a percentage of the 50 scored questions. The skills it measures, and how much each area weighs, are listed below.

We can tell you that we update our exams monthly, so they always reflect the current state of both the certification and the documentation that supports it. That means our exams follow the certification’s current topic weights, and our domain reviews and explanations are always up to date.

Start Preparing

We can’t tell you how well you know the content — you need to take one of our real exams for that. But our full exams also tell you how you miss: what question answering habits are tripping you up (and we do it across six kinds of ‘bad habits’). We have over 100 answers written that not only test your knowledge but catch those specific bad habits.

These 10 questions, for example, find which kind of ‘almost right’ answers catch you:

Sample exam coming soon.

Skills at a glance

Design Secure Architectures30%
  • Applying AWS security best practices to IAM users and root users (for example, multi-factor authentication [MFA])
  • Designing a flexible authorization model that includes IAM users, groups, roles, and policies
  • Designing a role-based access control strategy (for example, AWS STS, role switching, cross-account access)
  • Designing a security strategy for multiple AWS accounts (for example, AWS Control Tower, service control policies [SCPs])
  • Determining the appropriate use of resource policies for AWS services
  • Determining when to federate a directory service with IAM roles
  • Designing VPC architectures with security components (for example, security groups, route tables, network ACLs, NAT gateways)
  • Determining network segmentation strategies (for example, using public subnets and private subnets)
  • Integrating AWS services to secure applications (for example, AWS Shield, AWS WAF, IAM Identity Center, AWS Secrets Manager)
  • Securing external network connections to and from the AWS Cloud (for example, VPN, AWS Direct Connect)
  • Aligning AWS technologies to meet compliance requirements
  • Encrypting data at rest (for example, AWS KMS)
  • Encrypting data in transit (for example, AWS Certificate Manager [ACM] using TLS)
  • Implementing access policies for encryption keys
  • Implementing data backups and replications
  • Implementing policies for data access, lifecycle, and protection
  • Rotating encryption keys and renewing certificates
Design Resilient Architectures26%
  • Designing event-driven, microservice, and/or multi-tier architectures based on requirements
  • Determining scaling strategies for components used in an architecture design
  • Determining the AWS services required to achieve loose coupling based on requirements
  • Determining when to use containers
  • Determining when to use serverless technologies and patterns
  • Recommending appropriate compute, storage, networking, and database technologies based on requirements
  • Using purpose-built AWS services for workloads
  • Determining automation strategies to ensure infrastructure integrity
  • Determining the AWS services required to provide a highly available and/or fault-tolerant architecture across AWS Regions or Availability Zones
  • Identifying metrics based on business requirements to deliver a highly available solution
  • Implementing designs to mitigate single points of failure
  • Implementing strategies to ensure the durability and availability of data (for example, backups)
  • Selecting an appropriate DR strategy to meet business requirements
  • Using AWS services that improve the reliability of legacy applications and applications not built for the cloud (for example, when application changes are not possible)
  • Using purpose-built AWS services for workloads
Design High-Performing Architectures24%
  • Determining storage services and configurations that meet performance demands
  • Determining storage services that can scale to accommodate future needs
  • Decoupling workloads so that components can scale independently
  • Identifying metrics and conditions to perform scaling actions
  • Selecting the appropriate compute options and features (for example, EC2 instance types) to meet business requirements
  • Selecting the appropriate resource type and size (for example, the amount of Lambda memory) to meet business requirements
  • Configuring read replicas to meet business requirements
  • Designing database architectures
  • Determining an appropriate database engine (for example, MySQL compared with PostgreSQL)
  • Determining an appropriate database type (for example, Amazon Aurora, Amazon DynamoDB)
  • Integrating caching to meet business requirements
  • Creating a network topology for various architectures (for example, global, hybrid, multi-tier)
  • Determining network configurations that can scale to accommodate future needs
  • Determining the appropriate placement of resources to meet business requirements
  • Selecting the appropriate load balancing strategy
  • Building and securing data lakes
  • Designing data streaming architectures
  • Designing data transfer solutions
  • Implementing visualization strategies
  • Selecting appropriate compute options for data processing (for example, Amazon EMR)
  • Selecting appropriate configurations for ingestion
  • Transforming data between formats (for example, .csv to .parquet)
Design Cost-Optimized Architectures20%
  • Designing appropriate storage strategies (for example, batch uploads to Amazon S3 compared with individual uploads)
  • Determining the correct storage size for a workload
  • Determining the lowest cost method of transferring data for a workload to AWS storage
  • Determining when storage auto scaling is required
  • Managing S3 object lifecycles
  • Selecting the appropriate backup and/or archival solution
  • Selecting the appropriate service for data migration to storage services
  • Selecting the appropriate storage tier
  • Selecting the correct data lifecycle for storage
  • Selecting the most cost-effective storage service for a workload
  • Determining an appropriate load balancing strategy (for example, Application Load Balancer [Layer 7] compared with Network Load Balancer [Layer 4] compared with Gateway Load Balancer)
  • Determining appropriate scaling methods and strategies for elastic workloads (for example, horizontal compared with vertical, EC2 hibernation)
  • Determining cost-effective AWS compute services with appropriate use cases (for example, AWS Lambda, Amazon EC2, AWS Fargate)
  • Determining the required availability for different classes of workloads (for example, production workloads, non-production workloads)
  • Selecting the appropriate instance family for a workload
  • Selecting the appropriate instance size for a workload
  • Designing appropriate backup and retention policies (for example, snapshot frequency)
  • Determining an appropriate database engine (for example, MySQL compared with PostgreSQL)
  • Determining cost-effective AWS database services with appropriate use cases (for example, DynamoDB compared with Amazon RDS, serverless)
  • Determining cost-effective AWS database types (for example, time series format, columnar format)
  • Migrating database schemas and data to different locations and/or different database engines
  • Configuring appropriate NAT gateway types for a network (for example, a single shared NAT gateway compared with NAT gateways for each Availability Zone)
  • Configuring appropriate network connections (for example, AWS Direct Connect compared with VPN compared with internet)
  • Configuring appropriate network routes to minimize network transfer costs (for example, Region to Region, Availability Zone to Availability Zone, private to public, AWS Global Accelerator, VPC endpoints)
  • Determining strategic needs for content delivery networks (CDNs) and edge caching
  • Reviewing existing workloads for network optimizations
  • Selecting an appropriate throttling strategy
  • Selecting the appropriate bandwidth allocation for a network device (for example, a single VPN compared with multiple VPNs, Direct Connect speed)

Domains

Design Secure Architectures30%
Design secure access to AWS resources
  • Applying AWS security best practices to IAM users and root users (for example, multi-factor authentication [MFA])
  • Designing a flexible authorization model that includes IAM users, groups, roles, and policies
  • Designing a role-based access control strategy (for example, AWS STS, role switching, cross-account access)
  • Designing a security strategy for multiple AWS accounts (for example, AWS Control Tower, service control policies [SCPs])
  • Determining the appropriate use of resource policies for AWS services
  • Determining when to federate a directory service with IAM roles
Design secure workloads and applications
  • Designing VPC architectures with security components (for example, security groups, route tables, network ACLs, NAT gateways)
  • Determining network segmentation strategies (for example, using public subnets and private subnets)
  • Integrating AWS services to secure applications (for example, AWS Shield, AWS WAF, IAM Identity Center, AWS Secrets Manager)
  • Securing external network connections to and from the AWS Cloud (for example, VPN, AWS Direct Connect)
Determine appropriate data security controls
  • Aligning AWS technologies to meet compliance requirements
  • Encrypting data at rest (for example, AWS KMS)
  • Encrypting data in transit (for example, AWS Certificate Manager [ACM] using TLS)
  • Implementing access policies for encryption keys
  • Implementing data backups and replications
  • Implementing policies for data access, lifecycle, and protection
  • Rotating encryption keys and renewing certificates
Design Resilient Architectures26%
Design scalable and loosely coupled architectures
  • Designing event-driven, microservice, and/or multi-tier architectures based on requirements
  • Determining scaling strategies for components used in an architecture design
  • Determining the AWS services required to achieve loose coupling based on requirements
  • Determining when to use containers
  • Determining when to use serverless technologies and patterns
  • Recommending appropriate compute, storage, networking, and database technologies based on requirements
  • Using purpose-built AWS services for workloads
Design highly available and/or fault-tolerant architectures
  • Determining automation strategies to ensure infrastructure integrity
  • Determining the AWS services required to provide a highly available and/or fault-tolerant architecture across AWS Regions or Availability Zones
  • Identifying metrics based on business requirements to deliver a highly available solution
  • Implementing designs to mitigate single points of failure
  • Implementing strategies to ensure the durability and availability of data (for example, backups)
  • Selecting an appropriate DR strategy to meet business requirements
  • Using AWS services that improve the reliability of legacy applications and applications not built for the cloud (for example, when application changes are not possible)
  • Using purpose-built AWS services for workloads
Design High-Performing Architectures24%
Determine high-performing and/or scalable storage solutions
  • Determining storage services and configurations that meet performance demands
  • Determining storage services that can scale to accommodate future needs
Design high-performing and elastic compute solutions
  • Decoupling workloads so that components can scale independently
  • Identifying metrics and conditions to perform scaling actions
  • Selecting the appropriate compute options and features (for example, EC2 instance types) to meet business requirements
  • Selecting the appropriate resource type and size (for example, the amount of Lambda memory) to meet business requirements
Determine high-performing database solutions
  • Configuring read replicas to meet business requirements
  • Designing database architectures
  • Determining an appropriate database engine (for example, MySQL compared with PostgreSQL)
  • Determining an appropriate database type (for example, Amazon Aurora, Amazon DynamoDB)
  • Integrating caching to meet business requirements
Determine high-performing and/or scalable network architectures
  • Creating a network topology for various architectures (for example, global, hybrid, multi-tier)
  • Determining network configurations that can scale to accommodate future needs
  • Determining the appropriate placement of resources to meet business requirements
  • Selecting the appropriate load balancing strategy
Determine high-performing data ingestion and transformation solutions
  • Building and securing data lakes
  • Designing data streaming architectures
  • Designing data transfer solutions
  • Implementing visualization strategies
  • Selecting appropriate compute options for data processing (for example, Amazon EMR)
  • Selecting appropriate configurations for ingestion
  • Transforming data between formats (for example, .csv to .parquet)
Design Cost-Optimized Architectures20%
Design cost-optimized storage solutions
  • Designing appropriate storage strategies (for example, batch uploads to Amazon S3 compared with individual uploads)
  • Determining the correct storage size for a workload
  • Determining the lowest cost method of transferring data for a workload to AWS storage
  • Determining when storage auto scaling is required
  • Managing S3 object lifecycles
  • Selecting the appropriate backup and/or archival solution
  • Selecting the appropriate service for data migration to storage services
  • Selecting the appropriate storage tier
  • Selecting the correct data lifecycle for storage
  • Selecting the most cost-effective storage service for a workload
Design cost-optimized compute solutions
  • Determining an appropriate load balancing strategy (for example, Application Load Balancer [Layer 7] compared with Network Load Balancer [Layer 4] compared with Gateway Load Balancer)
  • Determining appropriate scaling methods and strategies for elastic workloads (for example, horizontal compared with vertical, EC2 hibernation)
  • Determining cost-effective AWS compute services with appropriate use cases (for example, AWS Lambda, Amazon EC2, AWS Fargate)
  • Determining the required availability for different classes of workloads (for example, production workloads, non-production workloads)
  • Selecting the appropriate instance family for a workload
  • Selecting the appropriate instance size for a workload
Design cost-optimized database solutions
  • Designing appropriate backup and retention policies (for example, snapshot frequency)
  • Determining an appropriate database engine (for example, MySQL compared with PostgreSQL)
  • Determining cost-effective AWS database services with appropriate use cases (for example, DynamoDB compared with Amazon RDS, serverless)
  • Determining cost-effective AWS database types (for example, time series format, columnar format)
  • Migrating database schemas and data to different locations and/or different database engines
Design cost-optimized network architectures
  • Configuring appropriate NAT gateway types for a network (for example, a single shared NAT gateway compared with NAT gateways for each Availability Zone)
  • Configuring appropriate network connections (for example, AWS Direct Connect compared with VPN compared with internet)
  • Configuring appropriate network routes to minimize network transfer costs (for example, Region to Region, Availability Zone to Availability Zone, private to public, AWS Global Accelerator, VPC endpoints)
  • Determining strategic needs for content delivery networks (CDNs) and edge caching
  • Reviewing existing workloads for network optimizations
  • Selecting an appropriate throttling strategy
  • Selecting the appropriate bandwidth allocation for a network device (for example, a single VPN compared with multiple VPNs, Direct Connect speed)