Regions

Content Cloud can be hosted in the following geographic locations:

• EU (Ireland)

• US (North Virginia)

The region can be set per space and cannot be changed later.

Considerations when selecting a region

• What geographic location is closest to most of your users (or applications)?

• What privacy and compliance requirements do you have to meet?

You can also use replication to serve content in both regions. When doing so, we recommend using the region that’s closest to most of your users as the source region. This can significantly speed up requests leveraging custom user data stores.

Replication

Content can be replicated across multiple regions. This is a full database replication, not just a caching layer. This allows for low-latency, dynamic requests across the globe.

You can assign replication to a space during the creation of the space. Replication cannot be added to a space later.

User requests are automatically routed to the closest database depending on which edge data center they hit.

Privacy

By assigning multiple regions, you agree to host all of your content and user data stores across all regions. If you are storing any PII in your user data stores, please verify that the replication you configure for your project is allowed by your organization.

If you are not sure about the implications of replication, please contact our support team.

Target selection

By default, incoming requests will go to the closest allowed geographic location to the user. If you are not using replication, the request will always go to the same region. Requests requiring read or write access for custom user data will always go to the source region by default.

To force a request to use either the closest region or the source region, you can append a parameter to your request:

• ?region=source to request data from the source region explicitly.

  • This may be wanted if you want to guarantee getting the most recent entry as soon as possible, especially when using the Live API.

• ?region=closest to request data from the closest replica.

  • This may be wanted to speed up requests reading custom user data if you know that user data has not been updated recently.

Please note that this setting is not guaranteed to be applied, as we may be forced to select a different region in some edge cases based on availability, latency, or security considerations.