Installing Control Room on Amazon Web Services
Login to an Amazon Web Services (AWS) server instance as Administrator. Then download and start the Control Room installer and select Custom mode.
Automation 360 supports Amazon Workspace cloud license and bring your own license (BYOL).
For Automation 360 to work properly on Amazon Workspace, update the registry on all Workspace machines by performing the following:
- Go to C:\Windows\System32\drivers.
- Rename the spacedeskHookKmode.sys file to spacedeskHookKmode.sys.old.
- Restart the machine.
- In Task Manager, verify the
STXHD Hosted Application Serviceis not running.
For more information, see Troubleshooting Amazon WorkSpaces issues
- Step 1: Prepare for installation
- Verify Automation 360 On-Premises prerequisites.
- Ensure that you have the following:
- Automation Anywhere Control Room installation file
- TLS certificate
- License file
- Step 2: Prepare for installation on Amazon Web Services
- Use these steps to prepare the Amazon Web Services (AWS) instances for the Control Room installation.
- Step 3: 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.
- Step 4: Complete Control Room configuration and validation.
- Complete Control Room post-installation configuration
- After installing the Control Room, complete the configuration settings to ensure timely Automation Anywhere communications are specified and confirm Automation Anywhere services are running.
- Post-installation user management
- After completing the post-installation tasks, validate the setup by logging in to the Control Room and installing a license. First time access to the Control Room walks you through the configuration for your authentication method.
- Step 5: Prepare for users.
- Manage users
- As a Cloud user with administrator permissions, you can create, view, edit, delete, and enable or disable a user. Creating users steps vary depending on whether the user is a non-Active Directory, Active Directory, or single sign-on (SSO) user from an IdP server.