Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

On this page:

This page provides considerations and requirements for AWS instances that host the Controller.  

Instance Sizing

The table shows AWS instance sizing by metric ingestion rate. The actual metrics generated can vary greatly depending on the nature of the application and the AppDynamics configuration. Be sure to validate your sizing against the metric ingestion rate before deploying to production. 

Installer Performance ProfileMaximum Metric Count/MinuteMaximum Agent CountController EC2 Instance SizeAurora RDS Instance SizeNotes
Small1 M1,500



This performance profile assumes the use of 6 SSDs using 2 NVMe cards (minimum 800GB each).

 There is no Aurora DB support for 1 M metrics. Both Controller and MySQL reside on the same instance.

Medium3 M7,500r4.4xlargedb.r4.8xlarge 
Large5.5 M10,000r4.8xlargedb.r4.16xlarge 

The numbers here have been updated to reflect the latest performance testing results as of May, 2018.

Elastic Network Interface (ENI)

For AWS, provision an ENI for each Controller host and link the license to the MAC address of the ENI. For more information about ENI, see the AWS documentation at the following link:  


  • No labels