#38 5 good reasons not to get AWS certified

Download it: MP3 | AAC | OGG | OPUS


Every week, we write about all things AWS. For example, we unbox or review new AWS services. We also share pitfalls that we learned about the hard way ourselves. On top of that, we provide code examples for Infrastructure as Code and Serverless applications.

Subscribe to our newsletter for free!


Don't miss the blog post 5 good reasons not to get AWS certified, the written version of this podcast episode.

Support us

We launched in 2015. Since then, we have published hundreds of articles, podcast episodes, and videos. It's all free and means a lot of work in our spare time. We enjoy sharing our AWS knowledge with you.

Have you learned something new by reading, listening, or watching our content? If so, we kindly ask you to support us in producing high-quality & independent AWS content. We look forward to sharing our AWS knowledge with you.

Support us!


We ask for feedback! Please rate or review our podcast on Apple Podcasts or wherever you listen to your favorite shows. Or send us a message via Twitter (Andreas and Michael) or LinkedIn (Andreas and Michael) or send us an email.


by Pia on the West Coast on
Decided to listen to this one first even though another episode brought me here. Sounds like I am on the right track before I listened to this. Not to belabor the point, my viewpoint is to get certified to support and supplement my other skills from the last century even though my current work is not using AWS. Instead of the certificate being the focal point, I make applying the AWS skills a priority so that I can speak to the experience. My fate has always been that I mess up something, and I have to figure out how to resolve it. I already came to the conclusion that just about every training material is set up as if nothing goes wrong. I leverage my past experience to bridge the gap that the training material might not cover. Generally speaking, some books out there point out traps and pitfalls which makes the material more valuable to me. As for the comment about the 1,000 getting certified that have not gone through the pitfalls, I say, let them experience it. That will separate those that are willing to be uncomfortable and learn from it, from those that are instantly frightened and already rethinking their choices that led them to that point. As with any industry, there are those that know their stuff and there are those that are just getting by and only in it for the fame and glory. Looking forward to catching up on your past material and looking forward to the upcoming ones. Thanks.
by Walid El Sayed Aly on
Thank you so much for the 5 reasons why we should not certify AWS. I totally agree with you, and I also find through blogs, Twitter, GitHub and other open projects are better the skills to refer instead of a certification. But most customers and recruiters are unfortunately not yet able to measure such resources. And they want to show the easiest certificates.

New comment

By submitting your comment you agree that the content of the field "Name or nickname" will be stored and shown publicly next to your comment. Using your real name is optional.

cloudonaut podcast

We are two brothers focusing 100% on Amazon Web Services (AWS). Every other week, one of us prepares the topic of the podcast. The topic is not known to the other one, which results in surprising conversations about all things AWS.

Typically, we are covering the following topics: DevOps, Serverless, Container, Security, Infrastructure as Code, Container, Continuous Deployment, S3, EC2, RDS, VPC, IAM, VPC, and many more.

by Andreas Wittig and Michael Wittig focusing on AWS Cloud


Follow us

Imprint - Privacy Policy