<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Glue on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/aws-glue/</link><description>Recent content in Aws-Glue 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/aws-glue/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Glue Data Catalog adds OAuth 2.0 support for Iceberg REST APIs</title><link>https://curadevops.metacog.co.kr/insights/2026-10-27-aws-glue-data-catalog-now-supports-oauth-for-apache-iceberg/</link><pubDate>Tue, 27 Oct 2026 16:07:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-27-aws-glue-data-catalog-now-supports-oauth-for-apache-iceberg/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> New GA capability that changes how external query engines and partners authenticate to Glue-hosted Iceberg tables — teams running Iceberg on Glue should evaluate replacing SigV4 paths with OAuth token exchange to eliminate credential distribution to third-party analytics platforms.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> OAuth-based federated access to Iceberg tables without distributing AWS credentials is a meaningful shift in data-partnership architecture, relevant for orgs negotiating third-party analytics integrations, but no immediate strategic decision is triggered.&lt;/li>
&lt;/ul></description></item></channel></rss>