AWS Solutions Architect. Associate
The most popular AWS certification. Broad coverage of core services, the Well-Architected Framework, and basic design tradeoffs.
Cloud certifications are strongest when paired with hands-on infrastructure work. Build something real with Terraform, deploy it in your own account, and document the design choices, that's what wins interviews.
In context
This cert in isolation tells you very little. Here is where it actually sits. The pathways that use it, and the roles it realistically supports.
- Cloud Engineer
- Cloud Support
- DevOps Engineer
- Solutions Architect (associate level)
SAA is the cert that actually moves cloud CVs, and it's also the cert that creates a very particular kind of disappointment. Passing it makes you employable for cloud engineer interviews. It doesn't make you a cloud engineer. The people who get hired off SAA built three small things in a real AWS account before the exam. Usually a static site with CloudFront, a Lambda + DynamoDB CRUD API, and one Terraform-managed VPC. The people who don't get hired studied for SAA, passed, and assumed someone would now teach them. The cert is a baseline. The portfolio is the differentiator.
Recommended prior knowledge
- Basic networking (subnets, routing)
- Linux fundamentals
- Comfort reading IaC (Terraform / CloudFormation)
Common misconceptions
- SAA proves you can architect production systems, it proves vocabulary.
- You need it before doing real work, most teams hire on portfolios.
What this cert does NOT guarantee
- Architect titles
- Senior salaries
- Multi-cloud roles
Practical skills that matter
- VPC design
- IAM least privilege
- Cost optimization
- High-availability patterns
- Infrastructure as Code