<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>S3 on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/s3/</link><description>Recent content in S3 on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 27 Aug 2026 20:52:16 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/s3/index.xml" rel="self" type="application/rss+xml"/><item><title>Mountpoint for Amazon S3 adds configurable memory usage controls</title><link>https://curadevops.metacog.co.kr/insights/2026-08-27-mountpoint-for-amazon-s3-adds-memory-usage-controls/</link><pubDate>Thu, 27 Aug 2026 20:52:16 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-27-mountpoint-for-amazon-s3-adds-memory-usage-controls/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you run Mountpoint in EKS or other memory-constrained environments, upgrading to the latest release lets you set explicit memory targets or rely on automatic container-limit detection, preventing the expansion-over-time instability that previously competed with ML or analytics workloads. No deadline, but worth scheduling as a planned upgrade this quarter if Mountpoint is in your stack.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>CloudFront OAC now supports S3 Multi-Region Access Points natively</title><link>https://curadevops.metacog.co.kr/insights/2026-08-21-amazon-cloudfront-now-supports-origin-access-control-oac-for/</link><pubDate>Fri, 21 Aug 2026 11:18:28 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-21-amazon-cloudfront-now-supports-origin-access-control-oac-for/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you use S3 MRAP with CloudFront, you can now drop the Lambda@Edge workaround for SigV4a signing and let CloudFront handle OAC natively — plan to migrate existing custom auth header functions to simplify the architecture.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS Lambda adds self-managed S3 code storage, raises default limit to 300GB</title><link>https://curadevops.metacog.co.kr/insights/2026-07-15-aws-lambda-announces-self-managed-code-storage/</link><pubDate>Wed, 15 Jul 2026 12:10:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-15-aws-lambda-announces-self-managed-code-storage/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This GA capability removes the per-Region Lambda-managed storage quota for teams running large function/layer footprints; evaluate adopting &lt;code>S3ObjectStorageMode=REFERENCE&lt;/code> this quarter for deployments approaching the old 75GB ceiling, and note the default limit has already been raised to 300GB for all accounts.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Cost impact is neutral-to-positive (standard S3 rates replace implicit Lambda storage overhead) with no forced migration, but worth flagging to platform teams running high function counts so they can evaluate whether S3-backed storage fits their existing artifact management posture.&lt;/li>
&lt;/ul></description></item></channel></rss>