Managing multiple clusters of HashiCorp tools can be complicated. Target CLI eases the burden by using context profiles to easily switch between different clusters and environments.
Running Boundary workers as dynamic workloads can be challenging. Using the Nomad and Vault integration along with a custom Vault plugin, this process can be seamlessly automated.
Worker management is very dynamic in Boundary and HCP Boundary. With a new custom plugin, you can automate even more tasks, including worker cleanup.
TerraCurl is a utility Terraform provider that allows engineers to make managed and unmanaged API calls in their Terraform code.
HashiCorp’s Rift proof-of-concept app automatically grants and revokes infrastructure access to on-call engineers when an incident is triggered and resolved.
Learn how to achieve machine authentication to HashiCorp Vault with the Azure auth method using Microsoft Azure managed identity — and set it up with Terraform.
Learn how to configure HashiCorp Vault’s OIDC auth method to use Azure as an identity provider.
Learn how to achieve user authentication to HashiCorp Vault with OIDC using Microsoft Azure AD as a central identity provider.
HashiCorp Consul and Nomad use Azure managed identities to authenticate against Azure in order to read tags and manage service principal information.
Secrets management with HashiCorp Vault can use Microsoft Azure managed identities to ease the operational burden of Vault cluster availability: Part 2 in a series.
See how HashiCorp Terraform and Packer can leverage of Microsoft Azure’s Managed Identities.
Learn how the domain model works in HashiCorp Boundary and how it approaches IAM.
Hear the story of how Rob Barnes, who had just joined HashiCorp's Developer Advocates, was tapped to co-emcee HashiConf Digital last June.