A Comparison of SAP HEC with Virtustream Versus AWS

Executive Summary

  • SAP is aggressively pushing HEC or HANA Enterprise Cloud and other private cloud providers.
  • We compare HEC versus AWS.


Virtustream and AWS are two differently positioned cloud service providers. AWS is the largest cloud provider in the world by far and was the early pioneer in the public cloud. Virtustream is a niche private cloud provider. AWS provides support for a wide variety of applications, which Virtustream is focused on SAP.

The Comparison

AWS supports some SAP applications. However, there are extra complexities to running SAP on AWS. One of the easiest items from SAP to run on AWS is HANA. SAP offers some images of HANA on both AWS, GCP, and Azure under a free development license to entice people to use HANA. This does not extend to SAP’s applications.

Virtustream bristles as the comparison of AWS as a direct competitor. This is explained in the following quotation by the CEO of Virtustream.

While AWS focused on serving scale-out cloud native applications, we architected our cloud platform to solve a different engineering problem: to run scale-up, I/O-centric enterprise applications that require higher availability and security.– Diginomica

Part of this quote is more marketing positioning than a reflection of reality. Here are some interesting points.

  • Scalability: It is unlikely that Virtustream can scale up more than AWS, that it has higher availability than AWS.
  • I/O: The points around I/O might be correct.

Security: Private cloud/hosting is considered to be a good fit for customers with the highest security requirements. But it is difficult to make the argument of higher security than AWS considering all of the security clearance focused government entities that use AWS.

The previous points, combined with the fact that Virtustream is a private cloud means that Virtustream is a premium-priced offering over AWS. Virtustream uses miniaturized virtual machines, with their product call uVM, that it claims improves resource utilization. Virtustream claims 250 production instances (that 1000 SAP total instances, but 250 in production) of HANA and S/4HANA. This seems to be relatively small for a company that makes a big point about how it specializes in SAP.

The Comparison Matrix Provided

We found this comparison matrix sent to a client of ours.

Something of note is that no “cons” are listed with using HEC and Virtustream. However, there are, in fact, cons to using them. The only compared item that has any cons is AWS. The message from this comparison matrix is that AWS is the clear laggard of the compared providers.

This matrix was received from the firm contracted with to perform analysis for the procurement.

This matrix does not do an excellent job of drawing the distinctions between the various cloud providers listed in the matrix. It appears designed to dilute the differences. And second, some of the differences listed in the matrix are inaccurate. The first impression is that this matrix was rigged to push the client down a predetermined pathway. That is the only way the matrix could be so specifically inaccurate.

Let us review each of the line items for accuracy.

  • Instance Size?: According to the matrix, AWS only supports “medium instances?” First, AWS offers very large instances, and these are priced right on their website. We will show the large instance sizes available right from the AWS website further on in this document. Secondly, AWS has very large customers running large instances. All of this is exceptionally well known among those that work in or research cloud service providers
  • All Cloud Providers Lead AWS in Automation?: According to the matrix, AWS only has planned automation, while the other providers have automation currently. What services are considered automation in HEC, HPE, and Azure? It’s difficult to understand what is meant here without more specifics. However, there are many automated services in AWS. Something to consider is that AWS is the leading innovator of cloud service providers. There is virtually nothing that other cloud service providers have that AWS does not have. Examples of automation in AWS include Chef for infrastructure automation. Another is AWS System Management Automation. And a third is Ansible for AWS. Overall, Brightwork ranks AWS in the leader category in automation.
  • All SAP Products Work on All Service Providers?: This matrix proposes that all SAP products can be run on all the cloud service providers. That is incorrect. Not all of SAP’s products will run in the cloud. SAP has very little in the way of production instances in the cloud, particularly as a percentage of their on-premises numbers. SAP’s application has specific limitations in this regard, which need to be overcome during the migration/implementation. There are overall, a low volume of SAP internally developed applications currently residing in a public cloud or even hosted (private cloud). The vast majority of internally developed SAP applications are still delivered on-premises. Products like SuccessFactors or Ariba, primarily acquisitions that were in the cloud before they were acquired by SAP, are designed to run natively in the cloud. The majority of S/4HANA on-premises versions of the application are on-premises rather than the private cloud/hosted.
  • Greenfield Implementations?: Why does AWS only support Greenfield implementations? If the issue is one of hybrid cloud, both Cisco and VMware have introduced hybrid cloud extensions of AWS. This matrix may be dated as both VMware and Cisco hybrid extensions are recent developments.
  • All of the Cloud Service Providers But AWS Support EMEA and APAC?: Which three cloud service providers have the highest CAPEX in the world? The answer is AWS, Google Cloud, and Azure.

Where are the (supposed) missing data centers for AWS in EMEA and Asia?

The following few pages provide coverage of the testing of latency, which contradicts the statement regarding AWS’s limitations internationally. For those interested in the main topic of the overall comparison, scroll past this section.

International Latency Testing

However, of the three hyper-scale could service providers, AWS does lag both Azure and Google Cloud in their network connectivity. This topic is covered in the research by ThousandEyes, which is a company that works in networking and network analysis.

Why AWS chooses to route its traffic through the Internet while the other two big players use their internal backbone might have to do with how each of these service providers has evolved. Google and Microsoft have the historical advantage of building and maintaining a vast backbone network. AWS, the current market leader in public cloud offerings, focused initially on rapid delivery of services to the market, rather than building out a massive backbone network. Given their current position, increasing profitability and recent investments in undersea cables, it is likely that their connectivity architecture will change over time. Enterprises considering a move to the public cloud should consider connectivity architectures to evaluate their appetite for risk while striking a balance with features and functionality. Enterprises should also be aware that even though public cloud backbones are each maintained by a single vendor, they are still multi-tenant service infrastructures that typically don’t offer SLAs. Furthermore, public cloud connectivity architectures continuously evolve and can be subject to precipitous changes at the discretion of the provider.”

However, even though there are differences that give the advantage of Azure and GCP over AWS, in testing, the bi-directional latency was quite similar.

From the US to other regions, the results are quite close, with AWS lagging somewhat in 4 of the five comparisons. But the differences are small.

From Singapore, there is no discernible pattern of advantage between the three providers.

Azure appears to lag both other providers. Each provider only has one location in Central and South America.

Therefore, while AWS lags the other service providers in the physical infrastructure sense, the outcome is that AWS records a very similar performance to Azure and GCP.

There is no possible scenario where Virtustream would compare against AWS or the other two hypercloud service providers listed in the Thousand Eyes study as Virtustream has far fewer data centers than do any of these providers. Even Oracle has only four regions and has historically had a small cloud CAPEX versus the hyperscale providers.

Therefore why is Virtustream listed in the matrix as having a larger geographic scope than AWS? It certainly appears nonsensical.

Conclusion on the Matrix

The matrix provided that is designed to compare HPE to Virtustream to AWS and Azure is has low accuracy. It is inaccurate to the degree that it develops a natural curiosity as to the reasons for why the matrix was developed as it was. Is this a matrix designed to show the technical capabilities of the cloud service providers, or is this a matrix intended to highlight those companies that have the most robust partnership with SAP? Finally, why are so many critical technical details missing from this matrix?

Without any partnership or financial relationship with SAP or any of the cloud service providers, the Brightwork matrix of comparison looks quite a bit different.

These criteria are far more relevant for the client when choosing a cloud provider, and this matrix also illuminates the distinctions between a private cloud offering and a public cloud offering.

What is Private Cloud (in Real Terms) Again?

A final problem with the matrix is that it treats the public cloud (HPE & Virtustream) and public cloud (AWS & Azure) as if they are almost the same thing. However, they are entirely different.

Private cloud is merely a new word for what has historically been known as “hosted.” For example, IBM and CSC have been very dominant in this market for decades before the public cloud ever existed. However, IBM and CSC are very small in revenues in the public cloud. Private cloud/hosted and public cloud providers tend not to play in each other’s spaces. However, nearly all the growth in the cloud is the public cloud, not a private cloud/hosted. Private cloud/hosted does not scale well and is often referred to as just “moving the location of the hardware.”

