AWS Config configuration changes alarm

Security & Compliance

AWS Config is a service that maintains a history of the configurations of your AWS resources and evaluates these configurations against industry best practices and your organization's internal policies. This alarm is triggered whenever configuration changes are made to AWS Config. Having visibility into the activity of your Amazon Web Services account is crucial for maintaining security and operational best practices. By using this rule to detect AWS Config configuration changes, you can prevent any accidental or intentional modifications that could result in unauthorized access or other security breaches.


When an AWS Config configuration change alarm is triggered, it means that a resource within your AWS environment has been modified in a way that violates one of the rules specified in your AWS Config rules. To remediate the issue, you can take the following steps:

  1. Identify the resource that triggered the alarm - Review the AWS Config dashboard to identify the resource that caused the alarm to be triggered. This will help you understand what has been changed and how it violates your AWS Config rules.
  2. Determine the scope of the change - Determine if the change is a result of a specific action or if it is part of a larger issue within your environment. This will help you understand the impact of the change and prioritize your response.
  3. Investigate the root cause - Investigate the root cause of the configuration change and determine why it violated your AWS Config rules. This may require reviewing logs, monitoring metrics, and speaking with stakeholders involved in the change.
  4. Roll back the change - If possible, roll back the change that caused the alarm to be triggered. This may require restoring a backup or reverting to a previous configuration.
  5. Apply a remediation action - Apply a remediation action to prevent the same issue from occurring in the future. This may involve modifying your AWS Config rules or implementing additional security controls.
  6. Monitor for recurrence - Monitor your environment for any recurrence of the issue. This may involve setting up additional monitoring or modifying your AWS Config rules.

By following these steps, you can effectively remediate an AWS Config configuration change alarm and prevent similar issues from occurring in the future.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.