Event: Account does not exist or incorrect permissions
The following are common issues when working with AWS cloud connections:Cause: AWS Account no longer exists
Cause: AWS Account no longer exists
Solution: If the account no longer exists, the connection can be deleted using the Public Cloud Connection Wizard. See Deleting a Connection.
Cause: Account exists, but has incorrect permissions
Cause: Account exists, but has incorrect permissions
Solution: Ensure the Minimum Permissions for CloudWatch Data Collection are set correctly.Once the permissions have been corrected, you can verify the connection using the Public Cloud Connection Wizard. See Reviewing a Connection.
Cause: Account exists, but is configured incorrectly
Cause: Account exists, but is configured incorrectly
Solution:Ensure the AWS Data Collection Prerequisites for an IAM Role are setup correctly, Including that the External ID you have entered corresponds to the correct IAM Role.Once the prerequisites and credentials have been corrected, you can verify the connection using the Public Cloud Connection Wizard. See Reviewing a Connection.
Cause: Systems within the AWS account are not supported
Cause: Systems within the AWS account are not supported
Solution: If your account only contains services that Densify does not analyze, then the audit will fail. i.e. DynamoDB, Redshift, Lambda, ElasticCache, etc.Within Densify you need to manually delete the Cloud Environments associated with these accounts.