This page describes the procedure used to deploy the AppDynamics Controller to an AWS environment. 

You can set custom configurations when you manually deploy the Controller to AWS. From these steps, you manually set up security groups, database parameter groups, Amazon Relational Database Service (RDS), Aurora DB instance, EC2 instance, Elastic Network Interface (ENI) for the Controller, DNS CNAMEs, and listeners for your load balancer.

Afterward, you install the Enterprise Console, and then use the Enterprise Console to install the Controller and configure it for the AWS environment. 

Based on the Amazon Machine Image (AMI), you can provision a replacement EC2 instance for the Controller as needed.

For help with your deployment, contact your AppDynamics account, sales, or professional services representative.

Before You Begin

  • Review if Amazon Aurora DB is available in your region – Check the AWS Region Table in the AWS documentation to see if the Amazon Aurora - MySQL-compatible service is available in your particular region.

  • Amazon RDS Password Requirements – There are some naming constraints in the Amazon Relational Database Service (RDS). The master password for Aurora DB can be any printable ASCII character except "/", """, or "@", and must contain 8 to 41 characters. Master password constraints differ for each database engine.
    For details on naming constraints in Amazon RDS, see the AWS documentation.

Deploy the Controller on AWS

To manually deploy the Controller on AWS:

  1. Create Security Groups
  2. Create Custom DB Parameter Groups
  3. Launch an Amazon RDS Aurora DB Instance
  4. Create Database User for Controller
  5. Launch an EC2 Instance for the Controller
  6. Create the ENI for the Controller
  7. Create DNS CNAMEs
  8. Install the Enterprise Console in an AWS Environment 
  9. Install the Controller in AWS Using Aurora
  10. Apply Controller Optimizations
  11. Configure a Load Balancer
  12. Configure Listener Rules

Troubleshooting the Installation

Issue: Controller EC2 Instance Stops

If the Controller EC2 instance stops almost immediately after you install the Controller, there may be an issue with your EBS devices. AWS may report that it is not able to boot from the volumes. If the EC2 machine stops, check and update your EC2 volumes so that they are mounted correctly.