Using Terraform and Consul to delegate service deployment to service teams
summary
Shows how Terraform and Consul combine: layered Terraform modules and remote state let central teams provision VPCs, subnets and IAM while service teams consume outputs to deploy images and security groups; Consul provides service discovery and health checks with DNS-based routing and an API gateway (Fabio) wired to service metadata. Demonstrates auto‑bootstrap scripts for autoscaling groups, force‑leave quorum handling, and active/standby failover using Consul primitives; demos suffer network hiccups but the patterns and tooling prove repeatable in production.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:33Hash Record Tools
- 2:03Terraform
- 3:55Terraform code
- 6:18Terraform workflow
- 14:30Terraform visualization
- 18:02Azure Virtual Network Test
- 19:04Console
- 24:02DNS
- 28:42Service Registration
- 31:32Deploying independently
- 34:22Outputs
- 35:02Querying data dynamically
- 39:02Deploying software
- 42:42Questions
- 43:42Remote State
- 49:22Console Run
related talks
22mNetwork Automation on Terraform Cloud With CTS
24mA10 & HashiCorp Network Infrastructure Automation with Consul-Terraform-Sync
55mBest practices
22mA Hands-on Approach to Consul Deployment Strategies in a Hybrid Environment
43mConsul Learn Lab: Deploy Resilient Applications with Service Mesh and AWS Lambda
01h 11mCrack the monolith with Consul and Nomad
55mSelf-service infrastructure is no longer a dream
29mInfinity and beyond: Scaling Terraform for the global enterprise