How to Earn the AWS Golden Jacket

Every week, my DMs fill up with the same question. How do I get the Golden Jacket. What is the process. Where do I apply.

I get why people ask me. And I also get why the information is so scattered, because when I was climbing this Everest Mountain toward my twelfth certification, I had to piece this together myself from conversations with peers, partner teams, and AWS contacts across three continents. There is no AWS page with a “claim your Golden Jacket” button. There is no published process. The path is real, but it is earned in rooms that most people never get invited into.

So I am writing the guide I wish existed when I was at certification number eight. Not a highlight reel. Not a “ninety-day sprint” fantasy. A field guide covering what the Golden Jacket actually is, the five real paths to earning one, why fewer than three hundred people in the world carry it, and what the title opens for you once you do.

This is a Special Bonus of the Golden Jacket Field Notes series. Regular technical programming resumes next week.

The Golden Jacket is a physical jacket, literally gold in color, with AWS Certified embroidered on it. AWS awards it to individuals who hold every generally available AWS certification simultaneously and who have earned recognition from the AWS community and partner ecosystem.

That second part is what most guides miss. The certifications are the foundation. The jacket is a recognition award and a title, and AWS awards it through specific channels rather than through an open application form.

Search around and you will find the common line that the Golden Jacket goes to anyone who holds “all active AWS certifications.” That is the entry ticket, not the full story. I personally know professionals who hold all twelve and are still waiting for their jacket to arrive, because nobody inside AWS has moved their request forward yet. Matthew Venne, who wrote one of the most honest public accounts of the process a couple of years back, describes how his Advanced Partner had to push the request in weekly calls with their AWS rep before his jacket actually got commissioned.

The framing that matches reality is this. The twelve certifications prove you earned the right to ask. The path you walk to claim determines when and how the jacket arrives.

There are Five realistic ways a person earns the Golden Jacket today, and each one opens through a specific relationship with AWS.

This is how I got mine. I work for an AWS Premier Partner, which means we have direct relationships with AWS Partner Development Managers, Partner Solutions Architects, and account teams. When a professional at a Premier or Advanced Partner reaches all twelve active certifications, the Partner team escalates the Golden Jacket request through internal AWS channels.

In practice, this looks like your Partner lead or Alliance Manager opening a conversation with the AWS Partner Manager, confirming your credential status in the AWS Training and Certification Registry, and requesting the jacket on your behalf. Premier Partners carry the most weight in this request. Advanced Partners work too, it just takes a healthy active relationship and a bit more time.

The jacket itself is custom-made. You send your size, the request goes into a production queue, and months later a FedEx tracking number shows up. For international deliveries to Latin America, Asia, or outside the main hubs, the last mile usually hands off to the local postal service. Mine shipped from Kotis Design in the United States through FedEx International Connect Plus and arrived a few weeks later in Brazil.

If you work at a Premier or Advanced Partner, this is the cleanest path. Talk to whoever owns your AWS relationship internally. Not your manager. The person who talks to AWS every week.

If you work at an AWS customer with Enterprise Support, your company has a Technical Account Manager assigned to the account. The TAM has a direct line into AWS internal systems and can route recognition requests through the appropriate teams.

The pattern looks like this across public accounts. The individual reaches twelve active certifications. They bring the accomplishment to their TAM. The TAM verifies credentials through the AWS Training and Certification Center, consults with the account’s solutions architect and account manager, and when internal stakeholders align, the request moves forward.

This path depends on the TAM advocating for you. Make it easy for them. Bring your credential page, your community contributions, the projects you have led inside the account, the customer outcomes you have delivered. You are giving them everything they need to champion you internally.

AWS runs an official Golden Jacket application program tied to re:Invent, the annual Las Vegas conference. There is a real form, a qualification window, and a pickup process at the event. The 2025 program required all twelve AWS certifications to be valid at application time and to remain active during the event itself, December 1 through 5.

This is the most predictable public-facing path. It suits professionals who do not work at a Partner and do not have Enterprise Support access to a TAM. The tradeoffs are clear. You need to be planning to attend re:Invent in person. The application window opens and closes on AWS’s timing. And qualification extends beyond just the certification check, so the program holds discretion.

For anyone already heading to re:Invent with twelve active, this is the path. Watch the AWS events page, the AWS Community social channels, and your re:Invent registration email for the application link when the 2026 program opens.

If you work directly for Amazon Web Services, there is an internal process for earning the Golden Jacket that employees navigate through AWS internal tooling. I am not an AWS employee, so I will not pretend to know the specifics. The consistent pattern across public accounts from former and current AWSers is that employees who reach all twelve active certifications and who have a track record of internal technical contribution earn the jacket through an internal nomination process tied to their org.

If you are at AWS reading this, you already know the path better than I do.

