How we built Enclaves: Routing Traffic with Consul

Evervault initially used Amazon Cloudmap for service discovery to deploy apps into trusted execution environments, but faced issues with DNS update timing that caused downtime during Enclave deployments. These issues included premature and delayed traffic routing due to mismatched health checks. Attempts to resolve this with Cloudmap configurations were unsuccessful, leading Evervault to explore alternatives. They eventually migrated to Consul by Hashicorp, which provided a more reliable solution for service discovery without the need for a full service mesh. Consul's system involves a cluster of servers and agents that manage service registration, health checks, and routing more effectively. The adoption of Consul not only removed downtime but also enhanced control over internal routing and visibility into the status of each Enclave. Although integrating Consul required more initial effort, it proved beneficial due to its robust features, extensive documentation, and supportive community.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.