Description
When using SageMaker Feature Store in a cross-account setup, create_dataset() fails because it assumes the Glue database name returned from the Feature Group description is directly usable in the consumer account.
In cross-account architectures, this assumption breaks.
Details
- Feature Groups are owned in a source account
- Offline store is accessed from a consumer account via a shared Glue database
- The Feature Group description returns the database name from the source account
- The shared Glue database name in the consumer account is different
- create_dataset() retrieves the database name directly from the Feature Group description without any way to override or remap it:
As a result, create_dataset() queries a database that does not exist in the consumer account.
Expected behavior
The SDK should support cross-account Feature Store usage by allowing:
- A database name override, or
- A mapping mechanism for shared Glue databases