You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the bug/Issue
gc06_check_encryption_at_rest_part2 lambda function is finding OpenSearch domains in accounts even if they were deleted and flagging them as non-compliant.
Resources that are affected
OpenSearch and ElasticSearch domains
Screenshots
In the following screenshot, we can see that there is only on OpenSearch domain
But in AWS config, we can see that we have another one marked as non-compliant, even though this one was already deleted
Current behavior
In the gc06_check_encryption_at_rest_part2 lambda function, doesn't find the deleted domain. But its showing up in the aws config.
Expected behavior
To report on the actual resources that are present in the account and exclude older resources that no longer exist.
Additional context
Originally reported in the old repo
The text was updated successfully, but these errors were encountered:
Description of the bug/Issue
gc06_check_encryption_at_rest_part2 lambda function is finding OpenSearch domains in accounts even if they were deleted and flagging them as non-compliant.
Resources that are affected
OpenSearch and ElasticSearch domains
Screenshots
In the following screenshot, we can see that there is only on OpenSearch domain
But in AWS config, we can see that we have another one marked as non-compliant, even though this one was already deleted
Current behavior
In the gc06_check_encryption_at_rest_part2 lambda function, doesn't find the deleted domain. But its showing up in the aws config.
Expected behavior
To report on the actual resources that are present in the account and exclude older resources that no longer exist.
Additional context
Originally reported in the old repo
The text was updated successfully, but these errors were encountered: