Deployment regions and strategies

Your primary deployment region holds all your Coveo data and is where your main organization processes take place. Satellite regions only contain duplicates of the content and services required for your end users to perform queries, namely your index, ML models, and the Search API. The Coveo indexing pipeline, usage analytics service, and main Coveo Platform services remain only in the primary region.

Active-Active is a major Coveo infrastructure resiliency upgrade available for non-HIPAA, production organizations whose primary deployment region is US East. With Active-Active, Coveo distributes the load between two US regions that work in pair: East and Mid West. If an issue occurs in one of the regions, Coveo automatically reroutes traffic to the healthy region to help increase the resiliency of your implementation.

Currently, only organizations whose primary deployment region is US East can benefit from Active-Active. No technical configuration is required, but to make sure you get the most out of this feature, we recommend using your organization endpoints, which help Coveo dynamically route traffic between regions. To benefit from Active-Active, contact your Customer Success Manager. US customers who wish to avail themselves of a 99.999% uptime guarantee powered by Active-Active may do so by contacting their Coveo account executive.

Data residency is a deployment strategy that aims at storing all your Coveo data in a single region. A typical use case is companies based outside of the United States that don’t want their data to be stored in the United States. To handle such scenarios, select another primary deployment region, such as Canada, Ireland or Australia, as your primary deployment region, with no satellite deployment.

The goal of multi-region deployments is to reduce query times for international end users by deploying satellite regions. Rather than having all end user queries travel to and from your primary deployment region, the service automatically routes them to your closest deployment ^[1], primary or satellite, which can dramatically reduce query response time. Additionally, if a satellite deployment encounters an issue, the service routes queries to your primary deployment region. For Search API requests specifically, the closest region will always be favored first, and if the Search API can’t connect to it, the main region and satellites regions alike redirect requests to each other as needed. This increases the overall resiliency of your search solution.