Back to production requirements

Private networking (Private Link)

Status: Complete — tested
Priority: Must have
Audience: Security, platform, networking

Why it matters

Elastic Serverless must be reachable from your application and ops networks without exposing the search plane on the public internet. Private Link is the approved path for production in Azure Central US.

Current state

ItemStatus
Azure Central USDelivered
Private LinkComplete — tested

End-to-end Private Link validation in Central US is done. Use the same private path for application traffic and for the audit Logstash bridge.

What was done

  1. Validated Private Link connectivity to the Central US Serverless project.
  2. Confirmed the approved private path for production use.
  3. Aligned audit Logstash bridge traffic to use Private Link.

Acceptance criteria

  • Application and ops traffic to Serverless uses the private endpoint in Central US
  • Private Link tested end-to-end
  • Runbook includes connect, failover of DNS/endpoint, and break-glass contacts (keep current as ops hygiene)
  • Test evidence available for customer share-out

Related

  • Azure Central US region (delivered)
  • Audit logging to external destinations (Logstash over Private Link)