AWS 'organization' integration
Naomi Purvis avatar
Written by Naomi Purvis
Updated over a week ago

Our AWS integration supports EC2 Elastic IP addresses or Amazon Route 53.
Any other will need to be added manually.

This feature is only available on the Premium plan

Intruder portal

There are two places you can add your AWS organization.

1a. From the Targets page. Click 'Add target' > Cloud asset sync:

1b. From the Integrations page. Click + Add under AWS:

2. Click 'AWS':

3. Click 'Add organization'

4. Download the org file and integration file from Intruder



AWS console

1. Navigate to the 'Stacks' section of your AWS console > Create stack:


2. Upload the template file provided by Intruder

3. Specify a name

4. No need to configure stack options – leave as default:

5. Acknowledge the AWS rules, by selecting this checkbox:

6. Once finished (which can take some time), copy the role ARN value:


Intruder portal

  1. Enter the role ARN you just copied from the AWS console:


AWS console

1. Navigate to 'stackset' area > click 'Create stackset':

2. Upload template file provided by Intruder (downloaded in step 4):


3. Set name:

4. Leave stackset option as default:

5. Set deployment options:

  • Deploy new stacks ☑️

  • Deploy to organization ☑️

  • Enable automatic deployment ☑️

6. Specify region:

7. Acknowledge AWS rules and click submit:


Intruder portal

1. Once it has succeeded, hit Next:

2. Configure your automation (more on Cloudbot, here) and click Connect:

3. Once Intruder has connected with AWS, you'll see one of two messages. If it's the top one, click Choose accounts; if it's the bottom one, you'll need to hit Back and review the details you input:

4. Assuming all is well, you can select which cloud accounts you'd like to add to Intruder and hit Add x accounts"

5. When you see this, click Go to organization:

6. Once the import has completed, your cloud assets tab will look like this 👇. Clicking on ... > View details will take you through to the cloud account details page:

7. On the cloud account details page, you can do a multitude of things, from target-specific actions such as adding authentication, kicking off a scan and applying a tag:

To applying account specific automation rules:


Did this answer your question?