Prepare for installation on Amazon Web Services - Use these steps to prepare the Amazon Web Services ( AWS ) instances for the Control Room installation.

Automation 360

Use these steps to prepare the Amazon Web Services (AWS) instances for the Control Room installation.

Before you begin

If you have not done so already, prepare your AWS Identity and Access Management (IAM) user account to login to the AWS Console.

Do the following:

  1. Create AWS Elastic Compute Cloud (EC2) Instances for the Control Room Servers.
  2. If you use RDS, create Relational Database Service (RDS) Instances for the SQL Server Enterprise 2014 Database server.
  3. Configure the AWS Load Balancer.

About this task

Note: There are many possible system configurations and requirements. These installation steps do not account for all those possibilities so your specific setup and installation steps will vary and Automation Anywhere does not make any warranties that these steps conform with your specific configurations.
To prepare AWS instances, do the following:

Procedure

  1. Set up the Microsoft SQL server on Amazon Web Services Elastic Compute Cloud (AWS EC2) or Relational Database Service (RDS).
    AAE supports both. For a comparison of the two, see Microsoft SQL Server on AWS.
  2. Test the database connection with the Microsoft SQL Server.
    1. Install Microsoft SQL Management Studio on one of the AWS EC2 instances inside the Virtual Private Cloud (VPC).

      For more information, see Download SQL Server Management Studio.

    2. Connect to the Microsoft SQL Server.

      For configuration information, see Microsoft SQL Server settings and service credential matrix.

    3. (Skip this step if the primary database user installs the Control Room). Create the following empty database and assign db_owner privileges to the primary database user for the Automation360-Database.
  3. Set up the shared repository.
    1. Create an AWS EC2 instance as a Windows File Server with an additional volume of 100 GB.
    2. Join the Active Directory domain.
    3. Create a folder and set up the permissions for the repository.
      Assign the Control Room admin full access to this folder.
      Important: Only the Control Room admin is to have full access to this folder because this is the account from which all Control Room services run.
  4. Launch three AWS instances, one for each Control Room server. This is because Control Room requires a minimum of three nodes to build a cluster for High Availability.
    1. Establish three AWS instances (one of each Control Room instance), each with the following configuration:
      • Type: c5.2xlarge or similar instance type (8 CPU, 16 GB RAM)
      • Storage: Root Device: 100 GB
      • Storage: Additional Device: D:\ 200 GB (For Automation Anywhere Install files)
      • Accidental Deletion Prevention: Enabled
    2. Access the three instances through Remote Desktop Protocol.
    3. Add the instances to the Active Directory domain.
    4. For each instance, add the Control Room system admin as a local administrator on the computer and reboot the system.
  5. Configure the firewall and port.
    See Ports, protocols, and firewall requirements.
  6. Set up the AWS Application Load Balancer.
    See Details for Elastic Load Balancing Products.
    • Disable the stickiness attribute.
    • Set the idle time-out to 120 seconds.
  7. Upload the SSL certificate to the Load Balancer.

What to do next

Continue with Customize Control Room installation on Amazon Web Services.