AppDynamics SaaS customers must make sure that their Agents can communicate to the AppDynamics SaaS Infrastructure (including the Controller, Analytics, and EUM) from the customer's network by whitelisting certain IP ranges. Click on the sections below for details:
In a SaaS environment, various Agents communicate to the SaaS Controller to publish metrics.
These Agents can be:
1. Application Agent(Java, PHP, .Net, Python etc)
2. Machine Agent
3. Database Agent
4. WebServer Agent
5. Machine Agent
6. Analytics Agent (v4.3.onwards)
Agents need to connect to an AppDynamics Controller in order to retrieve configuration data and send back information about the monitored environment. The connection between the Agent and the Controller is a one-way connection initiated by the Agent.
To enable these Agents to communicate with a Controller, whitelist the IP range below:
In addition to AppDynamics’ existing ranges, whitelist the following additional blocks or ranges of IP addresses. Due to the technical architecture of the DDoS services provided by our vendor, the entire set of ranges must be whitelisted:
Note: All communication with the AppDynamics SaaS Platform is OUTBOUND-only, and only uses port 443 for HTTPS over TCP. Our customers do NOT need to allow any inbound communication from the AppDynamics SaaS Platform and our customers do NOT need to allow any other ports or protocols in order to use the AppDynamics SaaS Platform.
SaaS customers' Analytics Agent or on-premises Controller needs to communicate with SaaS Analytics Processor in order to publish application/log events.
For the analytics capabilities of the AppDynamics SaaS Platform,
analytics.api.appdynamics.com needs to be whitelisted. If a customer is not comfortable with whitelisting based on DNS names, then they should be whitelisting the full IP range for the AWS UsWest2 region.
Customers with an on-premise Controller will need to whitelist the EUM Cloud Aggregator, located at
Both EUM CloudCollectors and Aggregator are hosted in AWS Region USWest2, same as Analytics.
If the customer can't whitelist based on domain, they should be whitelisting the full IP range for AWS UsWest2 region.
Last Updated: 1/4/18, updates to Controller existing AppDynamics ranges and additional IP blocks.