After this article went live, Romain Dupin, a Golden Jacket holder based in France, stepped into the comments with a path I did not cover explicitly. His company has no direct relationship with AWS, no Partner status, no TAM, and he did not go through the re:Invent program. He earned his jacket by reaching out to Julie Elkins, a former AWS professional who now serves as a known community advocate for Golden Jacket candidates and has published public guidance on the process.

Julie validated his twelve active certifications, helped move the request through the right channels, and the jacket arrived in the United States, where a friend received it for him and shipped it to France.

This is the community advocate route, and it deserves its own recognition. For anyone without a Partner relationship, Enterprise Support access to a TAM, or plans to attend re:Invent, reaching out to a trusted community advocate who has institutional memory of how these requests move is a legitimate way in.

The broader lesson is one worth naming. The certifications are yours alone, earned exam by exam with nobody standing in for you. The logistics of claiming the jacket, on the other hand, often move through networks rather than official channels, and that network is part of what makes this community worth being in.

Thank you to Romain for surfacing this, and to Julie Elkins for the work she continues to do for the global Golden Jacket community.

These three programs deserve their own callout. They are not paths to the jacket by themselves. They are accelerators for every other path.

The AWS Community Builders program recognizes early and mid-career professionals who actively contribute content and knowledge to the AWS community. Applications open periodically through the year. Community Builders receive exam vouchers, technical previews, and real visibility with the AWS teams that track community contribution.

The AWS Ambassador program is specific to AWS Partners. It formally recognizes top technical contributors at Partners who publish, speak, and train others on AWS. Ambassadors often receive Golden Jackets during AWS Global Summit recognition ceremonies as part of the Ambassador program benefits.

AWS Heroes is another recognition tier AWS offers. Heroes are named individually by AWS, with a global cap of a few hundred across all categories. Becoming a Hero does not require all twelve certifications. It is a recognition driven by AWS nomination and internal decision, which means the path depends on advocacy, visibility, and timing across AWS teams. Many Heroes happen to hold Golden Jackets, but the two achievements live on different rails. One is awarded. The other is earned by you, one exam at a time, and nobody can hand it to you.

That distinction matters, and it is worth sitting with. The Golden Jacket is one of the few elite recognitions in the entire cloud industry that you conquer by personal merit alone. No nomination. No committee. No political capital to burn. You sit for twelve of the hardest cloud exams in the world, you pass every one, you keep them all active, and the achievement is yours. Community programs and Partner relationships accelerate the moment your jacket ships, but the title itself is the product of your own work. That is exactly why people wear it with pride.

If you are pursuing the Golden Jacket, stay active in Community Builders, Ambassadors, and Heroes programs where they apply to you. They amplify your reach and support the recognition infrastructure around the title. But never forget which part of this was won by you and you alone.

There is no official AWS number for how many Golden Jackets exist. Every source you will find is an estimate. In 2023, a representative at the Certified Lounge at the AWS Public Sector Summit mentioned around one hundred globally. In 2024, a Ukrainian holder estimated roughly one hundred worldwide with fewer than ten in Europe. The community estimate in 2026 places the number under three hundred globally, which makes this one of the rarest public recognitions in the entire cloud industry.

The closest thing to a public census is the AWStronauts community list, created and maintained by Yongkang He, a long-time community builder who also runs the Kubestronaut community programs. The list is community-sourced and voluntary but it remains the most transparent public directory of Golden Jacket holders that exists. I currently sit as the sixth Brazilian Golden Jacket on that list.

Four structural reasons keep the number this low.

All twelve have to be active at the same moment. Each certification is valid for three years. By the time you hit your twelfth, your first one is likely close to expiring, which means you are simultaneously studying new exams and recertifying earlier ones. The window to hold all twelve active at once is narrower than it looks, and it takes real engineering of your calendar to stay inside it.

The specialties are no joke. Solutions Architect Professional and DevOps (Development and Operations) Engineer Professional are hard, but professionals in those roles touch that content daily. The specialty exams force you into territory most cloud architects avoid. Advanced Networking pulls you deep into routing, DNS (Domain Name System), and hybrid connectivity that even senior architects often outsource. Security Specialty demands mastery across identity, encryption, detection, and incident response. Machine Learning Specialty, before it was restructured, was a two-thirds algorithmic exam that broke careers not grounded in statistics. Clearing these exams is proof of serious technical range, which is exactly why the title carries weight.

The target keeps moving. New certifications get added. Old ones get retired. AI Practitioner and Machine Learning Engineer Associate arrived recently. Database Specialty and Data Analytics Specialty were retired. Every time AWS updates the catalog, the math of what counts toward the full set changes, and holders have to adapt immediately to stay current.

Recognition is earned, not issued. Holding all twelve active is the threshold, not the guarantee. AWS recognizes professionals whose credentials are matched by real contribution, real advocacy, and real presence inside the AWS ecosystem. That is why the Golden Jacket means something. It is not a certificate you print. It is a recognition that the community, the Partner network, or AWS itself has stepped forward to confirm.

