This page describes how to install the the Enterprise Console in an AWS environment using an EC2 instance. You then use the Enterprise Console to install the Controller on a separate EC2 instance (using Aurora DB as the backend). 

Launch the EC2 Instance

This example uses this AMI (which is provided by AWS): Amazon Linux AMI 2017.09.1 (HVM), SSD Volume Type - ami-f63b1193. The Amazon Linux AMI is an EBS-backed, AWS-supported image.

The default image includes AWS command-line tools: Python, Ruby, Perl, and Java.

The repositories include: Docker, PHP, MySQL, PostgreSQL, and other packages.

Launch EC2 instance

  1. Select the Instance type. The Enterprise Console has only modest requirements, therefore you can select the t2.medium instance type.
    Select instance type
  2. Use the default instance settings.
    Default instance settings
  3. Increase the storage amount from the default 8 GB to 32 GB.
    Increase storage
  4. Assign the instance to the appd-ec-security-group that you created previously.
    Assign the instance

Prepare the Instance

To launch the instance, you must specify a key pair. If you are using an existing key pair, ensure you have access to the private key file; otherwise, generate a new key pair and download it from the AWS console. The private key file is required to connect to the instance using SSH. 

The new instance should be available after a few minutes. Once the instance is available, you can verify the status using the AWS console. Connect to it through SSH, enter:

ssh -i "<private key file>.pem" ec2-user@ec2-18-222-75-189.us-east-2.compute.amazonaws.com

Then, substitute the appropriate path and filename for your private key file. 

Install the Enterprise Console

Use scp to transfer the Enterprise Console installer binary to your EC2 instance, enter: 

scp -i "<private key file>.pem" platform_setup.sh ec2-user@ec2-18-222-75-189.us-east-2.compute.amazonaws.com:/data

Then, SSH to your EC2 instance and run the installer to install Enterprise Console:

cd /data
chmod 700 platform_setup.sh 
./platform_setup.sh -c

While installing the Enterprise Console, you are prompted to either select a database port, or accept the default port of 3377.

Do not use port 3388 because it conflicts with the Controller database port which is used later in the installation process.

You must have write access to the Enterprise Console installation directory you select.

When installing one Controller in the AWS environment, it is easier to install both the Controller and Enterprise Console on the same host. 

However if you plan to install multiple Controllers and want to manage them through a single Enterprise Console instance, then you should install the Enterprise Console and the Controller on separate hosts.

Complete the installation of Enterprise Console, and make a note of any passwords you specify during the installation process.