Deployment using a new Control Room
- Updated: 2025/12/02
The deployment mode 2 provides instructions for setting up an entirely new infrastructure to create, manage, and run API Task on AWS private cloud. You require two AWS accounts, one each for Control Room installation and the API Task runtime environment.
Workflow
In deployment mode 2, you must first install the Control Room in an AWS EC2 instance and then connect AWS account to the API Task on AWS account.
| Steps | Task | Description |
|---|---|---|
| 1 | Set up and install Control Room on AWS EC2 instance. | Install the Control Room on Windows EC2 instance or Linux EC2 instance based on your requirement. Both UI-based and silent mode installations are available. |
| 2 | Control Room post installation | After you install the Control Room, complete the post-installation procedures to complete the setup. |
| 3 | Deploy CloudFormation stack on the Control Room AWS account. | The api-task-controlroom-account.yaml CloudFormation template file has parameters that you must modify as per your requirements, so that an IAM role in the Control Room AWS account can assume an administrator role in the API Task AWS account. |
| 4 | Deploy CloudFormation stack on the API Task AWS. | The
api-task-controlroom-account.yaml
CloudFormation template file has parameters that you must modify as
per your requirements, so that an IAM role in the Control Room
AWS account can assume an
administrator role in the API Task
AWS account. Deploying Automation Anywhere Cloud Service on private cloud |
| 5 | Set up VPC Peering | Set up VPC peering between both AWS accounts. |
| 6 | Route table configuration in API Task AWS account. | Update the route tables of API Task
AWS to ensure that the outgoing data
traffic is routed through VPC peering. Creating route table for VPC peering in Control Room AWS account |
| 7 | Route table configuration in Control Room AWS account. | Update the route tables of the Control Room
AWS to ensure that the incoming data
traffic is routed through VPC peering. Creating route table for VPC peering in Control Room AWS account |
| 8 | Configure DNS in the Control Room AWS | Configuring DNS in the Control Room AWS enables the Control Room to download the dependencies through VPC peering using the domain names of the Control Room. |
| 9 | Connect Control Room AWS account to API Task AWS. | Connect both AWS
accounts to run API Task on AWS private
cloud. Connecting Control Room AWS account and API Tasks AWS account |