Automation Anywhere now supports running API Task on AWS private cloud. This capability enables organizations to leverage secure and scalable infrastructure while maintaining full control over their automation workloads. This capability is designed for organizations that require private hosting to maintain data sovereignty, enhanced security, meet compliance standards, and achieve low-latency performance.

Overview

The API Task on AWS private cloud feature enables you to deploy API Task within your own AWS infrastructure. Deploying API Tasks in AWS private cloud ensures that the sensitive and critical data remain within the network perimeter of the organization. The organizations can control the cloud resources, scaling, and manage security controls based on their business needs.

Architecture

The architecture includes Control Room deployed on AWS EC2 instance and API Tasks infrastructure set up on another AWS account. Both accounts are connected through VPC peering ensuring that the data transaction occurs in real-time with low-latency during the automation runtime. All the current API Tasks workflows are available in AWS private cloud setup. For more information about architecture, see API Task on AWS private cloud architecture.

Note: API Tasks on AWS VPC supports AWS private cloud only. If your environment is on AWS public cloud, you cannot set up and run API Tasks on AWS public cloud.

With API Task on AWS private cloud, you can

Downloads

Download the following files from A-People Downloads page (Login required) for setting up API Tasks on AWS private cloud account.
File Description
api-task-onprem-infra.zip

This zip contains api-task-onprem.yaml and api-task-controlroom-account.yaml files.

The api-task-onprem.yaml is the AWS CloudFormation template that you must run on the API Task AWS account. It creates the EKS cluster, helm charts, and all necessary IAM permissions.
The api-task-controlroom-account.yaml is the AWS CloudFormation template you must run on the Control Room AWS Account. It creates an instance profile that you must manually attach to the Control Room instance.
Automation360_Build_<build-number>.zip The zip file contains the Automation 360 on-prem installer that is applicable for API Tasks in AWS.