It was back in 2010 that I first signed up for the AWS free tier and had a play with this latest thing – the public cloud. The original instance type – t1.micro – was slow, but it was great to have a free server on which to host a couple of websites and test out some web application ideas.

Fast forward seven years and AWS is now a $14 billion revenue operation and a hugely-profitable part of Amazon. It controls over one third of the market for cloud infrastructure. No longer is a cloud-based infrastructure unusual – it’s the new normal.

And so, as our two year web hosting agreement came to an end, it seemed logical to move Bright Bee to the cloud. After all, we already use SaaS solutions for many of our day-to-day operations – email, accountancy, time management, messaging, file storage. Why not have a dabble with IaaS too?

The latest tools that AWS provide are slick, getting a new, t2 instance up-and-running took next to no time. Installing the LAMP stack and moving our WordPress site across was easy, it was great to be back at the command line, dabbling with Linux again. The hardest part was securing it all – file permissions, Apache config and checking everything is patched and up-to-date. The metaphorical locking of every door in the house.

It’s probably a bigger job to secure our cloud server than to set it up in the first place, no wonder then that today the National Cyber Security Centre is due to be opened by the Queen backed up by £1.9bn of investment.