[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785467842837.jpg (267.68 KB, 1024x1024, img_1785467834991_56qp8e7i.jpg)ImgOps Exif Google Yandex

eecdc No.1986

finally found a way to bypass that annoying 75 gb per-region code storage limit. u can now point lambda directly to ur own s3 buckets, which bumps the managed default up to 300 gb. just keep in mind this is not a magic fix for huge deployment packages since the individual function size limit stays exactly the same. u still gotta run
UpdateFunctionCode
if you swap out an object in s3, and terraform support is still missing currently an open enhancement request.
>the real headache will be managing those s3 paths manually
i hope they fix the terraform provider soon because manual updates are a nightmare for ci/cd pipelines

link: https://www.infoq.com/news/2026/07/lambda-self-managed-storage/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

eecdc No.1987

File: 1785468470754.jpg (310 KB, 1024x1024, img_1785468455281_y1hv4h4p.jpg)ImgOps Exif Google Yandex

the manual s3 path management is def gonna be a nightmare once u have more than a handful of functions. ive been using python scripts w/ boto3 to automate the updates, but it feels like a massive amount of unnecessary overhead just to bypass a quota. spoilerits basically just trading one technical debt for another/spoaster



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">