This page explains how EdgeConnect provides secure access to services in your private network for Dynatrace apps, workflows, and functions. It also covers host patterns, host mappings, multiple instances, and least-privilege security.
EdgeConnect connects to AppEngine and runs selected HTTP(S) requests inside your network on behalf of the Dynatrace runtime. In the following diagram, each arrow indicates which side starts the connection.
The diagram shows the default deployment:
EdgeConnect can also operate behind an HTTP proxy.
The proxy variant uses the same model, with two differences:
edgeConnect.yaml.If you're using EdgeConnect behind an HTTP proxy that performs TLS interception, add the proxy's certificate to the certificate_paths field to allow EdgeConnect to verify the proxy's identity.
A host pattern is a hostname or wildcard that determines which EdgeConnect configuration handles an HTTP(S) request. The Dynatrace runtime matches the host of each outgoing request against the configured host patterns and selects the corresponding EdgeConnect configuration.
Hostname matching follows three rules.
*) at the start of a host to match multiple hostnames.To create host patterns, see Configure EdgeConnect in Dynatrace. To test which configuration handles a given URL, see Test EdgeConnect routing.
The following example shows how EdgeConnect selects a configuration when a request matches multiple host patterns.
Assume you have two configurations:
staging, with the pattern staging.myapp.org.prod, with the wildcard pattern *.myapp.org, which matches any subdomain, including staging.myapp.org and prod.myapp.org.Because host patterns must be unique, no other configuration can use either pattern.
A request to https://staging.myapp.org/test.html matches both configurations. In this case, the more specific staging.myapp.org pattern takes precedence, so the request is routed to the staging configuration.
Because host patterns must be unique, multiple configurations can't use the same hostname. For example:
localhost.kubernetes.default.svc.cluster.local, accessed from multiple clusters.To address this, use host mappings. Configure a unique host pattern for each EdgeConnect configuration and map it to the shared internal hostname. When a request matches the host pattern, EdgeConnect rewrites the host to the mapped internal hostname before sending the request.
This resolves two common shared-hostname scenarios:
localhost, isolating services that share the same address. See Multiple services on localhost.kubernetes.default.svc.cluster.local, keeping every cluster independently reachable. See Multiple Kubernetes clusters and the implementation walkthrough.For each EdgeConnect configuration, you can deploy multiple container instances to balance the request load across them. Matching requests are distributed across EdgeConnect instances with free capacity.
For multi-configuration and multi-cluster setups, see Manage multiple EdgeConnect configurations and instances.
EdgeConnect follows the least-privilege principle, providing access only to the resources and network paths required for its operation.
restrict_hosts_to property.restrict_hosts_to so its token can't reach an unintended host. For details, see Inject secrets into requests and Secrets.