Automation 360 On-Premises prerequisites

Determine whether the system has the required hardware and software to install Control Room for Automation 360 On-Premises.

Hardware requirements

Control Room server requirements
The Control Room is deployed on servers in data centers. The minimum Automation Anywhere hardware requirements include: server type, machine type, processor, RAM, disk storage, and network requirements.
Operating system, environment, and platform supported for Control Room
Automation 360 can be hosted on AWS, Microsoft Azure, Google Cloud Platform, IBM, and any public, private, or hybrid cloud service that meets the Control Room and Bot Agent hardware and software requirements.
Bot Agent compatibility
Bot Agent is the Automation 360 plug-in that enables you to create and run bots. The agent is installed on devices used to access the Control Room. Installing the Bot Agent is part of registering a device.
Credential requirements
Login credentials are required at different stages of Automation Anywhere deployment and use. Credentials are required for installation and data center servers, access to Automation Anywhere components, and to run tools in bots.
Supported cloud platforms
Review the supported cloud platforms for various Automation 360 features.

Data center requirements

Database requirements
Working with SQL Servers
Configure Microsoft SQL Servers before setting up the Control Room database.
Working with Azure SQL PaaS
Using PaaS SQL database with Azure requires configuration from the Azure instance.
Load balancer requirements
View the load balancer requirements for Automation Anywhere installation. This includes load balancer minimum requirements, and both TCP and HTTPS layer load balancing requirements.
Ports, protocols, and firewall requirements
View the default and configurable firewall, port, and protocol requirements for Automation Anywhere deployment.
Browser requirements for Automation Workspace
The user interface for Automation 360 (On-Premises or Cloud deployed) and for Community Edition is accessible through a browser.
HA and DR deployment models
High availability deployment
The high availability (HA) deployment model provides failure tolerance for the Control Room servers, services, and databases using a distributed load balancer.
Disaster recovery deployment
The disaster recovery (DR) deployment model uses high availability (HA) clusters distributed across separate geographic areas.
Single-node deployment
A single-node deployment hosts the Control Room only on one server or machine.

Trusted URLs

To ensure secure access to Automation 360 online services for On-Premises deployments, add the service-specific URL to the safe recipients or trusted list.

Add service URLs to trusted list for On-Premises.

Additional requirements

Configure application Transport Layer Security
Use the Transport Layer Security (TLS) configuration wizard page from the Automation 360 installer to generate a self-signed certificate or import a security certificate to set up a highly secure Control Room instance.
Naming guidelines for Control Room URLs
When configuring your domain and subdomain Control Room URLs, you must follow the Domain Name System (DNS) guidelines.

See also this article on the Automation Anywhere support site: Automation 360 On-Premises prerequisites (A-People login required).