Solution: If the account no longer exists, the connection can be deleted using the Public Cloud Connection Wizard. See Deleting a Connection.

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.

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.

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.