| I would not call AWS certs “good”, especially not the associate certs. I have the the three associates and two professional ones. The company paid for all except the first. AWS is so massive, it’s hard to know where to start to get a general overview of it. Studying for and at least doing proof of concepts help with giving you an organized learning path with an end goal in mind. But, I still don’t think that the certifications necessarily show any level of competence. I was the dev lead at a mid size company with a small development shop. I was specifically hired to modernize the department and to architect a green field project. Right after I designed the system, they decided to “move to the cloud”. I knew nothing about AWS at the time and neither did they. So they hired a bunch of “certified consultants”. At the end of the day with the consultants “help”, I ended up setting up an environment just like I would on prem (first mistake) with seven (1 in DEV/QA/UAT and a cluster in production) small VMs for Consul, Nomad, Mongo. I’m already at 21 servers. This doesn’t count two VMs for build servers and 10 or 11 app servers in all. While this design would have been perfectly acceptable for an on prem setup and looking back I wouldn’t have done anything differently if we were on prem, this was a horrible system for AWS. We could have used managed services for everything above and not had a single VM running except the app servers (today we could have used Fargate to avoid even the app servers but it wasn’t around at the time). We could have even used managed ElasticSearch instead of Mongo since the data stored in Mongo wasn’t the source of truth. But the “certified consultants” were a bunch of old school infrastructure guys who only knew how to click around on the web console (2nd mistake) and do a “lift and shift”. I started studying for the AWS Architect Associate just so I could talk intelligently to the consultants and see what type of improvements I could do during phase 2. I had already designed the system to abstract our dependency on Consul, Nomad, and Mongo. I was horrified after discovering all that AWS could have managed for us. I was more horrified that the certified consultants didn’t have a clue. I was most horrified that I passed the certification without ever touching the console and just by watching the videos. For various reasons, I ended up changing jobs shortly there after, to work for a company that was a pure AWS shop with a new (to the company) manager that wanted to be more “AWS native”. I became the “AWS guy” even though I’m a developer. Eventually we started interviewing “AWS Architects”. None of the people we were looking for (mid level) had any practical experience. They had just memorized enough from ACloudGuru to pass a multiple choice test. |
Sure, nothing beats experience, but they are a good place to start your cloud journey :)