Set the proxy URL of the Elastic Package Registry
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Stack
Generally available
Fleet might be unable to access the Elastic Package Registry because Kibana is behind a proxy server.
Also your organization might have network traffic restrictions that prevent Kibana from reaching the public Elastic Package Registry (EPR) endpoints, like epr.elastic.co, to download package metadata and content. You can route traffic to the public endpoint of EPR through a network gateway, then configure proxy settings in the Kibana configuration file, kibana.yml. For example:
xpack.fleet.registryProxyUrl: your-nat-gateway.corp.net
If your HTTP proxy requires authentication, you can include the credentials in the URI, such as https://username:password@your-nat-gateway.corp.net, only when using HTTPS.
In production environments, Kibana, through the Fleet plugin, is the only service interacting with the Elastic Package Registry. Communication happens when interacting with the Integrations UI, and when upgrading Kibana. The shared information is about discovery of Elastic packages and their available versions. In general, the only deployment-specific data that is shared is the Kibana version.