Elastic Serverless
Production requirements
Complete validation by end of October. Azure Central US is live — finish the open items below before cutover.
- CompleteMust have
Azure Central US region for Serverless
Primary Azure region for production clusters and the application monolith — Serverless must run where the workload already runs for latency.
Delivered by Elastic Product. Use Central US as the home for Azure Central testing and production cutover planning.
- Complete — testedMust have
Private networking (Private Link)
Required for secure connectivity from your network to Elastic Serverless in Azure Central US.
Done and tested in Central US. Keep the private path for app traffic and the audit Logstash bridge.
- Testing + ER #27661Must have
Audit logging to external destinations
Security requires audit events in your domain (Splunk today; Azure Monitor later). GA path is a Logstash bridge over Private Link; native external delivery is Platform ER #27661 (Planned).
Finish Logstash bridge testing in Central US. Drive ER #27661 onto the roadmap for native Splunk / Azure Monitor delivery.
- Complete — PDF runbookMust have
Snapshot restore → Point-in-time restore
Disaster recovery for the Serverless search plane must meet recovery objectives. Product path is point-in-time restore.
PDF runbook provided for Azure Central US. Multi-region restore remains future work.
- Testing in progressMust have
Autoscaling, reindex, and ingest stability
Under production-like load, scale oscillation, interrupted backfills, and ingest tail latency show up together — capacity changes interacting with search and writes.
Run production-like tests in Azure Central US: cooldowns, pre-warm, buffers, resumable reindex, and ingest-tail mitigation before locking write SLOs.
- Complete — runbook publishedMust have
Capacity overrides (pre-scale runbook)
POC hit errors while search capacity scaled up under load. Overrides cover pre-scale, cutover, soak tests, and other planned heavy windows — billing starts at the floor.
Done. Use the published overrides runbook for project, tier, value, when, and customer VCU acceptance. Reservation API later — do not wait for the pilot.
- Complete — articles providedMust have
Autosharding
Index layout for large interactive search on Serverless. Platform autosharding is available and accepted as complete for the production path.
Done. Reference articles shared (autosharding, replicas, tier/ingest autoscaling, stateless architecture). Keep layout in the cutover runbook.
- Complete (via workaround)Nice to have
Cold cache during deployments
Control-plane and node replacement events can clear caches and temporarily raise latency.
Accepted via workaround for GA. Watch cache behavior during Central US deploy and scale tests.