How to deploy AUTOMATE+ for the first time

To deploy AUTOMATE+ to your AWS Account, please follow the steps below.
If you run into any issues during the process, please contact support@6pillars.ai for assistance.

Deploy AUTOMATE+ to your first AWS Account - Deployment Steps

Open your preferred browser and log into the appropriate AWS account corrresponding with the intended AUTOMATE or AUTOMATE+ deployment.

Ensure you do not have any other AWS Accounts open, make sure you close all other browser windows that contain active logins to additional AWS accounts.

After creating an account for the first time you will only have the option to "Deploy to a new AWS Account" or use the Template Scanner listed under “IaC”.

Ensure you are logged in to the AWS account with the appropriate IAM user and that the IAM role has sufficient privledges to deploy AUTOMATE LIGHT, AUTOMATE READ ONLY or AUTOMATE+.

If you are returning to the portal to deploy an additional account, you will find deployment option under "Settings", “Accounts” as part of the main quickbar at the top of the screen inside the SaaS portal after you have logged in, "Deploy to AWS Account"

Select your preferred deployment type:

AUTOMATED DEPLOYMENT METHODS - EASY TO USE, QUICK

• AUTOMATE LIGHT (one time snapshot of findings)

• AUTOMATE (the read-only version)

Name your deployment, we recommend provide a name with a sequence that easily helps you understand which accounts you have connected when looking at them in a list. Otherwise when you look at your accounts in a list later with just the AWS account numbers and no easy reference, its unlikely to mean much to you in the future. For example: Orgname-Prod1-AuditAccount-1

Be sure to select the correct AWS region.

A new tab will open with a pre-filled CloudFormation stack check the IAM acknowledgement checkbox at the bottom of the page and click Create Stack.

• AUTOMATE+ to deploy the full platform (including Continuous Compliance - fix misconfigurations and enforce compliance)

With AUTOMATE+ all remediation/continuous compliance features are deployed to a read-only / alert-only state.

NO AUTOMATION IS TRIGGERED at time of deployment, auto-remediation needs to be enabled/configured by you.

Hardening the Cross Account role

The final (automated) step of the deployment process is to harden the Cross-Account role, at this time all permissions are reduced to the minimum requirement.

AWS Cross Account Role & AWS IAM role requirements.

MANUAL DEPLOYMENT METHODS - for advanced users, self install of CloudFormation Template, a few more steps, takes longer, more visibility of CloudFormation template and process

Instructions can be found here:

ADVANCED (MANUAL) DEPLOYMENT - AUTOMATE READ ONLY

If you run into any challenges with deployment or have questions, please contact support@6pillars.ai for assistance.