We are pleased to announce that HashiCorp Consul Service (HCS) on Azure is now in public beta. HCS on Azure enables a team to provision HashiCorp-managed Consul clusters directly through the Azure Marketplace and easily leverage Consul’s service discovery and service mesh features within their Azure Kubernetes Service (AKS) or VM-based application environments.
During the public beta period, any user can access the service to conduct a proof-of-concept in a managed, pre-production Consul environment. For a live overview and demo of HCS on Azure and the public beta feature set, please register for the upcoming webinar below.
HCS on Azure lowers the barrier to entry for an organization to implement secure service networking across any Azure compute environment by enabling application teams to:
Over 50 customers were enrolled in the private beta, with the majority expressing interest in multiple use cases and deployment scenarios (shown below on a percentage basis):
Feedback from private beta customers resulted in a number of security related enhancements, including configurable CIDR ranges, ACL bootstrapping, and elimination of public IP addresses—all of which are now available in the public beta. The following full set of features is available for HCS on Azure as of this announcement:
The recommended way to get started is through the HCS on Azure track in HashiCorp Learn. The following guides are available:
Another excellent resource is Cody De Arkland’s three-part blog series:
If you would like to proceed directly to the Azure Marketplace for a test drive, click here. To sign up for status updates or request a demo, please visit the HCS on Azure landing page. If you are new to HashiCorp Consul, please visit the Consul Learn documentation to get started!
Do cloud right with The Infrastructure Cloud from HashiCorp. Unlock developer potential while controlling cloud costs and risk.
A recap of HashiCorp infrastructure and security news and developments from Google Cloud Next, from scaling infrastructure as code to fighting secrets sprawl and more.
Try this example method for transitioning from Consul service discovery to service mesh without affecting uptimes or development teams.