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 Enterprise plan
Step 1 - Navigate to Intruder Portal
There are three places you can add your AWS organization from within the Intruder Portal:
1a. From the Targets page. Click the Discovery tab and select '+ Add Asset Source':
1b. From the Integrations page. Click + Add under AWS:
1c. The Targets page by clicking the yellow + Add Targets button > Cloud asset sync:
2. Click 'AWS':
3. Click 'Add organization'
4. Download the org file and integration file from Intruder
Step 2 - Create Stack in 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. Review the stack details, scroll to the bottom and click the 'Submit' button.
7. Once finished (which can take some time), copy the role ARN value:
Step 3 - Enter Role ARN in Intruder Portal
Enter the role ARN you just copied from the AWS console:
Step 4 - Create a StackSet in AWS Console
1. Navigate to the 'StackSets' area > click 'Create StackSet':
2. Upload template file provided by Intruder (downloaded in step 4):
3. Set name:
4. Leave the StackSet options as default and check the Capabilities acknowledgement:
5. Set deployment options:
Deploy new stacks ☑️
Deploy to organization ☑️
Enable automatic deployment ☑️
6. Select "Add all regions" (bottom left of the highlighted area):
7. Confirm the configuration and click the submit button:
If you encounter the message "Cloud account Prod has invalid credentials...' within Intruder, please confirm that the enabled regions in your AWS account match the regions where the CloudFormation stack will be deployed.
Step 5 - Add Asset in Intruder portal
1. Once it has succeeded, hit 'Add asset ->':
2. Once Intruder has connected with AWS, you'll see one of two messages. If it's the top one, click 'Go to organization ->'. If it's the bottom one, you'll need to hit <- Back and review the integration configuration:
4. After clicking 'Go to organization ->', you'll see your AWS organization:
5. Once the import has completed, your Discovery page will look something like this:
Clicking on ... > View details will take you through to the cloud account details page:
7. On each cloud account details page, you can do a multitude of things for each target, such as adding authentication methods, kicking off a scan, and applying a tag:
Clicking on the 'Sync rules' and 'Integration settings' in the top right will display account-specific options such as the ability to apply selective sync rules (only import targets matching a specific condition), or automatically kick off scans when changes are detected:
