Use Terraform to Extend Consul Service Discovery
The Terraform Consul provider exposes resources used to interact with Consul. You can use this provider to accomplish a number of tasks, including:
- Register external services or services that cannot be registered with local agent
- Reference Consul keys in your Terraform configuration
- Reference a list of agents
»Use Terraform to Register External Services
In a new Learn guide, you will register two external services with a small Consul datacenter. This guide will take you through the steps needed to deploy a three server Consul datacenter and two external services. You will then configure the Terraform Consul provider to register the external services with health checks to Consul.
You have two options for following along with this guide: locally or using the in-page interactive tutorial. If you want to deploy the demo locally, you will clone the Github repo and use Docker Compose.
Register External Services with Terraform
»Monitor Consul with AppDynamics CNS
Additionally, we recently published a guide to enable AppDynamics CNS to monitor Consul. In this new guide, you'll learn how to use the Consul Monitoring Extension for AppDynamics CNS to collect Consul telemetry data and node information.
Sign up for the latest HashiCorp news
More blog posts like this one
HashiCorp and Red Hat, better together
The IBM acquisition of HashiCorp sets up a vision for more tightly integrating HashiCorp Terraform and Vault with Red Hat Ansible and OpenShift
Terraform migrate now generally available
The GA release of Terraform migrate introduces several improvements and new capabilities based on feedback from our beta users.
Simplify policy adoption in Terraform with pre-written Sentinel policies for AWS
The new pre-written policy library co-developed by HashiCorp and AWS is now generally available, aiming to reduce the barrier of adoption for policy as code infrastructure workflows.