After the Cloud Practitioner (subchapter 32.1), the next natural step is the most popular and in-demand technical certification in the entire AWS ecosystem: Solutions Architect. It exists at two levels—Associate and Professional—and represents one of the most valued career paths. In this subchapter, we’ll see what they are, how they differ, and how to approach them. It is probably the certification that most boosts a cloud career.

A Solutions Architect is someone who designs architectures on AWS: decides which services to use and how to combine them to build systems that meet requirements (secure, reliable, cost-efficient, etc.). This is essentially what you’ve been learning to do throughout this book, especially with the Well-Architected Framework (Chapter 27).

That’s why this certification is so valued: it certifies that you know how to design well on AWS, a central and highly sought-after skill.

Analogy: a Solutions Architect is like a building architect, but for cloud systems. A building architect decides how to combine materials and structures to build something that fulfills its function, is safe, efficient, and fits the budget. The Solutions Architect does the same with AWS services: combines them to “build” systems that meet requirements. The certification is the “architect’s degree” that proves it.

The Solutions Architect certification has two levels, forming a progression:

The AWS Certified Solutions Architect – Associate validates that you know how to design architectures on AWS following best practices. It is intermediate level and one of the most popular certifications in the world, highly recognized by companies. It demonstrates solid and practical technical competence.

The AWS Certified Solutions Architect – Professional is the advanced level: it validates that you know how to design complex architectures on AWS, making sophisticated decisions in real and difficult scenarios. It is much more demanding than the Associate, and demonstrates deep mastery.

The usual path is first the Associate and then the Professional:

💡 Important: between the Associate and the Professional, the most valuable thing is to gain real practical experience. The Professional asks about complex scenarios that are best understood by having lived them (or practiced them thoroughly). Don’t rush to move up; consolidate with practice.

These certifications cover, in varying depth, everything you’ve learned in the book: networking (Chapter 6), compute (servers, containers, serverless), storage and databases, security (Chapters 7 and 23), high availability and disaster recovery (Chapter 26), cost optimization (Chapter 25), and above all the Well-Architected Framework (Chapter 27), which is at the heart of an architect’s thinking.

The Associate assesses that you know how to apply these concepts to design solid solutions; the Professional, that you know how to do it in complex scenarios and with advanced decisions.

• Master the Well-Architected Framework (Chapter 27): it’s the architect’s core mindset, and many questions revolve around its pillars (balancing security, reliability, cost, performance, etc.).
• Practice designing: when faced with a requirement, think about which services you would use and why. The questions are usually scenarios where you choose the best solution.
• Gain real experience (especially for the Professional): actually building things consolidates knowledge better than just studying.
• Use official resources and practice exams (Chapter 34): to get familiar with the style of the questions.

Real-world example: a developer who already masters the fundamentals wants to move up to cloud architecture roles, which are better paid and more strategic. They earn the Solutions Architect Associate: study architecture design, practice solving scenarios, and pass. Immediately, their profile becomes much more attractive and they land a position with more design responsibility. After a couple of years designing real systems (gaining that valuable experience), they go for the Professional and pass, establishing themselves as a senior architect. That progression—Associate, experience, Professional—hugely boosted their career. For many, the Solutions Architect is the certification that changes their professional trajectory.

• A Solutions Architect designs architectures on AWS (which services to use and how to combine them to meet requirements), exactly what this book teaches, especially the Well-Architected Framework. Like a building architect, but for the cloud.
• The certification has two levels:
  • Solutions Architect Associate: intermediate level, validates that you know how to design well; one of the most popular and valued certifications in the world.
  • Solutions Architect Professional: advanced level, validates that you design complex architectures with sophisticated decisions; much more demanding, demonstrates deep mastery.
• The usual progression: Cloud Practitioner → Associate → (gain practical experience) → Professional. 💡 Don’t rush to move up; real experience is key for the Professional.
• They cover everything in the book (networking, compute, storage, security, HA/DR, costs) with the Well-Architected Framework at the core. Prepare by mastering that framework, practicing designs, gaining experience, and with practice exams.

In the next subchapter, we’ll look at the certification specifically oriented to the culture and practices that run throughout this book: the DevOps Engineer Professional.