Stax identified inconsistencies in rule evaluations in the Compliance module following upgrades performed on Friday 22 September. This upgrade caused inconsistent results for the following rules:
* Ensure a log metric filter and alarm exist for AWS Config configuration changes * Ensure a log metric filter and alarm exist for AWS Management Console authentication failures * Ensure a log metric filter and alarm exist for Management Console sign-in without MFA * Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL) * Ensure a log metric filter and alarm exist for changes to network gateways * Ensure a log metric filter and alarm exist for CloudTrail configuration changes * Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer-created CMKs * Ensure a log metric filter and alarm exist for IAM policy changes * Ensure a log metric filter and alarm exist for route table changes * Ensure a log metric filter and alarm exist for S3 bucket policy changes * Ensure a log metric filter and alarm exist for security group changes * Ensure a log metric filter and alarm exist for unauthorized API calls * Ensure a log metric filter and alarm exist for unauthorized API calls (version 2) * Ensure a log metric filter and alarm exist for usage of root user credentials * Ensure a log metric filter and alarm exist for VPC changes * Ensure a log metric filter and alarm exists for AWS Organizations changes
The upgrades were successfully rolled back on Saturday 23 September.