Multi-Cloud in Context: Comparing Cloud Survey Results

Multi-Cloud in Context: Comparing Cloud Survey Results

The inaugural HashiCorp State of Cloud Strategy Survey collected responses from more than 3,200 IT practitioners, technical decision makers, and business decision makers in HashiCorp’s opt-in database. That’s a lot of responses for a survey like this, and we’re excited about the insights revealed in the survey. But for added context, we compared five of the key results in our survey against other research to see where our conclusions were reinforced — and where they surfaced other perspectives.

»1. Multi-Cloud Is Here. And There. And Almost Everywhere.

Our survey made it clear that multi-cloud is no longer merely an aspirational goal but an everyday reality for the vast majority of respondents. More than three quarters of respondents said they were already using more than one cloud, and 86% said they expected to be doing so in two years.

Not so long ago, that result might have raised eyebrows, but now similar findings are showing up from many sources. In 2020, IDC predicted that by 2022, “over 90% of enterprises worldwide will be relying on a mix of on-premises/dedicated private clouds, multiple public clouds, and legacy platforms to meet their infrastructure needs.” Methodologies vary, but many recent surveys seem to indicate that’s exactly what’s happening. According to Flexera’s 2021 State of the Cloud Report, for example, 92% of enterprises have a multi-cloud strategy and 82% have a hybrid cloud strategy combining public and private clouds.

The just-released Equinix 2020-21 Global Tech Trends Survey

Largely concurs, indicating that from 2020 to 2012, “hybrid cloud adoption has increased by 12%, while multi-cloud models have increased 11%,” making hybrid cloud the most common deployment of cloud globally, with Asia-Pacific having the greatest level of penetration. By contrast, the Accelerate State of DevOps 2021 survey showed 34% using a combination of public cloud with private cloud/datacenter/on-premises deployments and 21% using multiple public clouds.

»2. Digital Transformation Isn’t Always the Top Driver of Multi-Cloud Adoption

In our survey, digital transformation was the top factor driving multi-cloud adoption, but it was ranked in the top three by only a third (34%) of respondents and followed closely by avoiding vendor lock-in (30%), cost reduction (28%), and scaling (25%).

What

The 2020 IDC report, meanwhile, suggested that multi-cloud helps enterprises achieve “better performance, 24/7 availability, enhanced security, and greater compliance with regulations.”

The Accelerate DevOps report found similar fragmentation. Leveraging the unique benefits of each provider was the most commonly named reason for using multiple cloud providers, but was chosen by only about a quarter (26%) of respondents (respondents were allowed to select only one). According to that report, this suggests that when respondents select an additional provider, they look for differentiation between their current provider and alternatives. The second most common reason for moving to multi-cloud was availability (22%). Unsurprisingly, respondents who have adopted multiple cloud providers were “1.5 times more likely to meet or exceed their reliability targets.”

»3. Cloud Investment Keeps Growing: Is it Paying Off?

Money always matters, and that’s certainly true in the cloud, where there’s increasingly big money at stake. According to the HashiCorp State of Cloud Strategy survey, more than 15% of respondents budgeted at least $10 million on their multi-cloud initiatives, and that figure ballooned to 34% of large enterprises. (Six percent of respondents budgeted $50 million or more.)

What

And in 2020, the IDC report suggested that respondents devote an average of $73.8 million — almost a third (32%) of their IT budget — to the cloud.

Of course, managing cloud spend is just as important as the actual numbers, and almost 40% of respondents to the HashiCorp survey ended up busting their cloud budget, spending more on the cloud than they planned. Surprisingly, bigger budgets seemed to lead to even more spending: 46% of companies budgeting $2 million to $10 million on cloud overspent, compared to just 27% of companies budgeting less than $100,000. Reasons for the overspending range from shifting priorities to COVID-19 to poorly managed resources.

Other surveys found similar results. In the Flexera survey, for example, 36% of enterprises said they spent more than $12 million on the cloud, while 83% spent more than $1.2 million. That’s up significantly from last year, when 20% of enterprises said they spent more than $12 million, and 74% spent more than $1.2 million.

The next question, obviously, is whether enterprises are getting the desired bang for their bucks, or is some of their cloud investment going to waste? According to the new PwC US Cloud Business Survey, “53% of companies have yet to realize substantial value from their cloud investments.” And a recent Virtana survey focusing on FinOps indicates that 82% of organizations have incurred “unnecessary” costs in their cloud operations due to workloads bursting above agreed capacity, overprovisioning of compute or storage resources, storage blocks that are no longer attached to a compute instance, poor job scheduling, over-buying, and other factors.

But the Accelerate DevOps Report offers a ray of hope in this area, noting that “respondents who use hybrid or multi-cloud were 1.6 times more likely to exceed their organizational performance targets.

»4. The Cloud Skills Shortage Is Worse Than You Think

One theme that emerged from the HashiCorp State of Cloud Strategy survey is that many organizations are struggling to develop the in-house skill sets they need to manage a robust cloud infrastructure. That was cited as a top-three multi-cloud challenge by 57% of respondents, and a top-three cloud inhibitor by 41% of respondents. The problem was especially acute in the public sector (53%) and consumer goods/retail companies (51%).

What

The need for “cloud native application development and operations skills” topped the list of 46% of hiring managers in a recent survey report from The Linux Foundation and edX. To be fair, though, the skills issue reaches beyond the need for cloud and container technologies, as ZDNet notes 92% of respondents said they were struggling to find new talent more generally and even to “hold onto existing talent in the face of fierce competition.”

The PwC Cloud Business Survey confirms that the shift to cloud has “only intensified” the “severe talent challenges that are a byproduct of digital transformation.” According to the report, more than half (52%) of “executives cite lack of tech talent — such as skills in cloud architecture, cybersecurity, or DevOps — as a barrier to realizing cloud value. And it gets worse: The report notes that “the digital talent divide affects not just tech specialists, but employees and business leaders who have the skills and mindset to thrive in a cloud-empowered world.”

