You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When users are not allowed to create S3 bucket, they need to specify S3 bucket that they can access. For training, we can set output_path in estimator for specifying location for storing source code and a trained model.
However, calling estimator.deploy() repacks the source code and the trained model, and tries to upload to default bucket, named sagemaker-<region name>-<account_id>. If a user is not allowed to access the S3 bucket, SageMaker fails to deploy.
Reading model.py#L852, we need to overwrite model.bucket. Actually, the following code works, but is not easy for users.
model = estimator.create_model()
model.bucket = "accessible-bucket-name"
predictor = model.deploy(...)
Describe the solution you'd like
For estimator, output_path should be used for repacked model data. A user need not to specify the accessible bucket name again.
For create_model() or model.deploy(), an argument to specify a location for repacked model would be convenient.
The text was updated successfully, but these errors were encountered:
We actually received this as a feature request already in #1258 and I added new functionality to support this use-case =)
There are two ways you can change your code to resolve this:
(Recommended) Created your session as follows, by specifying the default_bucket that already exists (if it doesn't exist, sagemaker-python-sdk will attempt to create it for you):
Is your feature request related to a problem? Please describe.
When users are not allowed to create S3 bucket, they need to specify S3 bucket that they can access. For training, we can set
output_path
in estimator for specifying location for storing source code and a trained model.However, calling estimator.deploy() repacks the source code and the trained model, and tries to upload to default bucket, named
sagemaker-<region name>-<account_id>
. If a user is not allowed to access the S3 bucket, SageMaker fails to deploy.Reading model.py#L852, we need to overwrite
model.bucket
. Actually, the following code works, but is not easy for users.Describe the solution you'd like
output_path
should be used for repacked model data. A user need not to specify the accessible bucket name again.The text was updated successfully, but these errors were encountered: