Consul Associate case studies
Consul Associate · Put your knowledge to work in context.
HashiCorp Certified: Consul Associate (003) is a professional credential that validates your ability to deploy, configure, and operate Consul as a service networking platform. It is aimed at platform engineers, site reliability engineers, DevOps practitioners, and cloud infrastructure specialists who already work with distributed systems and want to demonstrate practical command of Consul rather than passive familiarity with its documentation. The Consul Associate case studies are 5 cases and about 4,252 words.
1Prepared Query Returns Instances the DNS Interface Would Have Hidden
Northwind runs Consul 1.15 in two datacenters. dc1 has three servers and 40 client agents; dc2 has three servers and 15 clients.
711 words, about 4 min2Flipping default_policy to deny on a Live Datacenter
Contoso is turning on ACLs for real. Servers already run with acl.enabled = true and default policy = "allow" while the team prepares tokens.
852 words, about 4 min3Snapshot Restore That Rolls Back ACLs and Intentions
Fabrikam runs five Consul servers and about 300 client agents. KV holds roughly 200,000 keys for runtime configuration, ACLs are enabled with per-team tokens, and Connect intentions are in use.
861 words, about 4 min4L7 Intention That Behaves Like a Blanket Allow
Tailspin runs Connect with Envoy sidecars for 30 services in one datacenter, with mTLS on. The security team added a wildcard - deny intention and then per-service allows, and asked the payments team to expose only GET /v1/public/ to web .
865 words, about 4 min5New Datacenter Never Elects a Leader
Globex is standing up a new production datacenter: five m5.large instances across three AWS AZs tagged consul-server=true env=prod , plus 60 clients in a second VPC that peers over a transit gateway. Every server config uses retry join with provider=aws tag name=consul-server,env=prod and a shared encrypt key.
963 words, about 5 min