Those four factors together are why fewer than three hundred people carry this title. Everyone who does has earned it.

This is where the Golden Jacket changes your professional trajectory, because it rewrites the market’s default position on you before you say a word.

For clients, it is proof of range. When a strategic conversation starts and the technical lead on the other side carries all twelve active certifications, the client stops questioning whether you understand their domain. Security, networking, data, machine learning, SAP, DevOps, all of it. The room assumes you have worked every major surface of AWS and can speak each language fluently. That shift reorders the meeting. You stop defending your qualifications and start architecting. Sales cycles shorten. Technical discovery goes deeper, faster. Executive conversations open that would not have opened otherwise.

For the community, it is gravity. Conference organizers, podcast hosts, meetup leaders, partner teams, they are all searching for voices that carry authority on sight. The Golden Jacket is one of the very few credentials that does that globally without any explanation needed. A CFP (Call for Papers) from a Golden Jacket holder gets read with a different level of attention than an identical submission without it. Invitations start arriving instead of being chased. That gravitational pull is one of the real prizes of joining a group this small.

For compensation, the ceiling moves. In Brazil, The Golden Jacket holders sit firmly in the top tier of cloud architect pay. International opportunities open that are simply inaccessible to non-holders, because companies hiring globally use the Golden Jacket as a shortlist filter. Consulting rates move to a different bracket, because clients who engage a Golden Jacket are not buying hours, they are buying twelve domains of expertise compressed into one person with proven range. I have watched peers multiply their market value after the jacket arrived, not because the physical jacket changed their skills, but because the market finally had a clean way to price what they already carried.

For career positioning, it is a category shift. Once you hold the title, the questions you get asked change. Nobody tests whether you can handle a multi-region architecture. The questions move to industry direction, technology bets, strategic trade-offs. You stop being hired for execution and start being consulted for judgment. That is a different category of professional life, and it does not reverse. Once the market places you in the strategic advisor set, it keeps you there.

The biggest shift is positional. You stop being evaluated against local architects and start being evaluated against the international community, which is exactly where the opportunities that matter live. Global Partner roles, international speaking circuits, AWS Hero nominations, advisory boards, paid keynotes. These doors do not open for generic cloud architects no matter how skilled. They open for the recognized few, and the Golden Jacket is one of the clearest public signals that places you in that set.

The jacket opens doors. You walk through them, you deliver when you do, and you keep building. But the doors open. For most architects in the world, these doors never appear at all. That is what the Golden Jacket does.

Once you have the jacket, the job is to stay current, and that discipline is part of what keeps the title meaningful.

Every certification you hold stays active for three years. The clock resets through a recertification exam or through the auto-renewal path where a higher-level certification renews the lower ones in the same family. The full set has to remain active for you to credibly hold the Golden Jacket status publicly.

The approach I follow is simple. I keep a maintenance calendar with every credential’s expiration date and a recertification target three to six months before each one expires. When a new certification goes generally available, I add it to the roadmap immediately. Staying current is the ongoing commitment behind the title, and every Golden Jacket holder I know treats it with the same discipline.

The Golden Jacket is one of the highest public recognitions AWS awards a practitioner. Fewer than three hundred people in the world carry this title. In a profession where credentials multiply and inflate every year, this one still means something, because nobody shortcuts their way through twelve exams across every major AWS domain and keeps them all active while contributing to the community. The Golden Jacket title is earned, it is defended, and the market knows it.

If you are on the climb, keep going. The path is long and the renewals never stop, but the position on the other side is real. You enter rooms you would not otherwise enter. You shape conversations you would not otherwise shape. You carry a credential that signals globally, in any country, in any industry, that you have done the work.

My path took nearly fifteen years of cloud work, cycles of deep study layered on top of full-time architecture roles, and the kind of persistence that only makes sense to people who have been in the climb themselves. I got here. I am proud to carry this title and this jacket, and I am even prouder of the community of Golden Jackets, Heroes, Ambassadors, and Community Builders that AWS has built around it.

The jacket is not the destination for me. It is the base camp. The destination is AWS Hero recognition, consistent international speaking, and technical work that moves the global conversation forward. The jacket confirmed I earned the right to stand in that room. What I build from here is the next chapter, and I am spending 2026 writing it.

If you are pursuing this title, you are pursuing something that matters. Do not let anyone tell you otherwise.

Your turn. If you are on the Golden Jacket path, tell the community where you are. How many active. Which path are you walking. The people in the middle of the climb deserve to see each other, and the people behind you need to see what the road looks like from someone who is actually on it.

If you already carry the jacket, step into the comments and be visible. This community grows stronger every time one of us shows up, tells the story, and lifts the next person coming up.

Erick Mancz is an AWS Solutions Architect and AWS Golden Jacket holder. He writes the weekly Golden Jacket Field Notes series on AWS ML, GenAI, and cloud architecture from a practitioner perspective. Find him on Medium  and LinkedIn .