<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Unity Catalog External Location with Amazon S3 Access Points,session policy behavior and workarounds in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/unity-catalog-external-location-with-amazon-s3-access-points/m-p/160296#M54880</link>
    <description>&lt;P&gt;&lt;SPAN class=""&gt;Context&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm working on integration patterns between enterprise NAS storage (Amazon FSx for NetApp ONTAP) and Databricks via S3 Access Points. S3 Access Points provide S3 API access to file data without copying — a common pattern for organizations with existing NFS/SMB workloads.&lt;/P&gt;&lt;P&gt;I've documented my findings publicly here:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A target="_blank" rel="noopener noreferrer"&gt;https://github.com/Yoshiki0705/fsxn-lakehouse-integrations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;What I've observed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When registering an S3 Access Point as a UC External Location:&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Yes: External Location creation succeeds&lt;/LI&gt;&lt;LI&gt;Yes: Top-level file listing works&lt;/LI&gt;&lt;LI&gt;Yes: Explicit file reads (specifying full path) work&lt;/LI&gt;&lt;LI&gt;No: Subdirectory listing fails with&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;UC_CLOUD_STORAGE_ACCESS_FAILURE&lt;/LI&gt;&lt;LI&gt;No: CREATE TABLE fails with&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;AccessDenied&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The behavior suggests the session policy generated during AssumeRole doesn't correctly handle S3 AP ARN format (arn:aws:s3:REGION:ACCOUNT:accesspoint/NAME).&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Technical details&lt;/SPAN&gt;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Databricks on AWS, Premium tier&lt;/LI&gt;&lt;LI&gt;Unity Catalog enabled&lt;/LI&gt;&lt;LI&gt;Storage Credential: IAM Role with full s3:* on the AP ARN&lt;/LI&gt;&lt;LI&gt;S3 AP type: Internet-origin (same as what works with Athena/Snowflake/EMR)&lt;/LI&gt;&lt;LI&gt;The same data is queryable via Athena, Snowflake External Stage, and EMR Serverless without issues&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN class=""&gt;Questions for the community&lt;/SPAN&gt;&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;&lt;P&gt;Has anyone successfully registered an S3 Access Point (not a standard S3 bucket) as a UC External Location? If so, what configuration was needed?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is there a documented limitation or roadmap item for S3 AP support in UC? I couldn't find this in the current documentation.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;For those using the Storage Ecosystem partners (announced at DAIS 2026) — does the native integration bypass this limitation by using a different registration path?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN class=""&gt;Current workaround&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm currently using DataSync → standard S3 bucket → UC External Location, which works but introduces data copy. For read-only analytics, Athena and Snowflake can query the S3 AP directly, so this is specifically a UC limitation.&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Why this matters to the community&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Many organizations store data on enterprise NAS (NFS/SMB) and want to use Databricks for ML/AI without duplicating everything to S3. S3 Access Points are designed exactly for this "access without copy" pattern. If UC could support S3 AP ARNs, it would enable zero-copy governed analytics on enterprise file storage — benefiting anyone with NAS-resident data.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Environment: Databricks on AWS, ap-northeast-1, Premium tier, DBR 16.1+&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jun 2026 19:49:20 GMT</pubDate>
    <dc:creator>YoshikiFujiwara</dc:creator>
    <dc:date>2026-06-23T19:49:20Z</dc:date>
    <item>
      <title>Unity Catalog External Location with Amazon S3 Access Points,session policy behavior and workarounds</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-external-location-with-amazon-s3-access-points/m-p/160296#M54880</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;Context&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm working on integration patterns between enterprise NAS storage (Amazon FSx for NetApp ONTAP) and Databricks via S3 Access Points. S3 Access Points provide S3 API access to file data without copying — a common pattern for organizations with existing NFS/SMB workloads.&lt;/P&gt;&lt;P&gt;I've documented my findings publicly here:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A target="_blank" rel="noopener noreferrer"&gt;https://github.com/Yoshiki0705/fsxn-lakehouse-integrations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;What I've observed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When registering an S3 Access Point as a UC External Location:&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Yes: External Location creation succeeds&lt;/LI&gt;&lt;LI&gt;Yes: Top-level file listing works&lt;/LI&gt;&lt;LI&gt;Yes: Explicit file reads (specifying full path) work&lt;/LI&gt;&lt;LI&gt;No: Subdirectory listing fails with&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;UC_CLOUD_STORAGE_ACCESS_FAILURE&lt;/LI&gt;&lt;LI&gt;No: CREATE TABLE fails with&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;AccessDenied&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The behavior suggests the session policy generated during AssumeRole doesn't correctly handle S3 AP ARN format (arn:aws:s3:REGION:ACCOUNT:accesspoint/NAME).&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Technical details&lt;/SPAN&gt;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Databricks on AWS, Premium tier&lt;/LI&gt;&lt;LI&gt;Unity Catalog enabled&lt;/LI&gt;&lt;LI&gt;Storage Credential: IAM Role with full s3:* on the AP ARN&lt;/LI&gt;&lt;LI&gt;S3 AP type: Internet-origin (same as what works with Athena/Snowflake/EMR)&lt;/LI&gt;&lt;LI&gt;The same data is queryable via Athena, Snowflake External Stage, and EMR Serverless without issues&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN class=""&gt;Questions for the community&lt;/SPAN&gt;&lt;/P&gt;&lt;OL class=""&gt;&lt;LI&gt;&lt;P&gt;Has anyone successfully registered an S3 Access Point (not a standard S3 bucket) as a UC External Location? If so, what configuration was needed?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is there a documented limitation or roadmap item for S3 AP support in UC? I couldn't find this in the current documentation.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;For those using the Storage Ecosystem partners (announced at DAIS 2026) — does the native integration bypass this limitation by using a different registration path?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN class=""&gt;Current workaround&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm currently using DataSync → standard S3 bucket → UC External Location, which works but introduces data copy. For read-only analytics, Athena and Snowflake can query the S3 AP directly, so this is specifically a UC limitation.&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Why this matters to the community&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Many organizations store data on enterprise NAS (NFS/SMB) and want to use Databricks for ML/AI without duplicating everything to S3. S3 Access Points are designed exactly for this "access without copy" pattern. If UC could support S3 AP ARNs, it would enable zero-copy governed analytics on enterprise file storage — benefiting anyone with NAS-resident data.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Environment: Databricks on AWS, ap-northeast-1, Premium tier, DBR 16.1+&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2026 19:49:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-external-location-with-amazon-s3-access-points/m-p/160296#M54880</guid>
      <dc:creator>YoshikiFujiwara</dc:creator>
      <dc:date>2026-06-23T19:49:20Z</dc:date>
    </item>
  </channel>
</rss>

