1 Answer
- Newest
- Most votes
- Most comments
0
The problem is that Sagemaker was trying to use a sub-directory that already contained a download. Not sure how that happened. I cleared the error by creating a sub-dir in S3 and referencing that location for the data download.
Hope this helps some one.
answered 3 years ago
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago