Gartner Blog Network

New IaaS scores for AWS, Azure and Google based on Gartner’s 234 Evaluation Criteria for Cloud IaaS

by Elias Khnaser  |  July 19, 2016  |  Submit a Comment

Gartner has published the updated cloud IaaS scores for AWS, Azure and Google Cloud Platform. These research documents are among the most anticipated research that we publish. It gives Gartner for Technical Professional (GTP) clients access to in-depth technical assessment of the three major cloud IaaS providers.

The updated in-depth assessments research and scores are based on the May 2016 update of the Evaluation Criteria for Cloud Infrastructure as a Service (Elias Khnaser @ekhnaser) which is now made up of 234 criteria items. The 234 criteria items are organized into 8 categories as follows:

  • Technical:
    • Compute
    • Networking
    • Storage
    • Security and Access
  • Non-technical:
    • Service Offerings
    • Management and DevOps
    • Service and Support Levels
    • Price and Billing

Within each of the above categories, we organize criteria into Required, Preferred and Optional sections. Gartner for Technical Professionals (GTP) clients can also download an interactive Microsoft Excel spreadsheet that allows them to move criteria around based on their requirements. For example, Gartner organizes some regulatory compliance criteria (for example HIPAA) under the Optional category because it does not apply to all clients. However, clients that are in healthcare will find that they may want to move that criteria into the Required category. Once the criteria have been organized based on the client’s requirements, the spreadsheet can then be sent out to major providers in the form of an RFP or an RFQ.

Gartner’s in-depth assessment of AWS, Azure and GCP are the result of extensive research. GTP clients can access these documents here:

Similarly to the Evaluation Criteria research, each of the in-depth assessment documents also have a companion downloadable Microsoft Excel spreadsheet that can be used to move criteria around and instantly rescore the provider. This is very useful to clients that don’t necessarily want to go to RFP or RFQ but still want a score based on their requirements.

In conclusion, I know you are all wondering about the scores, so I will share how each provider faired in the overall Required category:

  • Amazon Web Services: 92%
  • Microsoft Azure: 88%
  • Google Cloud Platform: 70%

I hope GTP clients enjoy the new research and put it to good use. It is the result of hard work and an exhaustive criteria validation process and a brutal vendor review. Gartner clients should also check the 2016 Magic Quadrant for Cloud Infrastructure as a Service as well. The MQ covers many more providers.

Additional Resources

View Free, Relevant Gartner Research

Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.

Read Free Gartner Research


Tags: aws  azure  google-cloud-platform  iaas  public-cloud  

Elias Khnaser
Research Director
1 years at Gartner
18 years IT Industry

Elias Khnaser is a Research Director in the Gartner for Technical Professionals (GTP). He works in the Cloud and Virtualization Strategy group, covering public and hybrid cloud computing, end-user computing, and virtualization. Areas of focus include cloud computing technology, cloud service providers, IaaS, DaaS, virtual desktops and application delivery. Read Full Bio

Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.