I am a Team Lead/Sr. DevOps Consultant in the Amazon Web Services Professional Services division. This article is my own work using publicly available information and does not necessarily reflect the opinions of my employer.
CloudWatch becomes an essential part of understanding what is happening within our infrastructure and application, both during development and production. CloudWatch is an integral part of observability.
Sometimes things don’t behave as planned, and we want to take action when specific events occur. This article describes a scenario and how using CloudWatch Subscription filters takes additional measures when such an event occurs.
What are CloudWatch Subscription Filters
CloudWatch logs contain the information written to the log file by an AWS service or your code. Sometimes, we want to take a specific action when a particular log entry occurs. Subscription filters provide a real-time stream of log data that can be sent to an
- Amazon Kinesis stream;
- Amazon Kinesis Firehose stream; or,
- an AWS Lambda function.
The subscription filter allows us to send specific log events to the desired destination based upon a filter pattern. This means we can detect different events…
