<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Amazon Web Services</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Amazon Web Services feed</description>
    <item>
      <title>AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit</title>
      <link>https://www.infoq.com/news/2026/07/lambda-self-managed-storage/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Amazon+Web+Services</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/lambda-self-managed-storage/en/headerimage/generatedHeaderImage-1784880181733.jpg"/&gt;&lt;p&gt;AWS Lambda can now reference deployment packages directly in customer-owned S3 buckets, removing the per-Region code storage quota and raising the managed default from 75 GB to 300 GB. Per-function package limits are unchanged, and UpdateFunctionCode is still required after replacing an object. Terraform provider support remains an open enhancement request.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>AWS</category>
      <category>Cloud</category>
      <category>Cloud Architecture</category>
      <category>AWS Lambda</category>
      <category>S3</category>
      <category>Amazon Web Services</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Thu, 30 Jul 2026 07:57:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/lambda-self-managed-storage/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Amazon+Web+Services</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-07-30T07:57:00Z</dc:date>
      <dc:identifier>/news/2026/07/lambda-self-managed-storage/en</dc:identifier>
    </item>
    <item>
      <title>AWS Billing Bug Shows Customers Trillion-Dollar Estimates While Its Own Cost Alarms Fail to Act</title>
      <link>https://www.infoq.com/news/2026/07/aws-billing-estimates-incident/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Amazon+Web+Services</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/aws-billing-estimates-incident/en/headerimage/generatedHeaderImage-1784456911552.jpg"/&gt;&lt;p&gt;A configuration change in AWS's bill computation system showed customers estimated bills in the billions and trillions of dollars for over 24 hours. AWS's own alarms detected the anomalies but failed to halt bill generation or page engineers; customer escalations alerted the company 4.5 hours later. Budget and cost anomaly alerts were disabled platform-wide during mitigation.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>AWS</category>
      <category>Cloud</category>
      <category>Cost Optimization</category>
      <category>Site Reliability Engineering</category>
      <category>Amazon Web Services</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Wed, 22 Jul 2026 10:19:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/aws-billing-estimates-incident/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Amazon+Web+Services</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-07-22T10:19:00Z</dc:date>
      <dc:identifier>/news/2026/07/aws-billing-estimates-incident/en</dc:identifier>
    </item>
  </channel>
</rss>
