My AWS Rocks!

Caveat: I started this post in April because lots of people were shocked at the cost appearing on their bill. I got half way and though it wasn't worth publishing as the chatter would die down. However 4 months later I am still seeing people ask what can they do about IPv4 costs so thought I'd finish it off. So you will know, or should know, that the 1st February 2024 saw AWS introduce charges for all public IPv4 addresses in use within an AWS account.

I was part of a webinar with Jeff Barr where he was discussing creating your own luck. One of the elements he talked about was doing something quickly and more frequently can often be better than waiting to ensure you are doing the right thing. He talked about the OODA model which I discuss later, but it got me thinking about how often in technology we so often get caught up in the detail, or even worse, the wrong detail and we end up not doing anything.

One of the most common post by newcomers to AWS seems to be bill shock or unexpected charges. Some of this is from using a service with out knowing the costs or forgetting to shut something down and incurring costs for longer than planned. Some however is where accounts have been compromised and resources used by someone else. So what can you do to prevent this? This article will look at ways of securing your account and managing your costs. It is a high level article and doesn't go into every service mentioned in detail, however it should give you enough to protect yourself and point you to further resources.

So, I've just completed my AWS Machine Learning Specialty certification. This now brings my total active certifications to 12, the "full suite" of achievable certification. In doing so I'm now eligible for the elusive "golden jacket" awarded by AWS to holders of all certifications. I've had a few people ask my about my certification journey and as often as the how did I do it, is they why did I do it.

This blog follows on from my speaking session as a Community Builder at the AWS Summit in London (June 7th 2024). I looked at why so many people miss understand the Well Architected Framework, and as a result perform poorly in Well-Architected Reviews. While this post will not cover everything I talked about it should give you an idea of the content and act as a reminder if you were at the event.