DNS Cutover: TTL Planning and the Rollback Window Nobody Sizes Properly

Lowering your TTL 48 hours ahead is the easy part of a DNS cutover. The hard part is the cache layers that never honored your TTL at all, and the rollback window that closes the moment the new origin takes its first write. Here is how to plan both, and what to do with the old origin the second you flip.

Continue ReadingDNS Cutover: TTL Planning and the Rollback Window Nobody Sizes Properly

Serving Millions of Images From S3 Without public-read

A public S3 object gives every viewer a second path to your bytes, one that skips your cache, ignores your headers and bills on a different rate card. Here is how to serve S3 images without public-read at scale: origin access control, the bucket policy condition that matters, the 403-versus-404 trap that turns missing thumbnails into origin load, and cache design that survives millions of objects.

Continue ReadingServing Millions of Images From S3 Without public-read