Posted On: Dec 6, 2021
You can now build event-driven applications using Amazon S3 Event Notifications that trigger when objects are transitioned or expired (deleted) with S3 Lifecycle, or moved within the S3 Intelligent-Tiering storage class to its Archive Access or Deep Archive Access tiers. You can also trigger S3 Event Notifications for any changes to object tags or Access Control Lists (ACLs). You can generate these new notifications for your entire bucket, or for a subset of your objects using prefixes or suffixes, and choose to deliver them to Amazon EventBridge, Amazon SNS, Amazon SQS, or an Amazon Lambda function.
S3 Event Notifications for S3 Lifecycle and S3 Intelligent-Tiering actions can be used for a wide range of automated workflow use cases. For instance, you can automatically update your Amazon DynamoDB tables, AWS Glue Data Catalogs, or media asset managers to track whether your data, per your S3 Lifecycle configuration, has transitioned into a storage class with retrieval times of minutes or hours, or been expired. In addition, you can now use S3 Event Notifications for changes in object tags to build applications that invoke an AWS Lambda function to resize images.
These new Amazon S3 Event Notifications are now available in all Amazon Web Services Regions, including the Amazon Web Services China (Beijing) Region operated by Sinnet, and the Amazon Web Services China (Ningxia) Region operated by NWCD. You can configure Amazon S3 Event Notifications in the Amazon Web Services Management Console or with an API request. To learn more, visit the S3 User Guide.
These new Amazon S3 Event Notifications are now available in all Amazon Web Services Regions, including the Amazon Web Services China (Beijing) Region operated by Sinnet, and the Amazon Web Services China (Ningxia) Region operated by NWCD. You can configure Amazon S3 Event Notifications in the Amazon Web Services Management Console or with an API request. To learn more, visit the S3 User Guide.
Note: Amazon Web Services services generate events that invoke Lambda functions, and Lambda functions can send messages to Amazon Web Services services. To avoid infinite loops, we recommend care to ensure that Lambda functions do not invoke services or APIs in a way that trigger another invocation of that function.