Technology providers know they have to break into the public cloud market, as that is where the overall market is headed. (hence the IBM acquisition of Red Hat/Open Shift).

Private cloud is not the cloud. The term “private cloud” was created by entities that offered hosting, as a way to rebrand their offering into something that was “cool,” and to piggyback on the concepts of innovation and growth that is primarily in the public cloud.

One cannot get any sense of this from reviewing the matrix above.

The Issue of Private Pricing

One of the requirements of public cloud (sometimes referred to as just cloud) is that it has transparent pricing. Though this public pricing, it can be determined that SAP has been marking up AWS cloud services in some cases that we checked by a factor of 10x. This client was aware of the price difference between Virtustream direct and Virtustream through SAP, but only because Virtustream has provided a separate quote from SAP on Virtustream services. Ordinarily, SAP would prefer that Virtustream not give a quote to this client. SAP would consider a referral back to SAP if this client were to reach out to a private cloud/hosting provider as “good partnership behavior.” If Virtustream repeatedly circumvented SAP to sell directly to SAP customers rather than giving them a markup, Virtustream would immediately disappear from SAP’s recommended providers listing.

The benefit of the public cloud options is that as the pricing is easily determined (online actually from within the cloud service provider consoles), the markup from SAP is a known quantity.

This slide from a presentation by AWS shows a complementary relationship between AWS, SAP, and a number of partners. However, the reality is quite a bit different. Not only SAP but many of the partners on this slide intent to significantly intermediate between AWS and the final customer.

This slide (by AWS) shows what is feasible, but not necessarily what is desirable for customers. Under the scenario where the SAP Cloud is the origination, the prices are dramatically higher. The table to the right shows that AWS claims a far more complete offering than GCP or Azure.

All of SAP’s recommendations for cloud come with a markup over the cloud provider, which SAP does not discuss and pretends does not exist.

Why SAP should be marking up cloud services at all is an interesting topic as they will not be doing the work. For example, SAP does not make a margin on the IT department for an on-premises implementation (that is SAP cannot say, pay us 2x of your internal cost to host our applications), so it is odd that SAP would ask for compensation for something that has nothing to do with.

The Issue of Dedicated Servers and the Public Cloud

As stated, a primary issue is not explained in the matrix, which is that SAP’s internally developed products (not acquired products like Ariba or SuccessFactors) have traditionally run on dedicated servers. This should not be all that surprising. ECC and BW were developed before the public cloud is a delivery mechanism or what we describe as a “hardware modality.” Therefore there are several challenges entailed in moving these applications to the private cloud.

How SAP Uses a Dedicated Server

The primary issue with SAP’s need to use a dedicated server and a primary reason for this is that SAP applications use a dedicated IP address. Private clouds use primarily dedicated servers. However, AWS now also offers dedicated servers.

Amazon/AWS allows for dedicated instance, which means that the instance runs on dedicated hardware. One pays a price premium for this, but dedicated hardware is appropriate in some circumstances. It is desirable to choose a cloud service provider that has both cloud/shared and dedicated capabilities. Some people will comment that AWS only offers shared, but that is no longer true. Although there is little doubt that the vast majority of AWS’s revenues come from shared services.

Notice the instances recommended by AWS for SAP. They lean towards “Memory Optimized” or “EC2 Bare Metal” or dedicated.

Bare Metal is a recent addition for AWS (notice 2H of 2018 in the slide). However, bare metal is far easier to manage than shared resources. It is more of a matter of installing the bare metal infrastructure.

The dedicated instance pricing with AWS is also transparent.

There are instances of S/4HANA that can be used that have transparent pricing. This is called BYOL, or “Bring Your Own License.” A license from SAP could be run on AWS following the BYOL model, which would provide pricing transparency. Under this approach, there is no intermediary.

The price paid by the client would be the AWS price, which is far lower than if SAP plays the middleman.

