What aspects of the notebook can be improved?
For AWS users who have already enabled Lake Formation as new data lake permission model, when creating Feature Store, it will throw "Access denied" error shown as below:
'FeatureGroupStatus': 'CreateFailed', 'FailureReason': 'Insufficient Lake Formation permission(s): Required Create Database on Catalog (Service: AWSGlue; Status Code: 400; Error Code: AccessDeniedException; Request ID: 2e3e108b-54f0-49d4-86fb-4a566cf4xxxx; Proxy: null)',
One can reproduce this issue when enable Lake Formation as default permissions for newly created databases and tables, and then run this notebook.
What are your suggestions?
Add the SageMaker execution role as Lake Formation as database creator will solve this problem.
Link to the notebook https://github.com/aws/amazon-sagemaker-examples/blob/master/end_to_end/1-data-prep-e2e.ipynb
What aspects of the notebook can be improved? For AWS users who have already enabled Lake Formation as new data lake permission model, when creating Feature Store, it will throw "Access denied" error shown as below:
'FeatureGroupStatus': 'CreateFailed', 'FailureReason': 'Insufficient Lake Formation permission(s): Required Create Database on Catalog (Service: AWSGlue; Status Code: 400; Error Code: AccessDeniedException; Request ID: 2e3e108b-54f0-49d4-86fb-4a566cf4xxxx; Proxy: null)',
One can reproduce this issue when enable Lake Formation as default permissions for newly created databases and tables, and then run this notebook.
What are your suggestions? Add the SageMaker execution role as Lake Formation as database creator will solve this problem.