AppDynamics recommends that you create aliases used to connect the Aurora database instance to the Controller EC2 instance.
For example:
You should use these aliases when you install the Controller through the Enterprise Console. Using aliases prevents you from tightly coupling the Enterprise Console with the specific Aurora DB instance or EC2 instance hosting the Controller.
For example, if the database were to fail completely, and you needed to restore the database from a snapshot, then you would have a new DNS name for the Aurora DB instance. Pointing the Enterprise Console at an alias, instead of the DNS name for the Aurora DB instance itself, allows you to only update the DNS alias, and leave the Enterprise Console configuration unchanged.
However, if you need to move the Controller to a different EC2 instance, which resides in another Availability Zone (AZ), you can just update the DNS alias to point to the ENI in the new AZ.
For purposes of testing an AWS configuration, it may not be possible to increase DNS aliases. As a result, you can just add entries to the /etc/hosts file on both the Enterprise Console and Controller EC2 instances. For example: