Bug in v1.47.0 after allowing default bucket to be specified by the user

[elvinx]

@andremoeller thank you for the quick fix!
I am afraid this feature (#1168) introduced a bug :/ And now by default the SDK tries to create the bucket all the time

• I upgraded to SageMaker 1.47
• Run below lines of code

import sagemaker
role = sagemaker.get_execution_role()

• I get the below error
  ClientError: An error occurred (AccessDenied) when calling the CreateBucket operation: Access Denied

#1165

[andremoeller]

@elvinx

Thanks for reporting this! We're looking into this now.

[knakad]

While we push a revert out, I believe a workaround is to specify the session with the custom bucket name as part of the session you pass in to .get_execution_role().

i.e.:

my_session = Session(..., default_bucket="my_custom_bucket")
role = sagemaker.get_execution_role(sagemaker_session=my_session)

Alternatively, you can also downgrade to a previous version to unblock yourself.

In the meantime, we're working on a version of this fix that doesn't create the bucket on init.

[ajaykarpur]

Hi @elvinx, we've merged in the fix for this bug. We'll have a release out soon.

[ajaykarpur]

The bugfix has been released. Please feel free to reach out if you have any further questions.