Consul Service Discovery: DNS vs HTTP API Decision Guide
Guide for choosing between Consul DNS and HTTP API for service discovery, comparing caching, metadata, load balancing, and practical validation steps.
Loading…
ReadMeFeed / Community knowledge
Consul
Real questions. Useful conversations. Find the people who know your stack.
Consul
DevOps & observability · #consul
Consul Connect mTLS and Health Checks for Internal Service Trust
Run a minimal Consul cluster with service discovery, health checks, and Connect intentions to enforce mTLS between internal services.
Securing Microservices with Consul Connect: Moving Beyond Perimeter Security
Stop relying on perimeter firewalls. Learn how Consul Connect uses Envoy sidecars and Intentions to implement mTLS and Zero Trust security across your microservices.
Using Consul Intentions to Enforce Least-Privilege Service Access in Connect
Consul Connect sidecars allow all inbound traffic by default. Intentions provide a declarative allow/deny layer enforced by the proxy, enabling least-privilege service-to-service access without code changes.
Using Consul Connect Intentions to Enforce Zero‑Trust Between Microservices
Learn how Consul Connect intentions let you enforce service‑to‑service allow/deny rules with zero‑trust mTLS, illustrated by a concrete deny‑rule example and its verification steps.
Moving Beyond Hardcoded IPs with Consul DNS Service Discovery
Learn how to use Consul's DNS interface to replace hardcoded IPs with dynamic service discovery and automated health checking.
Enabling Consul Connect mTLS with Minimal Effort: A Practical Guide
Enable Consul Connect’s automatic mutual TLS with a single flag, see a real Docker‑Compose example, verify the handshake, and understand the performance and resource trade‑offs. Secure your micro‑services without touching application code.
Register a Consul Service with a TTL Health Check and Verify DNS Visibility
Use the Consul agent HTTP API to register a service with a TTL health check, verify catalog and DNS visibility, and recover from critical checks or deregistration.
Dynamic Endpoints Without an SDK: Consul Service Discovery and Health Checking in Practice
Hardcoded service IPs break under autoscaling. Consul replaces them with a self-registering catalog and DNS-based discovery—if you tune health checks and TTLs correctly.