AWS Lambda adds direct read configuration for Amazon S3 Files
AWS Lambda now supports direct read configuration for Amazon S3 Files, allowing explicit control over how functions read from storage. This new capability enables developers to optimize throughput and latency for S3 file reads, choosing between high-performance storage or direct S3 bucket reads. It is designed to benefit scalable data processing pipelines and stateful agentic workloads, providing control independent of Lambda function memory size. The feature is available in most AWS commercial and GovCloud regions and can be configured via various AWS tools at no additional cost beyond standard S3 and Lambda pricing.
Features (1) ›
- Control Direct Read Configuration for S3 Files in Lambda
AWS Lambda functions can now be configured to explicitly enable or disable direct read from Amazon S3 Files. This allows optimization of file read performance based on application needs, directing reads to high-performance storage for low latency or directly from an S3 bucket for high throughput, independent of function memory size.
https://aws.amazon.com/about-aws/whats-new/2026/09/aws-lambda-direct-read-s3files/
Related releases
- SageMaker HyperPod adds model caching for faster inference autoscaling AWS What's New ·
- Amazon Bedrock Knowledge Base adds TwelveLabs Marengo 3.0 for multimodal embeddings AWS What's New ·
- AWS Lambda recursive loop detection now available in Europe Sovereign Cloud AWS What's New ·
- AWS Storage Gateway adds FIPS-compliant private connectivity for S3 File Gateway AWS What's New ·
- Amazon API Gateway now supports 1 MB execution logs with configurable delivery destinations AWS What's New ·
- Terraform AWS Provider v6.64.0 Adds New Resources and Bedrock Agent Enhancements Terraform AWS Provider Releases ·