Skip to content

A log metric filter and alarm does not exist for AWS Config configuration changes

Description

Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs and establishing corresponding metric filters and alarms. Monitoring changes to AWS Config configuration will help ensure sustained visibility of configuration items within the AWS account.

We recommend you establish a log metric filter and alarm for detecting changes to AWS Config configurations.

Fix - Runtime

Procedure

To setup the metric filter, alarm, SNS topic, and subscription, follow these steps and commands:

  1. Determine the CloudTrail log group name to monitor. 
aws cloudtrail describe-trails

Look for the field CloudWatchLogsLogGroupArn. Your log group name comes after the log-group field. For example:

arn:aws:logs:us-west-2:123456789012:log-group:aws-cloudtrail-logs-123456789012-68a4172e:*

If you don't see the field CloudWatchLogsLogGroupArn in your output, your CloudTrail is not setup to ship logs to CloudTrail. Please follow the AWS Documentation for sending CloudTrail events to CloudWatch logs.
2. Create a metric filter based on filter pattern provided which checks for AWS Configuration changes and the \ taken from step 1.

aws logs put-metric-filter 
--log-group-name <cloudtrail_log_group_name> 
--filter-name <aws_config_changes_metric> 
--metric-transformationsmetricName= <aws_config_changes_metric>,
        metricNamespace='CISBenchmark',metricValue=1 
--filter-pattern '{($.eventSource = config.amazonaws.com) &&
        (($.eventName=StopConfigurationRecorder)||($.eventName=DeleteDeliveryChannel)|| 
        ($.eventName=PutDeliveryChannel)||($.eventName=PutConfigurationRecorder))}'

📘 Note

You can choose your own metricName and metricNamespace strings. Using the same metric Namespace for all Foundations Benchmark metrics will group them together.

  1. Create an SNS topic that the alarm will notify.
aws sns create-topic --name <sns_topic_name>

📘 Note

You can execute this command once and then re-use the same topic for all monitoring alarms.

  1. Create an SNS subscription to topic created in Step 2.
aws sns subscribe 
--topic-arn <sns_topic_arn> 
--protocol <protocol_for_sns> 
--notification-endpoint <sns_subscription_endpoints>

📘 Note

You can execute this command once and then re-use the SNS subscription for all monitoring alarms.

  1. Create an alarm that is associated with the CloudWatch Logs Metric Filter created in Step 1 and an SNS topic created in Step 2.
aws cloudwatch put-metric-alarm 
--alarm-name <aws_config_changes_alarm>
--metric-name <aws_config_changes_metric>
--statistic Sum 
--period 300 
--threshold 1 
--comparison-operator GreaterThanOrEqualToThreshold 
--evaluationperiods 1 
--namespace 'CISBenchmark' 
--alarm-actions <sns_topic_arn>

Fix - Buildtime

Resource: aws_cloudwatch_log_metric_filter, aws_cloudwatch_metric_alarm

```go aws_cloudwatch_metric_alarm.config_change.tf resource "aws_sns_topic" "trail-unauthorised" { name="Unauthorised" kms_master_key_id = "alias/aws/sns" }

resource "aws_sns_topic_subscription" "sms" { topic_arn = aws_sns_topic.trail-unauthorised.arn protocol = "sms" endpoint=var.endpoint }

resource "aws_cloudwatch_metric_alarm" "config_change" { alarm_name = "aws_config_changes_alarm" comparison_operator = "GreaterThanOrEqualToThreshold" evaluation_periods = 1 metric_name = "aws_config_changes_metric" namespace = "CISBenchmark" period = 300 statistic = "Sum" threshold = 1 alarm_actions = [aws_sns_topic.trail-unauthorised.arn] }

resource "aws_cloudwatch_log_metric_filter" "config_change" { name = "aws_config_changes_metric" pattern = "{($.eventSource = config.amazonaws.com) && (($.eventName=StopConfigurationRecorder)||($.eventName=DeleteDeliveryChannel)|| ($.eventName=PutDeliveryChannel)||($.eventName=PutConfigurationRecorder))}" log_group_name = var.log_group_name

metric_transformation { name = "aws_config_changes_metric" namespace = "CISBenchmark" value = "1" } } ```