Add artifacts-bundler community tool for air-gapped endpoint setups

[pkward]

Summary

This PR adds a community-contributed example to the "Configure offline endpoints and air-gapped environments" documentation. It introduces the artifacts-bundler Bash-based CLI tool that automates downloading Elastic Stack artifacts, endpoint security content, and optionally builds an NGINX image for serving the content in air-gapped environments.

Why This Is Useful

Preparing air-gapped Elastic deployments—especially Elastic Defend with endpoint artifact requirements—is time-consuming and error-prone when done manually. This tool simplifies:

• Multi-version artifact downloading
• Endpoint manifest and global artifact fetch
• Bundle creation (.tar.gz)
• Optional Docker/Nginx server generation

This is especially helpful for DoD or offline regulated environments.

Placement

This contribution adds a dropdown section under:

Step 3: Manually copy artifact updates

in the configure-offline-endpoints-air-gapped-environments.md document. It provides an alternative method using a community-contributed Bash script to automate downloading and bundling endpoint artifacts.

[github-actions]

🔍 Preview links for changed docs

• solutions/security/configure-elastic-defend/configure-offline-endpoints-air-gapped-environments.md

[florent-leborgne]

Hi @pkward, just want to say we've seen your suggestion and are currently discussing it internally as it's not usual for us to openly link to community third-parties from our official docs. We'll provide an update as soon as we have a clear path. Thank you for your contribution, and for your patience!

[xeraa]

Hey @pkward,
This looks like a great addition. Could we interest you in contributing it as a blog post?
To explain it a bit more: The Elastic documentation documents and recommends officially supported tools and configurations, which doesn't quite work here. But it is very useful so we'd love to find the right home for it :)

[pkward]

Hey @pkward, This looks like a great addition. Could we interest you in contributing it as a blog post? To explain it a bit more: The Elastic documentation documents and recommends officially supported tools and configurations, which doesn't quite work here. But it is very useful so we'd love to find the right home for it :)

Yes, of course! Is there a similar process for submitting the contribution as a Blog post?

[xeraa]

Google doc would be preferred so we can go back and forth a bit more easily. I think some context / story around it + a bit more structure (like https://www.elastic.co/blog/elasticsearch-mcp-server-aws-marketplace etc) and we should be good to go. And if you share it with me (philipp at elastic dot co), I can kick off the rest of the process on our side :)

[pkward]

Google doc would be preferred so we can go back and forth a bit more easily. I think some context / story around it + a bit more structure (like https://www.elastic.co/blog/elasticsearch-mcp-server-aws-marketplace etc) and we should be good to go. And if you share it with me (philipp at elastic dot co), I can kick off the rest of the process on our side :)

I just shared the document with you in google docs. Thanks again!

[xeraa]

That was quick :)
I kicked off the blog process internally to work out the finer details. Hold tight.

[florent-leborgne]

Glad we found a way! I take it that we can close this PR.

Feel free to contribute to the docs or suggest other improvements in the future.
Thanks again!

[pkward]

Thank you both! @florent-leborgne @xeraa