fix(examples): correct cross-account access in LF Feature Store notebook#6048
Open
Hannah14295 wants to merge 6 commits into
Open
fix(examples): correct cross-account access in LF Feature Store notebook#6048Hannah14295 wants to merge 6 commits into
Hannah14295 wants to merge 6 commits into
Conversation
Two fixes so v3-feature-store-lake-formation-cross-account.ipynb runs
end-to-end across the three accounts:
1. Online-store PutRecord/GetRecord run as the Feature Group owner
(central account), not the producer. SageMaker Feature Store has no
cross-account resource policy for the online store, so the producer
session gets AccessDenied ('no resource-based policy allows
sagemaker:PutRecord'). Cross-account sharing is via the offline store.
2. Grant the producer account cross-account Glue Data Catalog access
before the PyIceberg write. GetTemporaryGlueTableCredentials requires
it; without it the write fails with 'Insufficient Glue permissions to
access table'. The notebook previously only granted the consumer
(and only after this write).
Hannah14295
had a problem deploying
to
manual-approval
July 17, 2026 22:31 — with 
GitHub Actions
Error
GitHub Actions
Error
Hannah14295
had a problem deploying
to
manual-approval
July 17, 2026 22:33 — with
GitHub Actions
Error
GitHub Actions
Error
added 2 commits
July 17, 2026 15:40
…/github.com/hannah14295/sagemaker-python-sdk into fix/feature-store-lf-cross-account-notebook
Hannah14295
had a problem deploying
to
manual-approval
July 17, 2026 22:41 — with
GitHub Actions
Error
GitHub Actions
Error
Hannah14295
had a problem deploying
to
manual-approval
July 17, 2026 22:46 — with
GitHub Actions
Error
GitHub Actions
Error
aviruthen
approved these changes
Jul 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two fixes so v3-feature-store-lake-formation-cross-account.ipynb runs end-to-end across the three accounts:
Online-store PutRecord/GetRecord run as the Feature Group owner (central account), not the producer. SageMaker Feature Store has no cross-account resource policy for the online store, so the producer session gets AccessDenied ('no resource-based policy allows sagemaker:PutRecord'). Cross-account sharing is via the offline store.
Grant the producer account cross-account Glue Data Catalog access before the PyIceberg write. GetTemporaryGlueTableCredentials requires it; without it the write fails with 'Insufficient Glue permissions to access table'. The notebook previously only granted the consumer (and only after this write).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.