Google and HashiCorp announce expanded open source collaboration

Google and HashiCorp just announced an expanded collaboration, a move aimed at making it easier for people to take advantage of the features of HashiCorp products while also making optimal use of Google Cloud Platform features and capabilities. The two entities have provided integrations and support since 2013. But now they’re expanding that collaboration. This is the latest example of Google’s recent teaming up with other companies to offer open source tools for GCP users.

There are a lot of potential benefits for developers, operators, and security professionals in using HashiCorp’s open source tools alongside GCP tools, especially now that Google is expanding support in HashiCorp products. Here are some of the areas where you might notice changes thanks to the new expanded collaboration.

Cloud provisioning from Google and HashiCorp

With the Google Cloud provider for HashiCorp Terraform, you can manage a broad array of GCP resource types, including recent additions like Bigtable and BigQuery. HashiCorp has also announced support for GCP in the Terraform Module Registry, giving users easier access to templates for setting up and running their GCP based infrastructure. The two companies also plan on expanding the number of GCP services that can be provisioned with Terraform. This means that Terraform users can adopt a familiar workload across multiple cloud and on-premises environments.

Cloud security

Google and HashiCorp are also working to strengthen the integrations between HashiCorp Vault and GCP. This means that Vault authentication backends for IAM and signed VM metadata will be supported. HashiCorp is also working to support Kubernetes authentication.

Users also now have access to two different authentication backends that they can use to validate a service’s identity in Vault. The first option involves GCP IAM service accounts, which allows you to use an existing IAM identity to authenticate to Vault. And the second involves using Google Compute Engine instance identity tokens to authenticate using an instance’s signed metadata.

Since these are open source products, Google and HashiCorp are also interested in feedback and user innovations.

Photo credit: HashiCorp

Annie Pilon

Annie Pilon is a freelance writer specializing in topics related to business, marketing, social media, and tech. She has a degree in journalism and marketing from Columbia College Chicago and currently works and lives in Michigan.

Share
Published by
Annie Pilon

Recent Posts

Microsoft Teams guest access: How to enable and manage it

Two of the main factors that affect the total cost of an organization’s Microsoft 365…

15 hours ago

Samsung Galaxy Unpacked 2020: Everything you need to know

Samsung rolled out the all-new Galaxy Z Fold 2, Note 20, Note 20 Ultra handsets…

18 hours ago

SAN vs. NAS: Detailed comparison of these two storage technologies

SAN and NAS provide dedicated storage for a group of users using completely different approaches…

21 hours ago

Generation 1 virtual machines: Modernize them and bring them up to date

In many companies, Generation 1 virtual machines have been superseded by Gen 2 VMs. But…

2 days ago

Free VPNs from Hong Kong with ‘no-log policy’ experience data leak

With these free VPNs based in Hong Kong, you may not be paying any money…

2 days ago

Azure DevOps tips and tricks: Using built-in features

These Azure DevOps tips and tricks come fresh from the field where they have been…

2 days ago