The screenshot above is the largest S/4HANA instance before one moves to bare metal (which, of course, costs more) in AWS. This configuration has 4 TB of memory and 128 virtual CPUs.

AWS Dedicated Instances

Dedicated instances are available from AWS. As for the need for dedicated instances, we will address this issue from two directions.

  • Experience from the company AutoDeploy, which migrates customers from on-premises to the public cloud, is that this issue of SAP requiring a static IP is overstated, there are some straight ward things that can be done to adjust for this restriction that can be changed.

This need for a dedicated server is waning. The evidence for this is that SAP instances can be brought up directly onto cloud/shared instances.

Even though AWS is the largest cloud service provider in the world, it does not have very many images for S/4HANA. And the ones they do have are previous versions rather than the latest.

This lack of images extends to BW as well.

Some of the images for SAP aren’t much more than Linux images that have been tuned for SAP. In discussions with companies that move applications out to AWS, it is likely they would not use these images, as they are restrictive. Instead, they would build their own.  

  • Something interesting to note is that there are very few images for SAP on AWS outside of HANA and Adaptive Server. This brings up the question of “why.”
  • SAP databases aren’t used outside of supporting SAP applications and SAP reporting, so this shows a large discrepancy between the SAP database and the SAP applications available on AWS. (And BTW, GCP has like no SAP applications.)


*Document Note

The coverage on Containers and Firecracker is of a more technical nature than may be digestible for some readers. It is informational for those with the right background. For those less interested in how to optimize bringing up SAP on the cloud, scroll through this section.


Using Containers & Firecracker

Placing an SAP application on AWS, one would most likely use containers to reduce the number of VMs (virtual machines). Reducing VMs normally has the effect of reducing the price. This is something that could be tested before or during the implementation.

  • Firecracker is a very lightweight virtualization technology or virtual machine manager that is new but already very highly regarded.
  • A new item adopted recently open-sourced by AWS is Firecracker, which could also be tested for improving the cost and performance of placing SAP on AWS.

Firecracker combines the virtues of both virtual machines and serverless (or autoconfigured servers).

Firecracker creates extremely lightweight VMs (called MicroVMs) for the Linux Kernel Virtualization Machine (KVM).

“The number of Firecracker microVMs running simultaneously on a host is limited only by the availability of hardware resources.” – Github

However, from within SAP Cloud, it is feasible to bring up a variety of SAP applications and HANA, where one has a choice of AWS, GCP, and Azure.

Including BPC 11.


  • We brought up S/4HANA 1809. It took 1.5 hours to be available. We found some missing login information restricting our ability to access the application.
  • This trial was brought up for testing purposes, but Brightwork recommends against going through the SAP Cloud for moving SAP applications to AWS, GCP, or Azure.

Virtustream’s Internal Changes as a Company

The cloud area is growing very rapidly, but Virtustream is not growing in US employment in the US, and in fact, appears to be shrinking. Virtustream is moving to a lower-cost model for its employees with less experience and more offshore resources. Overall, Dell’s acquisitions have been negative for the company and for Virtustream customers. (acquired through the EMC acquisition).

The following comment found off of GlassDoor is unheard of in the public cloud space.

“No one is sure of the direction Dell is looking to take this company in, seems they are trying to dissolve. Extremely cut throat atmosphere, major layoffs happening (I heard in the ballpark of 20%). When the most common word that pops up in the company reviews is ‘circus’ that should probably tell you something…”

This quotation also gets to the reputation of Virtustream as a sales-oriented organization that significantly overpromises the ability to deliver.

  • Customers should expect to have lower performance in operations than in the past, as Virtustream is turning over its more experienced technical resources.
  • What Virtustream was before, as they readied for acquisition, is not the company that they are presently, or will be in the future.
  • This will be an issue for the client as delivery will lag the promises of Virtustream.

Company Profiles

In this section, we will provide a profile of each company.


