Skip to content

creating estimator with role name fails if role is default sagemaker service role #43

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

Closed
jesterhazy opened this issue Jan 14, 2018 · 1 comment · Fixed by #68
Closed

Comments

@jesterhazy
Copy link
Contributor

if you pass a role name (instead of full ARN) to estimator constructor, and you are using default role created by SageMaker, training job will fail with "unable to assume the role" ClientError:

sagemaker-mxnet-py2-cpu-2018-01-14-15-35-12-859: Failed Reason: ClientError: SageMaker was unable to assume the role 'arn:aws:iam::<ACCOUNT>:role/AmazonSageMaker-ExecutionRole-20180114T073202'

error message shows the sdk converted role name to ARN without the 'service-role' prefix. running the same job with corrected full ARN works:

arn:aws:iam::<ACCOUNT>:role/service-role/AmazonSageMaker-ExecutionRole-20180114T075260

i encountered this error starting a training job, but I assume it would impact endpoint creation in same way.

@owen-t
Copy link
Contributor

owen-t commented Jan 16, 2018

Thanks for bringing this issue to our attention. We're looking into it and will post correspondence here when we have an update.

Thanks -- Owen

laurenyu added a commit to laurenyu/sagemaker-python-sdk that referenced this issue May 31, 2018
Follow-up to aws#39, which fixed the circular dependency
apacker pushed a commit to apacker/sagemaker-python-sdk that referenced this issue Nov 15, 2018
Updated: advanced_functionality notebooks

Pushing to prepare for Monday's meeting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants