In a previous post, I stressed the importance of hands on experience when it comes to preparing for AWS exams. However, people often object because “it’s too hard”. While they understand the theory, actually using the services is too daunting for them.

Unfortunately this doesn’t bode well for them. Not only does it put them at risk of failing the exam, but it will severely affect their job prospects. Even if they’re lucky enough to pass the exam, certs will only get them so far as explained in this A Cloud Guru post.

To assist people who find themselves in this situation, I’ll be working on a new series of posts dedicated to getting hands on with AWS.

You’ve got the job!

Readers will play the part of a DevOps engineer who has been hired by a startup to build and maintain the company’s AWS environment. To ensure it caters for all experience levels, we’ll start with a single EC2 instance. We’ll then add additional components as the company grows.

Along the way we’ll encounter real world problems. We’ll then implement best practice solutions to solve these problems. As our skills mature, we’ll adopt new services and technologies. We’ll also refactor our environment and applications to increase availability and security while also reducing cost and administrative overhead in order to align with the Well Architected Framework.

What’s next?

Stay tuned! The first post in the series will be posted soon. In the meantime, please set up an AWS account and enable a billing alarm. This will ensure your lab spending is kept to a reasonable level.

Posts in this series

  1. Architecting on AWS: Infrastructure as Code (IAC)
  2. Architecting on AWS: EC2
  3. Architecting on AWS: ALB

As always, if you have any questions or have a topic that you would like me to discuss, please feel free to post a comment at the bottom of this blog entry, e-mail at, or drop me a message on Reddit (OzNetNerd).

Note: The opinions expressed in this blog are my own and not those of my employer.

Leave a comment