»5. Yes, the COVID-19 Pandemic Is Accelerating Cloud Adoption

It’s tempting to blame companies scrambling to cope with the effects of the global pandemic for turbocharging the adoption of multi-cloud architectures. But while that’s clearly a factor, the situation is a bit more complicated. While more than half (54%) of HashiCorp survey respondents said that COVID had accelerated their cloud and multi-cloud adoption, most of them called the impact low or moderate.

How

Other surveys also showed pronounced pandemic effects, Almost half (47%) of global respondents to the Equinix survey said COVID had accelerated their digital transformation plans as a result of COVID-19. And 9 out of 10 respondents to the Flexera survey said COVID led to cloud usage “slightly higher than planned” (61%) or “significantly higher than planned” (29%).

But perhaps IDC put the COVID/cloud conundrum best by focusing not on specific effects, but on calling out the cloud’s ability to quickly adapt to changing conditions. As the research firm’s March 2020 press release (IDC Expects 2021 to Be the Year of Multi-Cloud as Global COVID-19 Pandemic Reaffirms Critical Need for Business Agility) noted, the story isn’t necessarily that the pandemic is driving specific technology solutions, but the fact that cloud is so well suited to helping enterprises cope with uncertainty and change. And that’s likely to remain valuable long after we put COVID-19 behind us.

»Learn More

For more insights into how companies are transitioning to the cloud and multi-cloud environments, and the benefits they’re getting from that move, check out the full HashiCorp State of Cloud Strategy Survey. And read more survey analysis on the HashiCorp blog.


Source: HashiCorp Blog

Announcing the Beta Release of Consul Service Mesh for Amazon ECS

Announcing the Beta Release of Consul Service Mesh for Amazon ECS

We are pleased to announce the public beta for HashiCorp Consul service mesh on Amazon Elastic Container Service (ECS). AWS users can now select Consul as their service mesh for secure ECS deployments.

In May 2021, we introduced Consul service mesh for Amazon ECS as a tech preview. Today’s beta release includes several new enhancements since the tech preview:

  • Secure deployment: Consul can now be deployed in secure mode, enabling defense-in-depth security mechanisms using access control lists (ACLs), Transport Layer Security (TLS), and gossip encryption. ACLs are used to provide secure access to Consul’s UI, API, CLI, service communications, and agent communications. Gossip communication between agents is secured and encrypted with a symmetric key, and TLS is used to secure the RPC calls between agents.
  • Support for Amazon ECS launch types: You can now deploy Consul client agents on both Fargate and EC2 launch types. The HashiCorp Consul AWS ECS Terraform module helps deploy applications seamlessly on both launch types.
  • HashiCorp Cloud Platform deployments: You can now deploy Consul client agents on ECS and peer these with Consul server agents on HashiCorp Cloud Platform (HCP).
  • Self-managed deployment on EC2 servers: You also have the option to deploy self-managed Consul server agents on EC2 instances and client agents on ECS instances.

»Deploying Consul Server(s) on HCP with Clients on ECS

Let’s take a look at how you can securely deploy Consul service mesh on ECS with a HCP Consul server cluster.

Consul

First, you need to create a HCP Consul server cluster. You can do so by following the Deploy HCP Consul with Terraform HashiCorp Learn guide. After completing the guide, you should have the server cluster running and the AWS peering between the HashiCorp Virtual Network (HVN) and your AWS VPC established.

Consul uses ACLs to securely communicate between agents and servers. Consul on ECS helps you automatically provision ACL tokens for the Consul clients and services on the service mesh using an ACL controller. The controller is an ECS task that runs in your ECS cluster. It watches for any new tasks that are coming up and creates ACL tokens with Consul. Here’s how to instantiate the ACL controller with Terraform:

module "acl_controller" {
  source 	= "hashicorp/consul-ecs/aws//modules/acl-controller"
  consul_bootstrap_token_secret_arn = aws_secretsmanager_secret.bootstrap_token.arn
  consul_server_http_addr = hcp_consul_cluster.example_hcp.consul_public_endpoint_url
  name_prefix  = “example”
  ...
}

Now you can deploy a service using the mesh-task module with secure features enabled. To configure the mesh-task module, reference the needed credentials from AWS Secrets Manager and enable TLS and gossip encryption.

module "example_app" {
  source = "hashicorp/consul-ecs/aws//modules/mesh-task"
  family = "example-app"
  container_definitions = ...
  ...
  tls                        	= true
  consul_server_ca_cert_arn  	= aws_secretsmanager_secret.consul_ca_cert.arn
  gossip_key_secret_arn      	= aws_secretsmanager_secret.gossip_key.arn
  acls                       	= true
  consul_client_token_secret_arn = module.acl_controller.client_token_secret_arn
  acl_secret_name_prefix     	= “example”
}

After the example-app task starts, the ACL controller will automatically create the ACL token for the service. Now the communication between the example-app task and the Consul cluster is secure.

»Learn More

For additional information about Consul on ECS, please visit our documentation. HashiCorp Learn also offers many other HCP Consul related tutorials.

To deploy Consul on ECS using Terraform, please see the Consul on ECS Terraform module.

If you want to see live demos, here are some upcoming opportunities to see Consul on ECS in action and ask questions:

»Try Consul on ECS Now

As is typical with a beta release, we recommend against using this build in a production environment, but we encourage you to experiment with the new features in a controlled environment. We are eager to see how this support for ECS enhances your service mesh experience. If you encounter an issue, please file a new bug report in GitHub and we’ll take a look.


Source: HashiCorp Blog