top of page

Deploy Automate+

How to sign-up and deploy AUTOMATE+ to your AWS Account(s)

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

There is also additional information on deployment requirements and troubleshooting located here:

⦿ Signup for a 6pillars SaaS account

1. Navigate to
2. Complete the sign-up form, ensuring you provide a complete phone number with the international ‎‎area code and + at the beginning of the number, for example: +61 123 456 789.
3. An email will be sent to you containing an authorisation code. Enter this code to proceed with‎‎ ‎logging in.
4. On logging in, you will be asked to input a Company or Organisation name for use within the 6pillars SaaS portal.
This name will be seen on AUTOMATE+ reports and referred to by 6pillars employees.
5. Proceed with your AWS account deployment(s) by following the steps outlined below.

⦿ Deploy AUTOMATE+ to an AWS Account - Deployment Steps

1. After creating an account for the first time you will only have the option to "Deploy to a new AWS Account".

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

2. Select your preferred deployment type:
- AUTOMATE+ to deploy the full platform (including automated remediation features) or
- AUTOMATE (the read-only version)

Note: Even with AUTOMATE+ all remediation 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.

3. 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-1

4. Select the region the AWS services that you wish to have visibility of are currently deployed into.

A new tab will open with a pre-filled CloudFormation stack (please ensure that pop-ups and new tabs are allowed within your browser at least for the portal) check the IAM acknowledgement checkbox at the bottom of the page and click Create Stack.

5. 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.

Details on the Cross Account role can be found here;

If you run into any challenges with deployment or have questions, please contact for assistance.

Deploy Automate+

bottom of page