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 allowing certain IP ranges.
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+)
Agents need to connect to an AppDynamics Controller in order to retrieve configuration data and send information about the monitored environment. The connection between the Agent and the Controller is a one-way connection initiated by the Agent; the Controller will never initiate a connection out to the Agent. The Agent only needs to use SSL on TCP port 443 for its communication to the Controller.
To enable Agents to communicate with a Controller, permit the IP range below:
Quick Reference: https://docs.appdynamics.com/display/PAA/SaaS+Domains+and+IP+Ranges
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 permitted. If a customer is not comfortable with permitting based on DNS names, then they should designate the full IP range for the AWS UsWest2 region.
Customers with an on-premise Controller will need to permit 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 permit IP addresses based on domain, they should permit the full IP range for AWS UsWest2 region.