S3 bucket needs a CORS permission

This solution breaks if the S3 bucket does not have a CORS permission. I just copied the permission JSON from https://docs.aws.amazon.com/sagemaker/latest/dg/sms-cors-update.html to make it work, but it may need more thought.

No file or test is named in the issue. Start by locating the solution's S3 bucket setup and compare its behavior without a CORS permission against the AWS SageMaker CORS guidance linked in the report; done means the solution works with the required bucket configuration documented or applied.

Written by the indexing model from the issue text.