A day later and now I was able to create that S3 bucket with the specific name and builds are now persisted there. Issue resolved.
Lesson learned: it uses a fixed name that does not change (even for a new Notebook) for the S3 bucket.
Edited by: neonguru on Apr 12, 2020 8:45 AM
Should SageMaker Canvas region and S3 region be the same?Accepted Answerasked 2 months ago
Excessive Memory use when deploying PipelineModel using the pre-build Scikit container in Sagemakerasked 7 days ago
Can we run a python script in Sagemaker using boto3 from a local machine?asked 7 months ago
Uploading a Dataframe to AWS S3 Bucket from SageMakerAccepted Answerasked 3 years ago
Sagemaker - S3 bucket access when logged into us-east-1asked 5 months ago
Sagemaker python sdk installation troublesAccepted Answerasked 2 years ago
Custom Amazon SageMaker container registration and deployment trackingAccepted AnswerEXPERTasked 2 years ago
Inspection of algorithm containers for Sagemakerasked 6 months ago
Can AWS Batch jobs use SageMaker FastFile mode?asked 6 months ago
Build SageMaker container get started has missing S3 bucketasked 2 years ago