Had a clarification question regarding Scenario 3 mentioned in the docs.
Assuming the Cluster AG will only be used for a) routing agents (from internal networks with private IPs) to the Dynatrace Managed Cluster and b) for Agentless and Mobile RUM then would placing an ELB (with access to the internet and having a public IP) in front of the Cluster AGs (with private IP) suffice?
In this case the Cluster AG can continue to have a private IP and the RUM traffic will hit the ELB endpoint (configured in CMC under Cluster ActiveGate URL) over 443 and the ELB will route traffic back to the Cluster AGs having a private IP over 9999.
Solved! Go to Solution.
Yes, if you're going to have an ELB or any type of load balancer in front of the Cluster ActiveGates there's no need for the ActiveGates to have a public IP address as long as the ELB can route the traffic properly to the internal addresses.
The only requirements for Agentless and mobile RUM is that 1) the browser/app can reach the cluster which routing through the ELB with a public IP address will accomplish and 2) there are valid CA signed certificates in use so the browser can validate and trust the connection.