Consul Terraform Sync - Awesome Use Cases
summary
Consul Terraform Sync (CTS) watches Consul and on changes generates terraform tfvars map of services and runs terraform apply, enabling concrete automations: syncing EKS services via Catalog Sync into Consul and populating Boundary host sets so a VPN stays up to date (configures Boundary hosts and targets); turning Consul KV keys into Prisma (formerly Twistlock) runtime allowlists for DNS and pushing identical container/host policies; and updating AWS NLB target groups to remove mTLS-disabled Vault nodes by regenerating targets from service health. Examples include a workshop POC and an AWS proof‑of‑concept that both work end to end.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 1:52What is Consul Terraform Sync
- 3:58How Consul Terraform Sync works
- 8:12Configuring Consul Terraform Sync
- 10:15Use case Kubernetes to Boundary
- 14:24Use case Palo Alto Prisma policies
- 18:41Use case Vault with ELB
- 22:55More use cases and closing
related talks
45mSecure Together: Consul + Vault
15mLightning Talk: Automate and Secure Consul Service Mesh on AWS ECS
49mEnterprise service networking with HashiCorp Consul and AWS (PRT238)
44mStretching the Service Mesh Beyond the Clouds
20mSentinel in action: Policy as code for secure Terraform workflows in HCP
38mModern Service Networking With Consul Connect, Envoy and Kubernetes
58mConsul + Vault Learn Lab: Consul API Gateway
31mStreamlining Compliance: Leveraging Open-Source Terraform AWS modules