# Using the "docker.elastic.co" container registry behind a firewall

**URL:** <https://discuss.elastic.co/t/using-the-docker-elastic-co-container-registry-behind-a-firewall/336888>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [June 26, 2023, 9:40am UTC](https://discuss.elastic.co/t/using-the-docker-elastic-co-container-registry-behind-a-firewall/336888 "2023-06-26T09:40:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![haseHH](https://avatars.discourse-cdn.com/v4/letter/h/a8b319/32.png) [@haseHH](https://discuss.elastic.co/u/haseHH)\
**Post date:** [June 26, 2023, 9:40am UTC](https://discuss.elastic.co/t/using-the-docker-elastic-co-container-registry-behind-a-firewall/336888/1 "2023-06-26T09:40:42Z")

</div>

Hi everyone, I am looking for guidance on how to properly access the "[docker.elastic.co](http://docker.elastic.co)" CR behind a corporate firewall.

This question was already posed back in 2020, but never answered. [Here's that original topic](https://discuss.elastic.co/t/fqdn-for-whitelisting-in-firewall-for-pulling-filebeat-docker-image/238069).

What I did find out so far is that the index seems to be at "[docker.elastic.co](http://docker.elastic.co)" and a needed auth endpoint is found at "[docker-auth.elastic.co](http://docker-auth.elastic.co)", those two can be whitelisted for outgoing traffic without a problem. But then clients are pointed at seemingly random and everchanging CDN endpoints, all under "\*.cloudfront.net". Our enterprise security team forbids us from whitelisting all of Amazon CloudFront in certain networks, where we plan to use Logstash.

Are there any other options, like a dedicated data endpoint?

Thanks in advance,  
Hase

---

<div class="post-metadata">

**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\
**Post date:** [June 26, 2023, 6:01pm UTC](https://discuss.elastic.co/t/using-the-docker-elastic-co-container-registry-behind-a-firewall/336888/2 "2023-06-26T18:01:15Z")

</div>

Is using Docker Hub an option? The images of Elasticsearch, Kibana, Logstash,... get mirrored there. For example [Docker](https://hub.docker.com/_/logstash)

I don't think changes to the backend of [docker.elastic.co](http://docker.elastic.co) are currently planned.

---

<div class="post-metadata">

**Author:** ![haseHH](https://avatars.discourse-cdn.com/v4/letter/h/a8b319/32.png) [@haseHH](https://discuss.elastic.co/u/haseHH)\
**Post date:** [June 27, 2023, 11:42am UTC](https://discuss.elastic.co/t/using-the-docker-elastic-co-container-registry-behind-a-firewall/336888/3 "2023-06-27T11:42:49Z")

</div>

That works for us, thank you! We weren't aware of the parameters allowing for changing the registry used by the charts.

---

<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:** [July 25, 2023, 11:43am UTC](https://discuss.elastic.co/t/using-the-docker-elastic-co-container-registry-behind-a-firewall/336888/4 "2023-07-25T11:43:12Z")

</div>

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