Run EdgeConnect as a standalone Docker container on a host that can reach your internal systems. The following steps guide you through configuration, deployment, and verification, including certificate and secret management.
Create the EdgeConnect configuration in Dynatrace.
To run EdgeConnect as a Docker container and connect it to Dynatrace, complete the following steps.
Ensure connectivity.
Before you run the container, open the outbound network paths that EdgeConnect needs, and then verify from the Docker host that each one is reachable. EdgeConnect doesn't require any inbound connection from Dynatrace.
https://sso.dynatrace.com/sso/oauth2/token and to https://<your environment ID>.apps.dynatrace.com.Configure the EdgeConnect image.
The EdgeConnect Docker container needs the edgeConnect.yaml configuration file you downloaded from
Settings > General > External Requests when you created the configuration. You reference this file when you run the EdgeConnect Docker image.
The name, oauth.client_id, and oauth.client_secret values in the file must match the configuration you created in the app. Otherwise, EdgeConnect can't connect to the platform.
Example edgeConnect.yaml:
name: my-corporate-networkapi_endpoint_host: abc12345.apps.dynatrace.comoauth:endpoint: https://sso.dynatrace.com/sso/oauth2/tokenclient_id: dt0s10.your-oauth-client-idclient_secret: <your OAuth client secret>resource: urn:dtenvironment:abc12345restrict_hosts_to:- "internal.example.org"- "*.example.com"certificate_paths:- "/path/to/some/certificate.cer"- "/path/to/another/certificate.pem"proxy:server: proxy.example.orgport: 8037exceptions:- "*.foo.com"- "noproxy.example.org"auth:user: proxy-userpassword: <your proxy password>
To inject credentials into outgoing requests, add a secrets section to the same file. See Inject secrets into requests.
You can override certain configuration values through environment variables. For the full field descriptions and their environment variable names, see the Configuration reference.
Verify the EdgeConnect container image.
Dynatrace provides signed container images and Software Bills of Materials (SBOMs) to help you verify image authenticity and review included software components. Verifying image signatures and SBOM attestations can help you identify vulnerabilities and reduce risk. For verification details, see Verify the Dynatrace EdgeConnect SBOM attestation.
Download the EdgeConnect container image.
docker pull dynatrace/edgeconnect:latest
A successful download displays:
Status: Downloaded image for dynatrace/edgeconnect:latestdocker.io/dynatrace/edgeconnect:latest
Always run the latest available version of EdgeConnect, and upgrade regularly.
Run the container from the directory that contains the edgeConnect.yaml file you created.
docker run \--mount type=bind,src=${PWD}/edgeConnect.yaml,dst=/edgeConnect.yaml \-d --restart always \dynatrace/edgeconnect
EDGE_CONNECT_CONFIG_PATH environment variable to the directory that holds edgeConnect.yaml inside the container. For example, EDGE_CONNECT_CONFIG_PATH=/etc/config makes EdgeConnect load /etc/config/edgeConnect.yaml.Validate the connection.
Go to
Settings > General > External Requests > EdgeConnect and check the Availability column. A connected EdgeConnect displays online. If it's still offline, check the Docker container logs for error messages.
When EdgeConnect shows as online, your environment is safely connected to the Dynatrace platform. Any HTTP request from an app function, ad hoc function, or workflow action whose target host matches a configured host pattern runs transparently through EdgeConnect instead of directly through the Dynatrace runtime.
edgeConnect.yaml parameters and environment variables, see EdgeConnect reference.