Set the proxy URL of the Elastic Package Registryedit
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
What information is sent to the Elastic Package Registry?edit
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.