AWS v2
You can import new assets directly from your AWS by giving us restricted read access.
Import assets directly from Route53, ElasticIP, and Elastic Load Balancer by integrating with AWS.
If you're connected with AWS, Halo Security can monitor assets with dynamic IP addresses by setting an AWS Instance ID for targets. For more information, see the Scan Configuration page.
Halo Security Setup
In your Halo Security dashboard navigate to Seeds -> Connectors -> Add Connector.
Select AWS v2.
Enter your AWS account information and click Save Changes.
Keep this page open while configuring the AWS permissions.
AWS Setup
In your AWS dashboard navigate to Identity and Access Management (IAM)
Click Roles then Create role
Select AWS account
Select Another AWS account and Require external ID. Add the external ID value found in your connector settings.
Click Next
On Add permissions click Next
Add Role name:
HaloSecurity
Add Description:
Must remain in place for HaloSecurity to function correctly. Email support@halosecurity.com for assistance.
Click Create role
Select the role you just created: HaloSecurity
Under Add permissions, select Create inline policy
Click JSON and paste the custom policy provided below
Click Next
Add Policy name:
HaloSecurity
Click Create Policy
Once you've created the policy, return to the Halo Security dashboard and click Run on the connector to confirm it is working correctly.
Custom Policy JSON
Last updated