Why the docs still uses "CloudWatch Event" even th...
# aws
Why the docs still uses "CloudWatch Event" even tho that got renamed "EventBridge" ages ago?
Also, no EventBridge Scheduler integration?
As I understand it, a part of CloudWatch because EventBridge years ago, but not the whole thing. It was "CloudWatch Events" that was renamed to "EventBridge", not the entire "CloudWatch" suite of services. I'm a bit fuzzy, but AWS currently uses "CloudWatch" to describe some of the monitoring sources, and "EventBridge" to describe the AWS service that sends various events, including CloudWatch events, around the place. I think this means that when something happens in your EC2 instance that needs to be recorded, CloudWatch generates an event (alarm) and records it. CloudTrail gets its events directly from there, but every other consumer of CloudWatch events is notified of them via the EventBridge service. More info here: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-cwe-now-eb.html https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-and-eventbridge.html
No, a CloudWatch Event Rule is not the same as EventBridge Scheduler. Even tho they can be used to achieve the same thing, Scheduler is much more powerful for some use-cases. It's also a way more recent service (GA at Re:Invent 2022).