“AWS continues to invest and innovate in the cloud services that it offers. It has evolved to include sophisticated tools for development including machine learning capabilities, a wide range of storage options, IoT and mobile platforms and others. AWS has taken a very proactive approach to compliance with GDPR. AWS global footprint continues to expand to satisfy the needs of its expanding customer base and services offered. It now has: fifty-three availability zones across 18 geographic regions, one local region, and has announced plans for 12 new availability zones and four more regions: Bahrain, Sweden, Hong Kong, and a second US GovCloud region.

The AWS Migration Acceleration Program (MAP) is designed to help enterprises migrating existing workloads to AWS. MAP provides consulting support, training and services credits to reduce risk, to build a strong foundation and to help offset the initial costs. It includes a methodology as well as a set of tools to automate and accelerate common migration scenarios.

AWS has a clear and open approach to security and compliance. It has a very wide range of independent certifications for compliance. AWS has led the CISPE code of conduct to provide clarity to cloud customers around the shared responsibilities for compliance with GDPR and to confirm the steps they are taking to support this.

AWS remains the leading IaaS Global service provider, offering the widest range of services across the greatest number of geographies.” – Ahmed Azmi

AWS Strengths

Strong basic IaaS platform

Rich DevOps capabilities

Speed of innovation of new services

Global footprint for availability and compliance

Hybrid / Private deployment support to cloud enable existing workloads

Independent certifications for a wide range of compliance

Strong security – Ahmed Azmi

AWS Challenges

While AWS has made significant progress in attracting enterprise customers, to retain this leadership position, it must continue to enhance its attractiveness to these customers

Competition from other CSPs that are evolving to challenge AWS position. – Ahmed Azmi


There is a large amount of public information available regarding AWS. This, combined with the ability to test AWS directly, an advantage to all public clouds, provides a low-risk option for the client.


Virtustream is a U.S.-based subsidiary of Dell Technologies, is focused solely on cloud services and software. Virtustream was founded in 2008. It was acquired by EMC in July 2015, and EMC’s managed services and some cloud-related assets were moved into Virtustream before EMC was acquired by Dell in September 2016.

Virtustream’s xStream cloud management platform and Infrastructure-as-a-Service (IaaS) are intended to meet the requirements of complex production applications in the private, public and hybrid cloud. Virtustream is headquartered in New York, NY with major operations in 10 countries.

Virtustream Enterprise Cloud uses patented xStream cloud resource management technology (μVM), to create secure, multi-tenant cloud environments that deliver assured SLA levels for business-critical applications and services. Virtustream provides managed services to help organizations to migrate legacy applications to their cloud platform. It also enables production and mission-critical applications to take advantage of technologies such as Big Data analytics such as SAP HANA and Hadoop, as well the advantages like agility, backup, and disaster recovery offered by cloud computing.

Virtustream Enterprise Cloud offers assured application level SLAs with up to 99.999% availability. High levels of security are provided as standard including 2-Factor authentication; Intel TXT Trusted Computing, separate application zones, integrated GRC, and continuous compliance monitoring. Flexible deployment options from the private cloud (on-premises), virtual private cloud, public cloud, public plus private cloud (hybrid) and trusted federated cloud exchange. The Virtustream offering is SAP certified and is independently certified as being compliance with a wide range of regulations and laws. – Ahmed Azmi

Virtustream Strengths

Innovative platform for migration and deployment of complex applications

Managed services available to support this migration and deployment

Strong security and compliance characteristics

Backing from Dell Technologies – Ahmed Azmi

Virtustream Challenges

Focus on enterprise workload migration rather than DevOps.

Differentiating their offering against the major CSPs evolution towards enterprise solutions. – Ahmed Azmi


Virtustream has a limited footprint and inadequate DevOps and automation compared to AWS. The rate of innovation is low, and internally, the company is facing sustainability issues due to its management.

The key to Virtustream’s differentiation is bundling services like migration, maintenance, and upgrades with hosting, so the customer needs to deal only with Virtustream. AWS has a far superior IaaS, global presence, and automation capabilities. Also, AWS offers a much more full range of services in analytics, database, and more so, the customer will get access and can grow on AWS integrated products. However, AWS provides services via partners, so customers will have to work with two providers rather than one.


