AWS Lambda supports Amazon S3 as a failed-event destination for asynchronous and stream event sources
News
AWS Lambda has expanded its failed-event destination options to include Amazon S3 for asynchronous and stream event sources.
- Now supports S3 as a destination for failed events from Lambda functions
- Applicable to asynchronous invocations, Kinesis, and DynamoDB event source mappings
- Allows complete event payload data to be stored in S3 without custom code
- Helps resolve challenges with payload size limitations in existing destinations
- Available in all AWS Commercial Regions at no additional charge
This feature simplifies error handling and event data management for developers by providing a direct, configurable way to store failed event information in S3.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Aug 25
2025
2025
Gracefully handle failed AWS Lambda events from Amazon DynamoDB Streams
Nov 24
2025
2025
AWS Lambda announces enhanced error handling capabilities for Kafka event processing
May 30
2024
2024
AWS AppSync now supports long running events with asynchronous Lambda function invocations
Nov 14
2025
2025
AWS Lambda enhances event processing with provisioned mode for SQS event-source mapping
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.