<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Notes on CloudKeep</title>
    <link>https://cloudkeep.io/notes/</link>
    <description>Recent content in Notes on CloudKeep</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 </copyright>
    <lastBuildDate>Thu, 28 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudkeep.io/notes/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Three Gotchas Connecting Google Workspace to AWS IAM Identity Center</title>
      <link>https://cloudkeep.io/notes/google-workspace-aws-iam-identity-center/</link>
      <pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://cloudkeep.io/notes/google-workspace-aws-iam-identity-center/</guid>
      <description>AWS&amp;rsquo;s docs walk you through Google Workspace + IAM Identity Center cleanly only if everything goes right. Here&amp;rsquo;s what the docs leave out — the gotchas we hit during a real migration.</description>
      
    </item>
    
    <item>
      <title>The S3 Presigned URL CORS Gotcha That Will Waste Your Afternoon</title>
      <link>https://cloudkeep.io/notes/s3-presigned-url-cors/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://cloudkeep.io/notes/s3-presigned-url-cors/</guid>
      <description>boto3 generates S3 presigned URLs with a global endpoint that 307-redirects to the regional one — without CORS headers on the redirect.</description>
      
    </item>
    
  </channel>
</rss>
