The AWS Connector provides real-time visibility and inventory of EC2 assets in AWS accounts. The AWS connector refreshes every 30 minutes. The licensing implications are as follows:
- Assets discovered through the connector do not count against the license until and unless the asset is scanned for vulnerabilities. Discovery through the connector is free.
- Assets discovered through the connector that did become licensed fall off the license the day after Cloudtrail shows the asset was terminated. This is an event that can be observed via the AWS connector.
Note: Because Tenable retains the asset vulnerability data for 15 months, the instance may still appear on your dashboard after termination.
Configure the AWS Connector
To configure AWS to support Tenable.io connectors via role delegation (keyless):
- In Tenable.io, record the External ID from the AWS connector pane.Note: The external ID is the same as the container ID.
- In your AWS account, create a role named tenableio-connector to delegate permissions to an IAM user, as described in the Amazon AWS documentation.
In the navigation pane of the console, click Roles > Create role.
For role type, click Another AWS account.
- For Account ID, type the ID 012615275169.Note:012615275169 is the account ID of the Tenable AWS account that you will be establishing a trust relationship with to support AWS role delegation (keyless authentication).
Select the Require external ID checkbox, and type the External ID (Tenable container ID) that was recorded in Step 1.
- Click Next: Permissions.
- Create or reuse a policy with the following permissions:
AWS Service Permission Amazon EC2
Tenable recommends that you set Amazon Resource Name to * (all resources) for each AWS Service.
Click Next: Tagging.
- (Optional) Add any desired tags.
Click Next: Review.
- In the Role name box, type tenableio-connector.Caution: The role must be named tenableio-connector for the connector to work.
Review the role, ensuring that the role name is tenableio-connector, and then click Create role.
What to do next:
See the AWS Connector Configuration Instructions for more information on configuring the connector.
Note: It is recommended that the customer create a new account just for Nessus which is restricted to read only access when scanning AWS web services.