-
Notifications
You must be signed in to change notification settings - Fork 1.2k
This project requires more permissions than AmazonSageMakerFullAccess gives it #2027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Did you try granting permission for |
We added "iam:GetRole", "iam:GetRolePolicy", "sts:GetCallerIdentity" and it worked. |
@tedivm I'll resolve this issue as it appears that you have found a solution. Please reopen if needed. |
Well yeah I found a solution, but you should probably fix the underlying problem- either in the documentation or in your policies themselves. |
You also don't allow people who aren't members of this project reopen tickets. |
@tedivm good point and your right, my apologies! I didn't realize you weren't allowed to reopen it the ticket. I'll do so now. |
Apparently the issues has not been addressed yet? Please fix if it has not yet because this is an essential step and will waste so much time of all the SageMaker users. |
This prerequisite is currently identified in the following documentation: |
Describe the bug
Extremely basic code examples from the website don't work.
To reproduce
Create a new notebook with the following code:
Run it and get this error:
Expected behavior
Either the policy should be fixed, or the documentation should be upgraded to tell people what additional permissions they will need.
Screenshots or logs

System information
A description of your system. Please provide: Sagemaker Studio with no extra installs or changes.
Additional context
This problem has apparently come up before (#291 #305 #575).
We are not using a local setup for this, but are running on Sagemaker directly.
The text was updated successfully, but these errors were encountered: