<?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>Amazon CloudWatch Omni Extends CloudWatch into the Agent Era</title>
      <link>https://www.infoq.com/news/2026/09/aws-cloudwatchomni-observability/?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/09/aws-cloudwatchomni-observability/en/headerimage/aws-reliability-dns-1790708319178.jpg"/&gt;&lt;p&gt;Recently launched, Amazon CloudWatch Omni is an AI-first observability platform designed to monitor, evaluate, and troubleshoot applications and autonomous AI agents in a unified environment.&lt;/p&gt; &lt;i&gt;By Sergio De Simone&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Agents</category>
      <category>Observability</category>
      <category>Performance Evaluation</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Tue, 29 Sep 2026 19:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/aws-cloudwatchomni-observability/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Sergio De Simone</dc:creator>
      <dc:date>2026-09-29T19:00:00Z</dc:date>
      <dc:identifier>/news/2026/09/aws-cloudwatchomni-observability/en</dc:identifier>
    </item>
    <item>
      <title>AWS Introduces Foreign Key Constraints in Aurora DSQL</title>
      <link>https://www.infoq.com/news/2026/09/aurora-dsql-foreign-keys/?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/09/aurora-dsql-foreign-keys/en/headerimage/generatedHeaderImage-1788260510964.jpg"/&gt;&lt;p&gt;AWS recently announced that Aurora DSQL now supports foreign key constraints, allowing applications to enforce referential integrity directly in the database, including CASCADE, SET NULL, and other referential actions. The addition addresses a long-standing gap that users had explicitly called out as an adoption blocker.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Relational Databases</category>
      <category>Distributed Data</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Database</category>
      <category>Postgres</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 28 Sep 2026 04:54:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/aurora-dsql-foreign-keys/?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-09-28T04:54:00Z</dc:date>
      <dc:identifier>/news/2026/09/aurora-dsql-foreign-keys/en</dc:identifier>
    </item>
    <item>
      <title>Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments</title>
      <link>https://www.infoq.com/news/2026/09/aws-stateless-mcp/?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/09/aws-stateless-mcp/en/headerimage/generatedHeaderImage-1788807776891.jpg"/&gt;&lt;p&gt;AWS details how the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. The change enables independent request routing and simpler horizontal scaling while shifting application state, retries, observability, and idempotency concerns to other layers.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Deployment</category>
      <category>Scaling</category>
      <category>Load Balancing</category>
      <category>OpenTelemetry</category>
      <category>Distributed Systems</category>
      <category>AWS Lambda</category>
      <category>AWS</category>
      <category>Serverless</category>
      <category>Microservices</category>
      <category>Observability</category>
      <category>W3C</category>
      <category>Frameworks</category>
      <category>AI Architecture</category>
      <category>Model Context Protocol (MCP)</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 25 Sep 2026 12:58:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/aws-stateless-mcp/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-09-25T12:58:00Z</dc:date>
      <dc:identifier>/news/2026/09/aws-stateless-mcp/en</dc:identifier>
    </item>
    <item>
      <title>Elastic Beanstalk Adds Cluster Mode, Running Applications on Shared EKS Clusters</title>
      <link>https://www.infoq.com/news/2026/09/elastic-beanstalk-cluster-eks/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;AWS has added Cluster Mode to Elastic Beanstalk, running applications on EKS clusters the service creates and operates. Clusters are assigned by subnet set and cannot be changed afterward, direct cluster access is service-managed, and AWS recommends separate clusters for untrusted or regulated workloads. The mode adds EKS and Auto Mode fees that EC2 discounts do not reduce.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Containers</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Cost Optimization</category>
      <category>Platform Engineering</category>
      <category>Kubernetes</category>
      <category>Architecture</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 23 Sep 2026 06:44:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/elastic-beanstalk-cluster-eks/?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-09-23T06:44:00Z</dc:date>
      <dc:identifier>/news/2026/09/elastic-beanstalk-cluster-eks/en</dc:identifier>
    </item>
    <item>
      <title>AWS Cannot Restore Data Held Only in Damaged Middle East Availability Zones</title>
      <link>https://www.infoq.com/news/2026/09/aws-middle-east-data-loss/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS-news</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;AWS has told customers it cannot restore resources and data hosted exclusively in the mec1-az2 availability zone in the UAE, or exclusively in the Bahrain region, after damage during the conflict with Iran. The company says the Bahrain damage spanned multiple availability zones and exceeded what its regional and multi-AZ services are designed to withstand.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Reliability</category>
      <category>Compliance</category>
      <category>Fault Tolerance</category>
      <category>Infrastructure</category>
      <category>Architecture</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 21 Sep 2026 08:43:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/aws-middle-east-data-loss/?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-09-21T08:43:00Z</dc:date>
      <dc:identifier>/news/2026/09/aws-middle-east-data-loss/en</dc:identifier>
    </item>
    <item>
      <title>AWS Lambda Pushes Serverless toward Long-Running Workloads</title>
      <link>https://www.infoq.com/news/2026/09/lambda-90-minute-timeout/?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/09/lambda-90-minute-timeout/en/headerimage/generatedHeaderImage-1789110995851.jpg"/&gt;&lt;p&gt;AWS Lambda now allows functions running on Lambda Managed Instances to run for up to 90 minutes, six times longer than the previous 15-minute limit, further blurring the line between a Lambda invocation and a traditional server. The limit remains unchanged for traditional synchronous requests.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>AWS Lambda</category>
      <category>AWS</category>
      <category>Serverless</category>
      <category>Event Driven Architecture</category>
      <category>Cloud Computing</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Sat, 19 Sep 2026 09:11:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/lambda-90-minute-timeout/?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-09-19T09:11:00Z</dc:date>
      <dc:identifier>/news/2026/09/lambda-90-minute-timeout/en</dc:identifier>
    </item>
  </channel>
</rss>
