Posted On: Jun 26, 2019
You can now use CloudWatch Logs to store, monitor, and analyze CloudWatch Events that are triggered in your environment.
With this new feature, when a CloudWatch Event rule is matched, log streams are created and the text from the triggered events are stored by CloudWatch Logs as log entries. For example, you can create a rule to log Amazon EC2 state-change notifications in CloudWatch Logs. You can then use CloudWatch Logs Insights to interactively search and analyze this log data. You can start using CloudWatch Logs as a CloudWatch Events target using the AWS Console, AWS CLI or SDK today. Simply create a rule, build an event pattern to match events from the AWS service of interest, and add CloudWatch Logs as a target.
Additionally, you can now assign tags to your Amazon CloudWatch Events rules. By using tags for CloudWatch Events rules you can better track CloudWatch Events rules usage or costs by application, environment or department. You activate these tags on the AWS Billing and Cost Management dashboard and AWS uses the tags to categorize your costs and deliver a monthly cost allocation report to you. You can also use tags for access control by granting a user permission to access or change only rules with certain tag values. You can start tagging your CloudWatch Events rules using the AWS CLI or SDK today.
Both features are available in all AWS public regions including GovCloud. For more information, please visit the CloudWatch Events Documentation.