1 Answer
- Newest
- Most votes
- Most comments
0
I found the root cause. I had to go to "Trust relationship" section of the IAM role and then add "sagemaker.amazonaws.com" to the service principal.
answered 5 years ago
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
