Skip to content

Update title of doc on running Elastic Agent in an air-gapped environment & link to it #4098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −3
Open

Update title of doc on running Elastic Agent in an air-gapped environment & link to it #4098

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
418bccd
Update title for the doc on running Elastic Agent in an air-gapped en…
vishaangelova Nov 26, 2025
a928c15
Update the Resources section in agent-es-airgapped.md
vishaangelova Nov 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions manage-data/ingest/ingest-reference-architectures/agent-es-airgapped.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,10 @@ Use when

## Resources [airgapped-es-resources]

Info for air-gapped environments:
For more information on air-gapped environments and running {{agent}} air-gapped, check:
Copy link
Contributor

@colleenmcginnis colleenmcginnis Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think I've seen the phrase "running air-gapped". I've always seen "running in an air-gapped environment". BUT I could be wrong. 🙃 What do you think about something like this?

Suggested change
For more information on air-gapped environments and running {{agent}} air-gapped, check:
For more information on using Elastic in air-gapped environments, check:


* [Installing the {{stack}} in an air-gapped environment](../../../deploy-manage/deploy/cloud-enterprise/air-gapped-install.md)
* [Install the {{stack}} in an air-gapped environment](/deploy-manage/deploy/self-managed/air-gapped-install.md)
* [Install {{ece}} in an air-gapped environment](/deploy-manage/deploy/cloud-enterprise/air-gapped-install.md)
* [Run {{agents}} in an air-gapped environment](/reference/fleet/air-gapped.md)
* [Using a proxy server with Elastic Agent and Fleet](/reference/fleet/fleet-agent-proxy-support.md)

3 changes: 2 additions & 1 deletion reference/fleet/air-gapped.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,13 @@
---
navigation_title: Run Elastic Agents in an air-gapped environment
Copy link
Contributor

@colleenmcginnis colleenmcginnis Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need the full title in the left nav or would Air-gapped environments be sufficient in the context of the nested nav?

If it is necessary to use the full title in the nav, I would recommend not using the sub in the h1 title (just hard-code Elastic Agents) and getting rid of navigation_title in the frontmatter. This would eliminate the risk of the h1 title and the navigation_title getting out of sync if we change it in the future.

mapped_pages:
- https://www.elastic.co/guide/en/fleet/current/air-gapped.html
products:
- id: fleet
- id: elastic-agent
---

# Air-gapped environments [air-gapped]
# Run {{agents}} in an air-gapped environment [air-gapped]

When running {{agent}}s in a restricted or closed network, you need to take extra steps to make sure:

Expand Down
Loading