Amazon CloudWatch is an inexpensive way to monitor your solution in AWS and due to the extensive set of metrics provided for every AWS service out of the box, it’s easy and quick to adopt. Granted it’s not going to replace your enterprise monitoring solution overnight, but for those who haven’t got the time or justification to spin up their own Nagios/Zabbix/OpsView solution it can do basic event monitoring and alerting.
It’s fairly legacy these days to use hardcoded IAM Access Key ID and Secret Access Key values to call the AWS API, which has spawned a variety of different ways to obtain and utilise IAM credentials. Wait, what’s wrong with hardcoded credentials? The issues are numerous, some of which have come to the surface because of data breaches. See Dev put AWS keys on Github or leaked access keys resulting in a $6,000 bill for starters.
I’ll start this post by setting out my stall - I’m a self confessed geek. I tinker, tweak and enjoy experimenting with new technologies. The arrival of my daughter a couple of years ago did reduce my tinkering time drastically but I digress. There was a time a few years ago that the keen IT hobbyist would have to invest serious time and money to feed their habit, namely in:
In the 1980s, I have vivid memories of waking up early in the morning and watching ‘Good Morning Britain’. TV-am, the first commercial breakfast show in the UK, was broadcast from Hawley Crescent in Camden Town, London. The only building in London with eggcups on it’s roof was built from scratch. TV-am started off life unsuccessfully as around the time it was due to launch, the BBC launched a rival service.