2 Answers
- Newest
- Most votes
- Most comments
0
Did you ever figure this out? Running into the same issue. I was not running into this issue on an earlier domain which I had built using the quick setup option.
answered 3 months ago
0
From what I remember I had created the Sagemaker domain with the incorrect permissions setup. I deleted the domain, started again, made sure to give more access, and that solved it - sorry I can't be more specific, it was a while ago! But that's probably the problem if you used the quick setup.
answered 3 months ago
Relevant content
- asked 2 years ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago