The AWS CloudFormation stack provisions the resources needed to run Automation Anywhere Cloud Service in an AWS private cloud and creates an instance profile you must attach to the EC2 instance.

Use the CloudFormation template to enter your parameters and deploy a stack that creates an instance profile granting the Control Room instance the IAM permissions required to communicate with the Automation Anywhere Cloud Service cluster.

Prerequisites

Ensure that you download the Automation Anywhere Cloud Service CloudFormation template file from A-People portal (A-People Downloads page (Login required)).

Procedure

  1. Log in to the AWS console.
  2. Go to the CloudFormation console, and click Create stack.
  3. Configure the following parameters in the Create stack page:
    1. Select Choose an existing template in Prerequisite - Prepare template section.
    2. Select Upload a template file, and click Choose file in Specify template section
    3. Select the downloaded CloudFormation template file and click Next.
      The uploaded file automatically generates the S3 URL.
  4. Click Next to proceed to the Specify stack details page.
  5. Configure the following parameters in the Specify stack details page.
    1. Enter api-task-onprem in Stack name.
      The stack name is hardcoded and cannot be renamed later.
    2. Enter the ID of the VPC in which you are setting up Automation Anywhere Cloud Service in ExistingVpcId.
    3. Enter the ID of the internet gateway attached to the VPC in InternetGatewayId.
      If the VPC is a non-default VPC, create, attach an internet gateway to the VPC and enter the ID in this field.
    4. Enter the existing IPv4 CIDR block of the VPC settings in ControlRoomSubnetsCidr.
    5. Enter the IPv4 CIDR block that you created in the VPC settings in AACSSubnetsCidr.
    6. Enter a CIDR block for AWS Elastic Kubernetes Service (EKS) in KubernetesServiceCidr.
      Ensure that this CIDR block does not overlap with AACSSubnetsCidr or ControlRoomSubnetsCidr. You can enter the default 172.20.0.0/16 CIDR block if it does not overlap with other CIDR blocks.
    7. Enter the domain name that you configured in Setting up domain names for Control Room in AACSDomainName.
    8. Enter the ARN number of the certificate provisioned from AWS Certificate Manager in CertificateArn.
    9. Optional: Select false in EnableGaiServices.
      Automation Anywhere Cloud Service in AWS private cloud does not currently support the generative AI features.
    10. Optional: Enter a custom domain name to access Control Room for REST API calls in CRDomainName.
    11. Optional: Enter 0 in ReservedCapacityPodCount.
      This parameter allows you to reserve additional AWS resources for the EKS to lower the latency. The default value is 0. You can increase this value per your requirements.
    12. Optional: Enter true in Release38CompatibilityMode if you are setting up Automation Anywhere Cloud Service in Automation 360 version 38.
      For other versions, enter false.
    13. Optional: By default, public.ecr.aws/r3y6m7m6 is set as the repository for helm charts in Repository.
      Change this file path to your private repository only in the unlikely scenario of the Automation Anywhere Cloud Service helm charts files are available in a private repository.
  6. Click Next to proceed to the Configure stack options page.
  7. Configure the following parameters in Configure stack options page:
    1. Select Preserve successfully provisioned resources in the Stack failure options section.
      The Preserve successfully provisioned resources option enables you to debug and troubleshoot in case of any deployment failures.
      Note: The Use deletion policy option is the default selection in Delete newly created resources during a rollback.
    2. Select the I acknowledge that AWS CloudFormation might create IAM resources with custom names check box, and click Next .
  8. Review the details of the CloudFormation template, and then click Submit.
    CloudFormation starts to create the stack
The Stacks dashboard of the CloudFormation console displays the new stack.

Ten minutes after the stack deploys successfully, a HelmInstallerInstance EC2 instance starts spinning up and installs the helm charts. This EC2 instance shuts down if the helm charts are installed successfully, you can proceed to launch the EC2 instance for the Control Room. If this EC2 instance is still available on the console after ten minutes, the installation has failed and you must recreate the stack.

Next steps

After CloudFormation creates the stack, you can launch an EC2 instance in which you install the Control Room. The CloudFormation stack creates an instance profile named aacs-profile-[AWS-REGION]. The [AWS-REGION] is the AWS VPC region. This profile grants appropriate IAM permissions to the EC2 instance for communicating with the Automation Anywhere Cloud Service resources. You must attach this profile to the EC2 instance when you launch it.