Which Aws Services Can Be Used For Event Notifcation

New – Use Amazon S3 Result Notifications with Amazon EventBridge

We launched Amazon EventBridge in mid-2019 to make it easy for you to build powerful, outcome-driven applications at any calibration. Since that launch, nosotros have added several important features including a Schema Registry, the power to Archive and Replay Events, support for Cross-Region Result Bus Targets, and API Destinations to allow you to send events to whatsoever HTTP API. With support for a very long list of destinations and the ability to do blueprint matching, filtering, and routing of events, EventBridge is an incredibly powerful and flexible architectural component.

S3 Result Notifications
Today we are making it fifty-fifty easier for y'all to utilise EventBridge to build applications that react quickly and efficiently to changes in your S3 objects. This is a new, "straight wired" model that is faster, more reliable, and more developer-friendly than ever. You no longer demand to make boosted copies of your objects or write specialized, unmarried-purpose code to process events.

At this signal you might be thinking that you already had the ability to react to changes in your S3 objects, and wondering what'southward going on here. Back in 2014 we launched S3 Event Notifications to SNS Topics, SQS Queues, and Lambda functions. This was (and still is) a very powerful feature, but using it at enterprise-scale tin can crave coordination between otherwise-contained teams and applications that share an involvement in the same objects and events. As well, EventBridge can already extract S3 API calls from CloudTrail logs and utilise them to do pattern matching & filtering. Again, very powerful and great for many kinds of apps (with a focus on auditing & logging), but we always want to do even ameliorate.

Net-net, y'all can now configure S3 Event Notifications to direct deliver to EventBridge! This new model gives you several benefits including:

Advanced Filtering – You can filter on many additional metadata fields, including object size, key name, and time range. This is more efficient than using Lambda functions that need to brand calls back to S3 to get boosted metadata in society to make decisions on the proper grade of action. S3 just publishes events that match a rule, and so y'all save money past only paying for events that are of interest to yous.

Multiple Destinations – You can road the same consequence notification to your choice of 18 AWS services including Step Functions, Kinesis Firehose, Kinesis Data Streams, and HTTP targets via API Destinations. This is a lot easier than creating your ain fan-out mechanism, and will as well help yous to deal with those enterprise-calibration situations where independent teams desire to exercise their ain issue processing.

Fast, Reliable Invocation – Patterns are matched (and targets are invoked) rapidly and directly. Because S3 provides at-least-one time delivery of events to EventBridge, your applications will be more than reliable.

Y'all can also take advantage of other EventBridge features, including the ability to archive and and so replay events. This allows you lot to reprocess events in case of an error or if you add a new target to an event bus.

Getting Started
I tin can go started in minutes. I outset by enabling EventBridge notifications on 1 of my S3 buckets (jbarr-public in this case). I open the S3 Console, find my bucket, open the Properties tab, scroll down to Event notifications, and click Edit:

I select On, click Save changes, and I'thousand ready to coil:

Now I use the EventBridge Console to create a rule. I start, as usual, by entering a name and a description:

Then I define a pattern that matches the bucket and the events of interest:

One design tin lucifer one or more buckets and one or more than events; the following events are supported:

Object Created
Object Deleted
Object Restore Initiated
Object Restore Completed
Object Restore Expired
Object Tags Added
Object Tags Deleted
Object ACL Updated
Object Storage Class Changed
Object Access Tier Changed

And so I choose the default outcome bus, and set the target to an SNS topic (BucketAction) which publishes the messages to my Amazon electronic mail address:

I click Create, and I am all set. To test it out, I simply upload some files to my bucket and await the letters:

The message contains all of the interesting and relevant data virtually the issue, and (afterward some unquoting and formatting), looks similar this:

My initial event pattern was very unproblematic, and matched only the bucket name. I tin use content-based filtering to write more complex and more interesting patterns. For case, I could utilize numeric matching to ready a design that matches events for objects that are smaller than 1 megabyte:

Or, I could utilise prefix matching to set a pattern that looks for objects uploaded to a "subfolder" (which doesn't really exist) of a saucepan:

            "object": {   "key" : [{"prefix" : "uploads/"}]   }] }

You lot can use all of this in conjunction with all of the existing EventBridge features, including Archive/Replay. You tin also admission the CloudWatch metrics for each of your rules:

Available At present
This characteristic is available now and you can showtime using it today in all commercial AWS Regions. You pay $one for every 1 one thousand thousand events that friction match a rule; check out the EventBridge Pricing page for more information.

— Jeff;