Update: In Nov. 2016, AWS introduced a 5th pillar, “operational excellence” to their Well Architected Framework
I got my AWS certification in November. Since then, a lot of people have asked me about it. So here is a blog with suggestions and a review of the Udemy preparation course that I used. AWS has many certifications. The one I have is the AWS Certified Solutions Architect-Associate. I found the time spent on learning AWS to be valuable. Good luck!
Official logo that you receive after getting certified
In today’s “AWS re:Invent” keynote, Andy Jassy, Senior VP of AWS (Amazon Web Services), said that 90% of their roadmap is driven directly by client feedback. For the other 10%, they listen to what the clients say but have to think about what the client really wants and invent on their behalf to solve the problem. Is server name convention one such scenario where those of us in the cloud space need to innovate?
One of my clients is so invested in their DNS naming convention that their applications and security protocols expect servers to follow a specific convention. They have requested that an IaaS (Infrastructure-as-a-Service) solution needs to conform to their DNS naming standard because it would be so difficult to move away from their convention.
Can we build clouds that scale and meet existing DNS naming conventions? Do we want to? In the long-term, when enterprises have fully embraced cloud, my belief is that we will move away from server naming conventions to server tagging and search. Such a transition will neither be quick nor easy. As Mark Twain wrote in The Adventures of Tom Sawyer, “the less there is to justify a traditional custom, the harder it is to get rid of it”. We will need interim solutions.