Engineering / ENG-1208
US region (Virginia) for Ridgeway Freight
Description
Ridgeway Freight signs in December and goes live in January. Their contract says their people's data stays in the United States, so they can't sit in Frankfurt or London. We open a third region in Virginia (decision in Confluence ENG › ADR-012: A US region for Ridgeway Freight).
What a region means here
Each client is placed in one region at onboarding. Its database rows, files, queue and backups live there. Nothing moves between regions in the app; moving a client is an operations job.
In this epic
- Database, queue and file storage in Virginia (ENG-1209)
us-eastas a region a client can be placed in (ENG-1210)- Nightly backups in the US only (ENG-1212)
- The portal shows the region (ENG-1216)
- notifier reads US clients' events from the US queue (ENG-1217)
Not in this epic
- SMS in the US. Ridgeway signs in with passwords; Okta is untested.
- A US mail account. Mailcrest's account is in the US already.
Go-live: Ridgeway on 12 January. Opening the region in production is OPS-25.
Child issues
- ENG-1209 US region: database, queue and file storage in Virginia Done
- ENG-1210 A client can be placed in the US region at onboarding Done
- ENG-1212 US region: nightly backups in the US only Done
- ENG-1216 Portal shows "United States (Virginia)" on Deployment settings Done
- ENG-1217 notifier: read US clients' events from the US queue Done
Linked issues
- relates to OPS-25 Open the US region (Virginia) for Ridgeway Freight Done
Ridgeway's first 40 people signed in this afternoon (their morning). Closing.