OFICIAL AWS What's New

AWS Lambda now supports direct read configuration for Amazon S3 Files

What happened
Based on AWS What's New · Sep 11, 2026

AWS Lambda now allows explicit control over direct read configurations for Amazon S3 Files, enabling optimized throughput or latency based on application needs without additional cost.

AWS Lambda now supports direct read configuration for Amazon S3 Files
AWS What's New — Amazon Web Services
Key points
·
AWS Lambda now allows explicit control over direct read configurations for Amazon S3 Files
·
Direct reads can be enabled or disabled independently of function memory size via AWS tools
·
Feature is available in all AWS commercial and GovCloud Regions except three specified locations
Key numbers
·
AWS Lambda has introduced direct read configuration for Amazon S3 Files, allowing users to specify whether Lambda functions read from high-performance storage or directly from S3 buckets.
·
Previously, Lambda supported direct reads only for functions with 512 MB of memory or higher, limiting optimization flexibility.
·
When enabled, files 1 MB or larger are read directly from S3 for maximum throughput, while smaller files use high-performance storage.

AWS Lambda has introduced direct read configuration for Amazon S3 Files, allowing users to specify whether Lambda functions read from high-performance storage or directly from S3 buckets. This feature enables developers to tailor read operations to their application’s requirements, balancing throughput and latency. Previously, Lambda supported direct reads only for functions with 512 MB of memory or higher, limiting optimization flexibility. The new configuration removes this dependency, granting explicit control over read behavior regardless of memory size.

The update lets users enable or disable direct reads for S3 Files via the AWS Management Console, AWS CLI, AWS SDKs, or AWS CloudFormation. When enabled, files 1 MB or larger are read directly from S3 for maximum throughput, while smaller files use high-performance storage. Disabling direct reads routes all operations through high-performance storage for the lowest latency. This flexibility supports scalable data processing pipelines and stateful agentic workloads without compromising performance or simplicity.

The capability is available across all AWS commercial Regions, AWS GovCloud (US-East), and AWS GovCloud (US-West), excluding Asia Pacific (New Zealand), Middle East (Bahrain), and Middle East (UAE). No additional charges apply beyond standard Lambda and S3 Files pricing, ensuring cost-effectiveness for users leveraging these services. Developers can configure direct reads immediately using existing AWS tools, streamlining integration with existing workflows.

The feature aligns with AWS’s goal of optimizing performance for serverless applications by providing granular control over data access patterns. By separating high-throughput and low-latency read paths, Lambda functions can now better meet diverse workload demands while maintaining the scalability and durability of S3. Users are advised to review the AWS Lambda developer guide for implementation details and best practices.

Original source → Deals on Clipraptor.com →