A client can be placed in the US region at onboarding

Project: Engineering
Type: Story
Status: Done Done
Priority: Medium
Reporter: Rafael Duarte <rafael.duarte@acme-hq.example>
Assignee: Piet de Vries <piet.devries@acme-hq.example>
Labels: ridgeway
Components: identity-service
Fix versions: identity-service 2025.12.12
Sprint: Sprint 31
Story points: 8
Parent: ENG-1208 US region (Virginia) for Ridgeway Freight
Created: 12 Nov 2025, 09:20 UTC
Updated: 12 Dec 2025, 14:45 UTC
Resolved: 12 Dec 2025, 14:45 UTC

Description

As ACME operations, I can place a new client in us-east when I create it, so its data never leaves the US.

Acceptance criteria

Regions are eu-central, uk-south and us-east.
identity-service:src/Clients/Client.php keeps the region; it can't be changed through the API.
Every request for a US client is served from the US database; a test proves a US client's rows never reach the EU.
The region shows in the client list of the ops console.

Comments (2)

Piet de Vries · 1 Dec 2025, 15:02 UTC

Region routing works off the client's subdomain lookup, which is global. The lookup table holds only client id, subdomain and region, no personal data. Fine for Ridgeway?

Mira Holm · 2 Dec 2025, 08:15 UTC

Fine. It's the same for UK clients and it's in the DPA wording. Go on.