After the Solutions Architect path (subchapter 32.2), there is another high-level certification that is especially relevant for those following this book, because it connects with its very spirit: the AWS Certified DevOps Engineer – Professional. While the architect focuses on designing systems, the DevOps engineer focuses on automating, deploying, and operating those systems efficiently. This is the certification that validates the automation, CI/CD, and infrastructure as code practices we have worked on throughout the book.

Remember the DevOps culture that permeates this book: the union of development (Dev) and operations (Ops) to build, deploy, and operate software in a fast, automated, and reliable way. Instead of one team building and another deploying "over the wall," DevOps integrates everything with automation, infrastructure as code, and continuous improvement.

Everything you have learned about Terraform (Parts II-V), CI/CD (Chapter 22), observability (Chapter 24), and automation is, in essence, DevOps.

The AWS Certified DevOps Engineer – Professional is an advanced (professional) level certification that validates that you know how to apply DevOps practices in AWS: automate deployments, manage infrastructure as code, set up CI/CD pipelines, monitor systems, and operate them efficiently and reliably.

It is at the professional level (advanced and demanding, like the Solutions Architect Professional), and demonstrates a deep mastery of the automated operation of systems in AWS.

Analogy: if the Solutions Architect (subchapter 32.2) is the architect who designs the building, the DevOps Engineer is the engineer of the construction and automated maintenance: the one who ensures that the building is constructed efficiently, repeatably, and without errors, and that it works perfectly day by day (with systems that monitor, repair, and update themselves). Both are essential and complementary: one designs, the other ensures it is built and operated flawlessly.

This certification is especially aligned with this book because it covers precisely the practices we have worked on chapter by chapter:

If you have internalized the philosophy of automating everything, treating infrastructure as code, and operating with observability, you already think like a DevOps engineer. This certification proves it.

A common question: which to choose, Solutions Architect or DevOps Engineer? The answer depends on your focus, but they are not mutually exclusive (many professionals have both):

💡 Recommendation: if you are attracted to designing systems, prioritize the Architect path; if you are attracted to automating and operating (which is very much the spirit of this book), the DevOps path will suit you perfectly. Ideally, over time, both complement each other.

• Master infrastructure as code (Terraform): it is central. Everything in Parts II-V is directly applicable.
• Understand CI/CD well (Chapter 22): pipelines, automated deployments, deployment strategies.
• Handle observability (Chapter 24): logs, metrics, alarms, traces.
• Practice real automation: set up pipelines, write infrastructure as code, configure monitoring. Real experience is key for a professional certification.

Real world example: an engineer who has worked extensively with Terraform, CI/CD pipelines, and monitoring wants to officially validate their DevOps profile to access better positions. They prepare for the DevOps Engineer Professional: since they already applied these practices in their daily work (infrastructure as code, automated deployments, observability), studying mainly consists of deepening and organizing what they already did, plus practicing scenarios. They pass, and their professional level certification positions them as a highly sought-after senior DevOps profile. For someone who has followed the philosophy of this book, this certification is the natural culmination of their technical profile.

• DevOps unites development and operations to build, deploy, and operate software in a fast, automated, and reliable way; it is the spirit that runs through this entire book (Terraform, CI/CD, observability, automation).
• The AWS Certified DevOps Engineer – Professional is an advanced level certification that validates that you know how to apply DevOps practices in AWS: deployment automation, infrastructure as code, CI/CD, monitoring, and reliable operation.
• If the Solutions Architect is the architect who designs, the DevOps Engineer is the engineer who automates construction and operation. Complementary.
• It is the certification most aligned with this book, because it covers exactly what has been worked on: IaC (Parts II-V), CI/CD (Ch. 22), observability (Ch. 24), automated security (Ch. 23).
• 💡 Architect vs DevOps is not exclusive: choose according to whether you are more attracted to designing or automating/operating; many professionals master both. Prepare by mastering Terraform, CI/CD, and observability, and by practicing for real.

In the next subchapter we will look at certifications to deepen in specific areas: the Specialty certifications.