<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cross-Region on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/cross-region/</link><description>Recent content in Cross-Region on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:07:53 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/cross-region/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS IAM Identity Center adds cross-Region trusted identity propagation</title><link>https://curadevops.metacog.co.kr/insights/2026-10-27-aws-iam-identity-center-now-supports-cross-region-trusted-id/</link><pubDate>Tue, 27 Oct 2026 16:07:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-27-aws-iam-identity-center-now-supports-cross-region-trusted-id/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This GA capability removes the need for overly broad IAM roles in multi-Region architectures, enabling per-user fine-grained access control and audit trails across Regions. Teams running distributed or disaster-recovery workloads on AWS should evaluate updating their IAM Identity Center configuration and multi-Region access patterns this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Cross-Region identity propagation tightens the audit and access-control story for multi-Region AWS deployments without additional cost, which may eventually inform golden-path standards for identity architecture, but no strategic decision is required now.&lt;/li>
&lt;/ul></description></item></channel></rss>