AWS FAQ and Troubleshooting

This article contains:

Access to Us-East-1 Region

Exclude the Tenable Role from Organization Policies

An explicit deny in an SCP, RCP, or Control Tower preventive control overrides the permissions in the IAM role. The role can have every permission in the wizard and still fail. The account status stays Connected when this happens.

If you turn on EC2 Instance and AMI Scanning, Tenable creates a snapshot of each volume and attaches a copy for scanning. Exclude the role from any policy that denies these actions:

  • ec2:CreateSnapshot
  • ec2:CreateSnapshots
  • ec2:AttachVolume

Control Tower controls

Two Control Tower preventive controls deny these actions on unencrypted volumes. If you've enabled either one, add the role to its ExemptedPrincipalArns parameter.

Control What it denies
CT.EC2.PV.1: Require an Amazon EBS snapshot to be created from an encrypted EC2 volume ec2:CreateSnapshot and ec2:CreateSnapshots on unencrypted volumes
CT.EC2.PV.2: Require that an attached Amazon EBS volume is configured to encrypt data at rest ec2:AttachVolume on unencrypted volumes

For the steps to set the parameter, see Configure controls with parameters in the AWS documentation.

Custom SCPs

If you manage these policies yourself, add an ArnNotLike condition on aws:PrincipalArn to each deny statement. This example excludes the role from a deny on snapshot creation:

Copy

JSON

{
  "Sid": "DenySnapshotsOfUnencryptedVolumes",
  "Effect": "Deny",
  "Action": [
    "ec2:CreateSnapshot",
    "ec2:CreateSnapshots"
  ],
  "Resource": "arn:*:ec2:*:*:volume/*",
  "Condition": {
    "Bool": {
      "ec2:Encrypted": "false"
    },
    "ArnNotLike": {
      "aws:PrincipalArn": "arn:*:iam::*:role/TenableRole"
    }
  }
}

Do the same for any statement that denies ec2:AttachVolume.

Note: Replace TenableRole with your role name if you changed it. The * in the account field covers every account you onboard.

AWS Console Access to Account

Exclude an OU or Account from Organization

GetObject Permission for Elastic Beanstalk Buckets

Need for Both Custom Policy and SecurityAudit Policy

New AWS Services and Permissions

Update the Integration Name for the Organization

ECS Task Definitions in Inventory

Multi-Region CloudTrail

Account Status and Troubleshooting

Cloud Exposure displays a Status for each account on the Accounts > AWS page, indicating, for example, whether Tenable can connect to the account, and helping you troubleshoot potential onboarding issues.

Status Description
Access denied Cloud Exposure wasn't able to synchronize one or more resource types. Although there are various reasons why this might happen, it is likely because you need to update the Cloud Exposure read-only policy (added during account onboarding) in AWS.
Account not found
Connected Cloud Exposure successfully connected to the account, and the account is up and running.
Connected with issues

The cluster is connected, but there are specific issues that need to be addressed:

Deleting... this may take up to an hour You deleted the account in Cloud Exposure, and the process hasn't completed yet.
Disconnected There is an issue with the IAM role that you created during account onboarding to delegate permissions to Cloud Exposure. It may have been deleted, or there was a change in the trust policy that prevents Tenable from assuming the role.
Invalid permissions There is an issue with the IAM role that you created during account onboarding to delegate permissions to Cloud Exposure. Some permissions are missing. Please add the required permissions to the IAM role.
Failed to query regions Cloud Exposure was unable to query the active regions that you selected in account onboarding. One or more of the regions may be disabled. Modify the region list or add an exclusion for the IAM Role from your SCPs and RCPs. Refer to the relevant AWS documentation for more information.
Pending deletion The account is pending closure in AWS. It will eventually be deleted. Resources and findings associated with accounts pending deletion are hidden in Cloud Exposure.
Read-only policy is incorrect

The Cloud Exposure read-only policy is missing one or more of the following actions:

  • AwsCloudTrail.Actions.DescribeTrails
  • AwsCloudTrail.Actions.GetEventSelectors
  • AwsCloudTrail.Actions.GetTrail
  • AwsCloudTrail.Actions.GetTrailStatus
Suspended The account is suspended in AWS. It will eventually be deleted. Resources and findings of suspended accounts are hidden in Cloud Exposure.

CloudTrail Status

See AWS CloudTrail for more information about CloudTrail-related issues.

Status Description
Connected Analyzing CloudTrail logs
Duplicate events CloudTrail contains duplicate events. Please ensure the trail is configured correctly. This can happen if you configure multiple trails for the same account that cover overlapping event types.
Invalid CloudTrail configured Invalid CloudTrail configured. Please select a valid trail or modify its configuration.
Missing permissions Missing permissions to the CloudTrail service (cannot fetch list of trails).
Missing permissions to bucket Missing permissions to read CloudTrail events from the target S3 bucket (may belong to a different account).
Not configured CloudTrail logs aren't being analyzed. Please configure a valid trail.