Customize Control Room installation on Amazon Web Services
Install and apply the customized configuration required for the Control Room cluster on Amazon Web Services (AWS) after completing initial preparations.
- Login to the first AWS instance as an Administrator.
- Click Next on the Welcome to the Setup Wizard page.
- Accept the licensing agreement and click Next.
Select the Custom option and click
The Destination Folder page appears. By default, the destination folder is C:\Program Files\Automation Anywhere\Enterprise\.
To make changes to the destination folder, click Change,
enter a new destination folder name, and click OK.
Recommendation: Do not install the application directly in the root directory (C:\). You should create a folder, for example, C:\Program Files\Automation Anywhere\Enterprise\.
- Click Next to configure the IP cluster.
Select the Enable Cluster Setup check
The check box is enabled by default if the machine on which the setup is being run has local IP addresses configured.To install the Control Room on a single node and not a cluster, clear the Enable Cluster Setup check box.
Enter the IP addresses of the nodes in the cluster.
Use a comma (,) to specify more than one IP address.
For example, to specify three IP addresses in the cluster, enter: 192.0.2.1,192.0.2.2,192.0.2.3Important: The first IP address in the list is used as the master node. Ensure that you enter the IP addresses in the same order on all node configurations in subsequent installations. An incorrect order causes the application to configure the IP addresses as separate clusters, which will result in data loss when the issue is fixed after installation.You can install multiple nodes at the same time after the master node is initially installed.After installation, you can add a new IP address to the cluster at the end of the list.
- After you enter the cluster IP addresses correctly, select a valid address IP at the message prompt to provide network access to the machine.
- Use a comma (,) to specify more than one IP address.
- Click Next to configure the application Transport Layer Security (TLS).
In the TLS Configuration page, configure the
- Generate a Self-Signed Certificate
Enabling the Self-Signed Certificate option allows the installer to generate a unique private key and a self-signed certificate for the Control Room.
- Import a Certificate
To import a custom certificate, clear the Self Signed Certificate check box. This setting allows you to import a certificate using the Certificate Path field.Note: The certificate file must be a PKCS12 format.Provide the following information:
- Certificate Path: Click Browse to import the certificate.
- Private Key Password: Enter the password for
the private key. Password limitation: Do not use the at sign (@) in passwords. Using the special character @ in the password causes the certificate file import to fail.
- Webserver Port: Enter the web server port –
either HTTP or HTTPS. If the port is already assigned, an error
message is displayed.Attention: The port validation message is also displayed when you add 8080 for the web server and if that port is already in use for a Control Room license service. Use a different unassigned port in these cases.
- Enable Force HTTP traffic to HTTPS: This
option redirects all HTTP port requests to HTTPS. To access to the
Control Room through HTTPS using the generated
self-signed certificate, ensure the port numbers are different for
HTTP and HTTPS. To generate a custom certificate for HTTPS, ensure your custom certificate meets the following:
- Create a .pfx certificate with a pass code from a CA trusted authority.
- Combine Root, Intermediate, and Machine level certificates into a single certificate.
- Use the format [WS Machine Host Name].[DomainName].com for the private key.
- Include the host name as a fully qualified domain name
(FQDN) in the certificate.
You provide the host name during Control Room installation.
- In multi-node HA clusters, issue certificates to the load balancer DNS name.
- Add individual URLs, which require access to all nodes, to the Subject Alternative Name field in the certificate.
For more information, see Automation Anywhere support site: Automation 360 On-Premises prerequisites (A-People login required).
- Generate a Self-Signed Certificate
- Click Next to configure the service credentials.
In the Service Credentials screen, choose from the listed
The Windows Service credentials include a user name and password. The user specified must meet these requirements:
- A member of the local system administrator group.
- Have permission to manage services, including Automation Anywhere services.
- If you use Windows authentication to connect to the SQL database, ensure
you grant the
db_ownerpermission to the service credential user.
These service credentials allow the Control Room processes to run the required services.
- Local System Account—(default) The logged-on user performing the installation
- Domain Account—Specify a user that
is not the local system account user
- Clear the Local System Account check box.
- Enter the user name and password for the domain account.
Use only supported characters for the user name and password. See Supported special characters.
- Do not use the Windows domain credentials
Enter credentials valid for running Automation Anywhere services. Without the valid credentials, the Control Room will fail to launch.
- PowerShell script restrictions
Specify a user with permissions to launch PowerShell scripts who is not a Windows domain user. Without the relevant permissions, database table creation can fail.
Add the SQL Server and click Next.
Select Microsoft SQL Server, type the Name, and click Next.
On the InstallShield Wizard Completed page, click
Launch Automation Anywhere is enabled by default.Enable Show installer settings to open the aae-installsummary.html file. By default, this is located at C:\Program Files\Automation Anywhere\Enterprise\. Use this file to view a summary of the installation.