If you are doing anything in cloud computing these days, you are probably doing it at least in part with Amazon Web Services, known as AWS to its many friends. This is what has made re:Invent, the AWS trade show, such a critical part of the cloud computing circuit, even though this year marks only the second re:Invent.
It’s amazing to think how quickly all this has happened. AWS was only launched in 2004, but in that short time the service has displaced many players who were much better established on paper. As I have had occasion to say, with cloud computing it’s no longer a question of when, but simply of how.
A huge part of the reason for the rapid success of AWS has been its ease of adoption. Users frustrated with the slow and bureaucratic delivery options offered by their internal corporate IT departments jumped at the chance to do their own IT procurement with nothing more than a credit card. Their users’ sudden migration to AWS provided a salutary wake-up call to those IT departments who had relied for too long on being the only choice users had.
However, this success brought with it some headaches. The enterprise view of AWS is coloured by fears of compliance violations and security breaches, not to mention fear of downtime. That last is unfortunately not unreasonable, given the repeated troubles of the US-East-1 AWS zone, but in fairness it has to be said that good application design, spanning multiple availability zones, can mitigate or even nullify the impact of AWS outages.
After going through the usual phases of dealing with public cloud options encroaching on “their” turf (denial, anger, bargaining, depression, and finally acceptance), corporate IT departments have by and large realised the great benefits that AWS can offer, and are focusing on how to access those features and services in a way that works for them and their constraints. For instance, AWS operates according to a Shared Responsibility Model, meaning that they will ensure the security and compliance of the infrastructure problem, but customers are responsible for everything from the operating system on up. Also, AWS operates much like a bartender who is happy to continue serving customers without asking too many questions. If they are buying with the corporate credit card, oversight is for their manager, whether we are talking about drinks or cloud services.
BMC is here to help with both parts of that problem. Intelligent placement logic built right into our Service Governor can ensure that only services appropriate for AWS are routed there, while other services with more specialised requirements – whether around geographical location, performance requirements, security standards, or technical compatibility – are routed to other infrastructure options. Once deployed, ongoing compliance audits with automated remediation capabilities can ensure that those services stay compliant to whatever standards until they are decommissioned at the end of the originating business requirement.
Thanks to our deep experience with processes and procedures, BMC can also offer plug-in integration of ITIL change management processes across all cloud delivery options, including AWS. Of course this does not mean having to convene the Change Advisory Board every time someone needs an AMI to be deployed! Rather, standard changes are approved automatically, created for the audit trail and the service model, while manual approval is reserved for anything out of the ordinary.
If you want to find out more about how BMC can work with you to make your AWS initiatives successful, Alan Chhabra, our VP of Worldwide Cloud Sales, will be talking about “Professional Grade Cloud for your Hybrid Needs” on the 14th at 4.15pm in Lido 3103. You can also come and visit us any time at booth 1000 to talk about your specific use cases and see a live demo of the various BMC products that could help make it a winning project. After all, the cloud loves a winner.