<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - AWS - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ AWS News feed</description>
    <item>
      <title>AWS Introduces Free Sandbox Environments for Workshops</title>
      <link>https://www.infoq.com/news/2026/08/aws-builder-sandbox/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/aws-builder-sandbox/en/headerimage/generatedHeaderImage-1783889777241.jpg"/&gt;&lt;p&gt;AWS Builder Center now offers free, time-limited sandbox environments for workshops, so developers no longer need to use their own AWS account and credit card or worry about unexpected charges. This has been a long-standing request from the community and removes one of the biggest friction points for practitioners learning new AWS technologies.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Training / Certification</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Cloud Adoption</category>
      <category>Workshop</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 01 Aug 2026 04:49:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/aws-builder-sandbox/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-08-01T04:49:00Z</dc:date>
      <dc:identifier>/news/2026/08/aws-builder-sandbox/en</dc:identifier>
    </item>
    <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=AWS-news</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>S3</category>
      <category>AWS Lambda</category>
      <category>Cloud Architecture</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Amazon Web Services</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=AWS-news</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 Launches Amazon GuardDuty Investigation Agent to Automate Threat Triage</title>
      <link>https://www.infoq.com/news/2026/07/guardduty-investigation-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/guardduty-investigation-agent/en/headerimage/generatedHeaderImage-1784791165676.jpg"/&gt;&lt;p&gt;AWS released a public preview of the GuardDuty investigation agent, which correlates findings, 90-day activity logs, and resource topologies into structured reports with risk ratings, confidence scores, and MITRE ATT&amp;CK classification. It is reachable through the AWS MCP Server, so investigations can run from agentic tooling. Preview quotas cap usage at 10 investigations per account per day.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>AI Architecture</category>
      <category>Cloud</category>
      <category>Information Security</category>
      <category>AWS</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Tue, 28 Jul 2026 07:14:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/guardduty-investigation-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-07-28T07:14:00Z</dc:date>
      <dc:identifier>/news/2026/07/guardduty-investigation-agent/en</dc:identifier>
    </item>
    <item>
      <title>Amazon EKS Adds Kubernetes Version Rollback within 7 Days of an Upgrade</title>
      <link>https://www.infoq.com/news/2026/07/eks-version-rollback/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/eks-version-rollback/en/headerimage/generatedHeaderImage-1783696042627.jpg"/&gt;&lt;p&gt;Amazon EKS has recently introduced support for Kubernetes version rollbacks, letting practitioners revert a cluster's control plane to its previous Kubernetes version within 7 days of an upgrade if issues arise. The feature reduces the risk of in-place cluster upgrades by giving teams a safety net to recover quickly from problematic updates.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Kubernetes</category>
      <category>Cloud Computing</category>
      <category>ECS - Compute</category>
      <category>Containers</category>
      <category>Cloud Native Architecture</category>
      <category>AWS</category>
      <category>Kubernetes Operator</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sun, 26 Jul 2026 06:04:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/eks-version-rollback/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-07-26T06:04:00Z</dc:date>
      <dc:identifier>/news/2026/07/eks-version-rollback/en</dc:identifier>
    </item>
    <item>
      <title>How Zalando Built an In-Process Client-Side Load Balancer for One Million Requests per Second</title>
      <link>https://www.infoq.com/news/2026/07/client-side-load-balancer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/client-side-load-balancer/en/headerimage/generatedHeaderImage-1783270035162.jpg"/&gt;&lt;p&gt;The engineering team at Zalando recently described the design and implementation of an in-process, client-side load balancer for a high-throughput API handling around 1 million requests per second. The result was more predictable latency, a drop in infrastructure costs, and better visibility into where failures actually originate.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Kubernetes</category>
      <category>Load Balancers</category>
      <category>Load Balancing</category>
      <category>AWS</category>
      <category>Performance &amp; Scalability</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Sat, 25 Jul 2026 06:43:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/client-side-load-balancer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-07-25T06:43:00Z</dc:date>
      <dc:identifier>/news/2026/07/client-side-load-balancer/en</dc:identifier>
    </item>
    <item>
      <title>Achieving Compliance as a Platform Engineering Team by Helping Developers</title>
      <link>https://www.infoq.com/news/2026/07/platform-that-helps-developers/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/platform-that-helps-developers/en/headerimage/header-1784099869567.jpg"/&gt;&lt;p&gt;When a new platform team set out to implement their roadmap through forced workflows with poor documentation, developer experience declined. Success came from simplifying governance, prioritizing what mattered, and rolling out compliance incrementally through prevention, detection, and communication. Empathy, focus, and shared purpose drove successful adoption.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Governance</category>
      <category>Communication</category>
      <category>Developer Experience</category>
      <category>Collaboration</category>
      <category>InfoQ Dev Summit Munich 2025</category>
      <category>AWS</category>
      <category>Platforms</category>
      <category>Change</category>
      <category>InfoQ Dev Summit</category>
      <category>Roadmap</category>
      <category>Platform Engineering</category>
      <category>Development</category>
      <category>Culture &amp; Methods</category>
      <category>news</category>
      <pubDate>Thu, 23 Jul 2026 11:42:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/platform-that-helps-developers/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-07-23T11:42:00Z</dc:date>
      <dc:identifier>/news/2026/07/platform-that-helps-developers/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=AWS-news</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>Site Reliability Engineering</category>
      <category>Cloud</category>
      <category>Cost Optimization</category>
      <category>AWS</category>
      <category>Amazon Web Services</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=AWS-news</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>