Virtustream Enterprise Cloud is hypervisor-neutral but typically supports VMware and KVM. It is offered in both single-tenant and multitenant variants; furthermore, it can support single-tenant compute with a multitenant back end, as well as bare metal. VMs are available by the hour, bare metal is available by the month, and both paid-by-the-VM and SRP models are available. The offering embeds a tool for governance, risk management and compliance (GRC) leveraging capabilities from Virtustream’s Viewtrust software. A similar offering, Virtustream Federal Cloud, targets U.S. federal government customers. The Virtustream Storage Cloud offers S3-compatible object storage that can integrate with some EMC storage products. Managed services are optional. Virtustream also offers its CMP, xStream, as software. – Ahmed Azmi


Virtustream has multiple data centers in the eastern and western U.S., the U.K., France, Germany, the Netherlands, Australia, and Japan. It has a sales presence in the U.S., the U.K., Ireland, Germany, Lithuania, Australia, India, and Japan. Virtustream’s service portal is provided in English, German, Japanese, Lithuanian, Portuguese and Spanish. Documentation and support are provided in English only. – Ahmed Azmi


Virtustream’s roadmap is inextricably tied into other Dell entities, such as VMware, EMC, and Pivotal, which each have their own sets of differing, and possibly competing, priorities. Customers should treat Virtustream as a specialized provider for the workloads that suit the strengths and weaknesses of its technology platform.

Although Virtustream supports self-service capabilities, it primarily targets complex, mission-critical applications where it is likely that the customer will purchase professional services assistance for implementation, and managed services on an ongoing basis.

Virtustream is a compelling and unique provider for particular enterprise application use cases, but it is better suited to implementations where an environment will be carefully and consultatively tuned for the needs of particular applications, rather than general-purpose environments where workloads are deployed without oversight. Prospective customers should ensure that they have a clear understanding of roles and responsibilities and that their expectations match what is actually written in the contract. – Ahmed Azmi

Gartner’s View of Virtustream and AWS

Observe the discrepancy between AWS and Virtustream. In many Gartner Magic Quadrants, the fees paid to Gartner are instrumental in determining the ranking. However, these MQ’s match our viewpoints, and neither AWS nor Google are significant contributors to Gartner. The funds paid by Microsoft show their impact, because we do not see Microsoft anywhere near AWS, and they are significantly behind Google/GCP in the offering, although Microsoft/Azure is larger due to Microsoft’s ability to cross-sell existing customers into Azure.

Advice on Enjoying the SAP Cloud Quiz

To see the full screen just select the lower right-hand corner and expand. Trust us, expanding makes the experience a whole lot more fun.



Whichever way the client decides to go, Brightwork thinks the client must have an accurate representation of these two providers.

A large part of the decision is also related to how much the client wants to take control of their cloud services, versus having everything managed for them. Virtustream by the nature of their business model will provide less transparency than AWS as to the cloud services, as AWS is entirely open to customers. With Virtustream, the infrastructure and the services are combined with one company. With AWS, one can select from many partners ranging from “white-gloved” to smaller partners that tend to provide more specific technical support. Virtustream and AWS are appealing to a very different type of customer.

Financial Disclosure

Financial Bias Disclosure

Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.

What We Do and Research Access

Using the Diagram

Hover over each bullet or plus sign to see more explanation. To move to a different bullet point, just “hover off” and then hover over the new bullet.


Research Access

  • Do You Need to Access Research in this Area?

    Put our independent analysis to work for you to improve your spend.

















For example, Brightwork estimates that roughly 10% of S/4HANA implementations are S/4HANA Cloud.

AWS and Google Cloud Book

How to Leverage AWS and Google Cloud for SAP and Oracle Environments

Interested in how to use AWS and Google Cloud for on-premises environments, and why this is one of the primary ways to obtain more value from SAP and Oracle? See the link for an explanation of the book. This is a book that provides an overview that no one interested in the cloud for SAP and Oracle should go without reading.