<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/a0cebc3b4a0f4ff7a77b1e36a3326bf6&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a0cebc3b4a0f4ff7a77b1e36a3326bf6-a28acdcb392de1ec.gif</thumbnail_url><duration>298.496</duration><title>Mastering Cross-Region S3 Replication and KMS Key Management</title><description>In this video, I walk you through a lab where we built a cross-region replication setup for critical data stored in S3, ensuring protection even if an entire AWS region goes down. We created two S3 buckets in U.S. East and U.S. West, set up automatic replication, and implemented KMS with customer-managed keys for encryption. I encountered some challenges, particularly with versioning and KMS key policies, which I resolved by ensuring the replication rule had the correct permissions. Overall, I highly recommend exploring cross-region replication, especially focusing on getting the KMS key policies right. If you&apos;re working with multiple regions, pay close attention to these details!</description></oembed>