So far, we have seen AWS certifications for general knowledge: Cloud Practitioner (fundamentals), Solutions Architect (design), and DevOps Engineer (automation and operations). But AWS is huge, and there are areas so deep that they deserve their own specialized certification. These are the Specialty certifications: credentials that demonstrate deep expertise in a specific area of AWS. In this subchapter, we’ll see what they are, what areas they cover, and when it makes sense to pursue them.

AWS has hundreds of services and covers very different fields: advanced networking, security, machine learning, big data, databases... No one can be a deep expert in everything. General certifications (like Solutions Architect) cover a lot, but in breadth, not in the maximum depth of each area. To prove that you are a specialized expert in a specific field, there are the Specialty certifications.

Specialty certifications are AWS credentials that validate deep and specialized knowledge in a specific technical area. They are designed for professionals who have specialized in a field and want to demonstrate that expert mastery. They are usually demanding, because they go much deeper into their topic than the general certifications.

Analogy: general certifications are like being a general practitioner (knows a bit of everything, handles many things), and Specialty certifications are like being a medical specialist (cardiologist, neurologist...): someone who has delved deeply into a specific area and is the expert reference in it. Both are valuable; the specialist is who you go to for deep problems in their field. In AWS, Specialty certifications accredit you as that specialist.

AWS offers Specialty certifications in several highly in-depth technical areas. The main ones include:

Each one corresponds to a field where specialization brings enormous value and where general knowledge is not enough. For example:

• The Security certification goes much deeper into everything we saw in Chapter 23 (and more): it’s for those dedicated to cloud security.
• The Advanced Networking certification goes far beyond basic networking (Chapter 6): for specialists in complex connectivity.
• The Machine Learning or Data certifications are for those dedicated to AI or data platforms (Chapter 29).

⚠️ The specific offering of Specialty certifications changes over time (AWS adds, removes, or renames certifications as technology evolves). The important thing is the concept: there are specialized certifications to accredit expert mastery in specific areas. Check the official AWS website for the current list.

Specialty certifications are not the first step nor for everyone. They make sense when:

• You have specialized (or want to specialize) in a specific area (security, networking, data, ML...).
• Your job focuses on that field and you want to prove your expert mastery.
• You already have a solid foundation (ideally, experience and perhaps an Associate or Professional certification) and want to go deeper in your specialty.

💡 Don’t rush into Specialty certifications. First master the fundamentals and get a general certification; Specialty certifications come when you’ve already oriented yourself toward a specific field and want to be an expert reference in it. They are the cherry on top of a specialized profile, not the starting point.

In a market where many people have general knowledge, specializing sets you apart. A certified expert in a high-demand area (like security or machine learning) is a highly sought-after and valued profile. Specialty certifications accredit that specialization and can open doors to very specific and well-paid roles.

Real-world example: an engineer has spent several years working in cloud security. She already has the Solutions Architect Associate and a lot of practical experience protecting AWS environments (IAM, encryption, threat detection... everything from Chapter 23 and more). She wants to position herself as a security specialist and stand out. She earns the Security Specialty certification, which goes extremely deep into her field. With that credential, her profile becomes that of a certified expert in AWS security, a highly demanded and scarce role. She goes on to lead her company’s cloud security and becomes a reference. Specialization, backed by the Specialty, positioned her as an expert where before she was “just another one.” For her, that was the certification that made her a specialist.

• AWS is so broad that no one is a deep expert in everything; general certifications cover breadth, and Specialty certifications cover depth in an area.
• Specialty certifications validate deep and specialized knowledge in a specific technical area (advanced networking, security, machine learning, data...). They are demanding. Like being a medical specialist versus a general practitioner.
• Each area connects with topics from the book taken to their maximum depth: Security (Ch. 23), Data (Ch. 29), Networking (Ch. 6)... ⚠️ The specific offering changes over time; check the official AWS website.
• They are not the first step: they make sense when you have specialized in a field, your job focuses on it, and you already have a solid foundation. 💡 First fundamentals and a general certification; Specialty certifications are the cherry on top of a specialized profile.
• Specializing sets you apart: a certified expert in a high-demand area is a highly sought-after and valued profile.

In the last subchapter of this chapter, we’ll look at a key certification for the central topic of this book, but which is not from AWS but from HashiCorp: the Terraform Associate.