From 4688f1722677631cd724c2871c927443b50295d6 Mon Sep 17 00:00:00 2001
From: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Date: Mon, 16 Feb 2026 11:43:56 +0100
Subject: [PATCH] Clarify endpoints for checking EPR health and readiness in
 air-gapped environments

This PR is a backport of https://github.com/elastic/docs-content/pull/2130
---
 docs/en/ingest-management/fleet/air-gapped.asciidoc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/en/ingest-management/fleet/air-gapped.asciidoc b/docs/en/ingest-management/fleet/air-gapped.asciidoc
index e56fed30a..62ed27aec 100644
--- a/docs/en/ingest-management/fleet/air-gapped.asciidoc
+++ b/docs/en/ingest-management/fleet/air-gapped.asciidoc
@@ -183,6 +183,9 @@ docker run -it -p 8080:8080 \
     --health-cmd "curl -f -L http://127.0.0.1:8080/health" \
     docker.elastic.co/package-registry/distribution:{version}
 ----
++
+You can use the `/health` or `/health?ready=true` API endpoints to check if EPR is ready to serve requests.
+When either endpoint returns a `200` HTTP status code, the service is ready to handle requests.
 
 [discrete]
 [[air-gapped-diy-epr-kibana]]