API Tasks on AWS private cloud supports two deployment modes. You can either use an existing Control Room deployed on AWS private cloud or deploy an entirely new setup.

  1. Mode 1 - Using an existing Control Room.
  2. Mode 2 - Using a new Control Room.

For more information about the requirements for each mode, see Prerequisites.

Mode 1 - Deployment using an existing Control Room

The deployment mode 1 enables you to use a Control Room that is already deployed in an AWS EC2 instance. You can use a Control Room that is deployed on either Windows EC2 instance or Linux EC2. You can configure this Control Room for connecting it to the API Tasks AWS account. Once you complete the configuration, you can set up the API Tasks AWS account.

After setting up both the AWS accounts, you must establish a VPC peering connection with cross-account DNS configuration. For more information about the workflow of this deployment mode, see Deployment using an existing Control Room

Mode 2 - Deployment using a new Control Room

The deployment 2 enables you to set up an entirely new infrastructure. You require two AWS accounts, one each for Control Room installation and for running API Task.

You must first install a Control Room on a Windows or Linux EC2 instance. You can then set up the API Task AWS account. The Control Room installer enables you to install the Control Room in an EC2 instance within your AWS private cloud environment. The installer provides an option to bind your AWS account to the installed Control Room and start the Automation Anywhere Cloud Service automatically.

After setting up both the AWS accounts, you must establish a VPC peering connection with cross-account DNS configuration. For more information about the workflow of this deployment mode, see Deployment using a new Control Room