Azure Central US region for Serverless
Status: Complete — delivered; testing phase open
Priority: Must have
Audience: Platform, networking, application owners
Why it matters
Your primary Azure region is Central US — where production clusters and the application monolith already run. Serverless Search must sit in that region for latency.
Region guidance
| Region | Role |
|---|---|
| Central US | Required — primary production region (delivered) |
| East US | Not the production target |
| East US 3 | Longer-term failover / DR once Serverless is available there |
Current state
- Elastic Product has delivered Serverless in Azure Central US.
- Shared with the customer for the Azure Central testing phase (9/29).
- Remaining work is in-region validation: Private Link, audit Logstash bridge, point-in-time restore runbook, and operational stability under load.
Recommendation
- Use Central US as the home for all Serverless test projects and cutover planning.
- Do not design production around East US.
- Pair Central US with Private Link validation in the same footprint.
- Keep East US 3 as the longer-term DR note — not a blocker for Central US testing.
Acceptance criteria
- Serverless Search available in Azure Central US
- Private connectivity validated in Central US
- In-region test results documented for customer share-out
- DR strategy documents East US 3 as the future secondary (when available)
Related
- Private networking (Private Link) — testing in progress
- Audit logging — Logstash bridge testing in progress
- Snapshot restore → Point-in-time restore — runbook needed