Amazon S3

AWS Transform's .NET modernization agent can now automatically convert application code that uses Azure Blob Storage into equivalent code using Amazon S3, as part of a broader Azure SDK to AWS SDK conversion capability. The tool discovers Azure service usage in submitted source code, presents conversion options in an assessment report, and validates that the converted code correctly calls AWS SDK methods after modernization runs.

Matters for: Teams migrating Azure cloud-native .NET applications that rely on Azure Blob Storage to run on AWS infrastructure.

AWS Security Hub can now export findings on demand from any findings page (Threats, Exposure, Vulnerabilities, Posture Management, Sensitive Data, All Findings) directly to an S3 bucket in your account, in either CSV or JSON (OCSF) format, without building a custom extraction pipeline. This capability is available in all AWS Regions where Security Hub operates.

Matters for: Security teams needing findings outside the console for compliance reporting and audit evidence.

You can now explicitly enable or disable direct read for S3 Files on Lambda functions, independent of function memory size, whereas previously direct reads from your S3 bucket only worked automatically for functions with 512 MB of memory or higher. When enabled, files 1 MB or larger read directly from your S3 bucket for maximum throughput while smaller files are served from high-performance storage; when disabled, all reads use high-performance storage for lowest latency.

Matters for: Teams building scalable data processing pipelines and stateful agentic workloads on Lambda that need to tune file read latency versus throughput for large file operations.

Amazon Bedrock Managed Knowledge Base now lets you configure automatic daily, weekly, or monthly sync schedules for data sources including Amazon S3, instead of requiring manual sync triggers or custom scheduling code. This is not a breaking change, so existing S3-backed knowledge bases continue to work without modification while gaining the option to enable scheduled syncing.

Matters for: Teams using S3 as a reference document store for retrieval-augmented generation applications built on Amazon Bedrock Knowledge Bases.

Coding agents like Claude Code and Kiro can now use the AWS MCP Server's serverless capability to inspect Lambda functions and their connected resources, including Amazon S3, correlating error signals, retrieving deployed configurations, and analyzing latency across the connection. This diagnostic data is gathered in a single call rather than through multiple separate API calls, reducing token consumption for the agent.

Matters for: Teams running Lambda functions that use S3 as an event source or connected resource, who need to troubleshoot errors or latency issues across that integration.