Amazon recently announced via their excellent blog, “Now Organize Your AWS Resources by Using up to 50 Tags per Resource”. So what does this mean for AWS customers? As we recently highlighted in an earlier blog “Why is the use of tagging for EBS volumes so important in AWS?”, this new announcement will enable customers, to organize AWS resources with 50 tags per resource. Woohoo!
On the 3rd of August 2016 Gartner published its annual Magic Quadrant for Cloud Infrastructure as a Service and it comes as no surprise to see Amazon Web Services leading the way once again. Gartner, Inc. is an information technology research and advisory company which publish a series of market research reports. One of these reports is the Magic Quadrant for Cloud Infrastructure as a Service which provides market research and qualitative analysis into that market, the direction of that market and the providers within that market.
An annual report survey “The 2016 State of the Cloud” by RightScale.Inc shows cloud adoption is growing and hybrid cloud adoption has increased. With growing maturity in the cloud of both user and providers, security concerns have dropped considerably. The greatest challenge cloud users and providers now face are a shortage of trained resources they need to fuel the growth and cost management and optimization strategies, to elevate the cloud bills and cost concerns for experienced cloud users. With AWS enterprise adoption growing from 50% to 56% in the past year, finding ways you can save money on AWS by eliminating EC2 idle resources will be of great benefit to all AWS customers.
Why do we need a simpler way to launch a new EC2 instance, does AWS not already tell us how simple this process is and how quick and easy it is to set up? This is all true, however, as more organisations migrate to the cloud AWS continually, strive to meet their customer’s demands and develop with them new ways to meet their organisation requirements or giving the customer the right tools for the right job. So let’s compare, What’s involved in creating an AMI and how does it work, compared to creating EBS snapshots?