HashiCorp Consul service mesh on Amazon ECS is now generally available and ready for production environments.
We are pleased to announce the general availability of HashiCorp Consul service mesh on Amazon Elastic Container Service (ECS). Amazon ECS users can now run Consul service mesh in their production environments.
In September, we announced the Consul on ECS public beta. The beta release enabled users to deploy Consul in a secure configuration on Amazon ECS. Since the beta release, the team has focused on making Consul on ECS production-ready through improvements to health checking, zero-downtime startup and shutdown, and more, including:
We are also excited to announce that HashiCorp and AWS have been collaborating on an AWS Cloud Development Kit (CDK) deployment of Consul on ECS. The CDK construct allows CDK users to deploy Consul and makes it easy to add existing ECS tasks into the service mesh.
The following HashiCorp Learn tutorials are available to help you get started with Consul on ECS:
Both tutorials provide guidance on how to deploy a new Consul environment on ECS, or how to integrate an existing Consul cluster with ECS.
To learn more, please visit our documentation, which includes step-by-step instructions for moving existing applications to the service mesh along with detailed architectural information.
The HashiConf Global talk on Adopting Consul on ECS by Jez Halford, Head of Cloud Engineering at Tide, is also a great resource for learning about a real-world deployment of Consul on ECS.
And be sure to watch the AWS-hosted Containers from the Couch talk on deploying Consul as service mesh on Amazon ECS. And check it out later on demand.
General availability of HashiCorp Consul-Terraform-Sync (CTS) 0.6 represents a key step in the maturity of our Network Infrastructure Automation (NIA) solution.
The HashiCorp Releases API is now available. This API is your one-stop shop for finding and viewing extended metadata about HashiCorp product releases.
Add OpenTelemetry to your Java or .NET applications on Kubernetes and combine them with Consul service mesh metrics and traces for use with Prometheus and Jaeger.