This page describes the procedure used to deploy the 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 Splunk AppDynamics support.