# Does Elastic Package Registry need to run for APM to work?

**URL:** <https://discuss.elastic.co/t/does-elastic-package-registry-need-to-run-for-apm-to-work/327245>\
**Category:** APM\
**Tags:** server\
**Created:** [March 8, 2023, 6:28am UTC](https://discuss.elastic.co/t/does-elastic-package-registry-need-to-run-for-apm-to-work/327245 "2023-03-08T06:28:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ong/32/40766_2.png) [@Ong](https://discuss.elastic.co/u/Ong)\
**Post date:** [March 8, 2023, 6:28am UTC](https://discuss.elastic.co/t/does-elastic-package-registry-need-to-run-for-apm-to-work/327245/1 "2023-03-08T06:28:06Z")

</div>

I am setting up APM and understand that the Elastic Package Registry container needs to be running in order to generate the APM server token.  
[Elastic Registry Package](https://www.elastic.co/guide/en/fleet/current/air-gapped.html)

After the initial setup is done, does the Package Registry container still need to be up and running for APM server and agents to run properly?

**Kibana version** : 8.5

**Elasticsearch version** : 8.5

**APM Server version** : 8.5

**APM Agent language and version** : Java

thank you

---

<div class="post-metadata">

**Author:** ![Ong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ong/32/40766_2.png) [@Ong](https://discuss.elastic.co/u/Ong)\
**Post date:** [March 15, 2023, 10:51am UTC](https://discuss.elastic.co/t/does-elastic-package-registry-need-to-run-for-apm-to-work/327245/2 "2023-03-15T10:51:26Z")

</div>

Anyone knows?

---

<div class="post-metadata">

**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\
**Post date:** [March 20, 2023, 10:50am UTC](https://discuss.elastic.co/t/does-elastic-package-registry-need-to-run-for-apm-to-work/327245/3 "2023-03-20T10:50:47Z")

</div>

If you only use Fleet for APM Server, you can preconfigure the installation of the apm integration. In most recent versions, the integration is bundled with and installed from Kibana and does not necessarily require an EPR for apm data ingestion. Everything else related to Fleet requires a reachable EPR though, so you might still see some error logs.  
[https://github.com/elastic/apm-server/issues/10361](https://github.com/elastic/apm-server/issues/10361) discusses in a bit more detail the effects of not having a reachable EPR in airgapped environments

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 10, 2023, 6:51am UTC](https://discuss.elastic.co/t/does-elastic-package-registry-need-to-run-for-apm-to-work/327245/4 "2023-04-10T06:51:23Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.