Deploy managed Consul in AWS or Azure. Connect Consul clients running on Azure Virtual Machines (VMs), Elastic Compute Cloud (EC2), Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), and/or Elastic Container Service (ECS).
Automate the deployment of a Consul managed service on AWS using the Terraform HashiCorp Cloud Platform (HCP) Consul provider.
8min
Configure Azure VM as a Consul client for HCP Consul Dedicated
Deploy an Azure VM instance running a Consul client and connect it to a specific HashiCorp Cloud Platform (HCP) Consul cluster.
14min
Configure EC2 as a Consul client for HCP Consul Dedicated
Deploy an AWS EC2 instance running a Consul client that can connect to a specific HashiCorp Cloud Platform (HCP) Consul cluster.
17min
Connect an Elastic Kubernetes Service Cluster to HCP Consul Dedicated
Connect an Elastic Kubernetes Service (EKS) cluster to HashiCorp Cloud Platform (HCP).
13min
Migrate your Consul datacenter to HCP Consul Dedicated
Move your KV data and ACL configuration to HashiCorp Cloud Platform (HCP) Consul and migrate your Consul clients.
13min
Connect an Amazon Transit Gateway to your HashiCorp Virtual Network
Create a transit gateway attachment from your Amazon Transit Gateway to your
HCP Virtual Network to enabled low friction, multi-region
networking.
12min
Federate multiple HCP Consul Dedicated clusters
Connect HashiCorp Cloud Platform (HCP) Consul clusters across different regions.
10min
Integrate your AWS ECS services into Consul service mesh
Consul on AWS ECS enables you to add your ECS tasks to the service mesh to manage and connect your services in a consistent manner across different clouds, platforms, runtimes, and networks.
16min
Extend your service mesh to support AWS Lambda
Migrate a Kubernetes service deployment into an AWS Lambda function. Import AWS Lambda functions inside your Consul service mesh using terminating gateways and Consul service splitters.