s3

DuckLake spec 1 shipped on 13 April 2026 and keeps lake metadata in a SQL database. DuckDB's architecture note puts Iceberg planning at about 100 ms per sequential S3 GET, roughly half a second before a query starts. On AWS, stay on S3 Tables when Athena, Glue, or Redshift must read the table.

On July 16, 2026 AWS removed the 30-day Standard residency gate for Standard-IA and One Zone-IA lifecycle transitions — day-0 IA can cut first-month storage ~46% on 10 TB cold logs, but the 30-day IA billing minimum and $0.01/GB retrieval fees still apply.

As of July 2026, Lambda S3 Files still mounts S3 as POSIX via NFS — roughly S3 Standard storage rates vs EFS for large files — but versioning is required, IAM is s3files:*, capacity providers are incompatible, and a ~60s write-back window breaks naive ports.

AWS CLI v2 #10196 chmod'd streaming outputs to 0600 — including /dev/null. July 2026 retrospective: #10215 revert, host repair, pin-and-canary checklist.

AWS publishes every price publicly, yet bills still surprise teams in 2026. Costs emerge from service interactions — now including Bedrock/AgentCore — not from any single rate card.

S3 storage is still cheap in July 2026. Request storms, unmanaged versioning, CRR, Express One Zone, and S3 Tables compaction choices are what blow the bill — not GB-month alone.

S3 misconfigurations are still the leading cause of headline data breaches. Bucket policies, encryption, access logging, Block Public Access, and the practices that keep "developer left the bucket public" from being your incident.