<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - multi-region - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ multi-region Articles feed</description>
    <item>
      <title>Article: Removing a Hidden Round Trip from a Multi-Region AWS API</title>
      <link>https://www.infoq.com/articles/aws-multi-region-signing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=multi-region-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/aws-multi-region-signing/en/headerimage/aws-multi-region-signing-header-1783602485181.jpg"/&gt;&lt;p&gt;When a series of regional outages forced a rethink of a multi-region AWS API, the team discovered that an obstacle to global failover was hiding in plain sight: a pre-flight discovery call baked into every client session years earlier as the only available option. This article describes what it took to remove it, and what the rollout actually cost.&lt;/p&gt; &lt;i&gt;By Suresh Gururajan&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>Resilience</category>
      <category>Low Latency</category>
      <category>AWS</category>
      <category>Authentication</category>
      <category>multi-region</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Mon, 13 Jul 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/aws-multi-region-signing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=multi-region-articles</guid>
      <dc:creator>Suresh Gururajan</dc:creator>
      <dc:date>2026-07-13T11:00:00Z</dc:date>
      <dc:identifier>/articles/aws-multi-region-signing/en</dc:identifier>
    </item>
  </channel>
</rss>
