Use a proxy with the Universal Profiling Agent
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is not available in Elastic Cloud Serverless. 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.
Serverless
Unavailable
Unavailable
Stack
Generally available
In some cases, your infrastructure Universal Profiling Agent installation needs to use an HTTP proxy to reach Elastic Cloud. In these cases, you can use the HTTPS_PROXY environment variable to configure a proxy used by the Universal Profiling Agent. The connection to the backend (Elastic Cloud) will be tunneled through the proxy (no MITM-TLS) using the CONNECT method. Basic authentication is supported. This can be useful in environments with security policies or network restrictions that block direct connections to outside hosts.
You need to set the HTTPS_PROXY environment variable in the machines that will run the Universal Profiling Agents. If you set the environment variable after the Universal Profiling Agent is installed, you may need to reinstall the Universal Profiling Agent.
The following example shows how to use the HTTPS_PROXY environment variable:
export HTTPS_PROXY=http://username:password@proxy:port