-
Notifications
You must be signed in to change notification settings - Fork 1.2k
XGBoost estimator, security_group_ids parameter doesn't work. #2107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@dmitrybugakov Thank you for using Amazon SageMaker. Which python version do you see the bug on? |
|
Hey @dmitrybugakov, Apologies on the late response. In order to use custom security groups, you will need to also provide corresponding subnets. The Python SDK determines this during fit in this line: sagemaker-python-sdk/src/sagemaker/job.py Line 81 in e08c04e
Which ends up calling: sagemaker-python-sdk/src/sagemaker/estimator.py Line 1245 in e08c04e
This is not a nice user experience, as it should fail if the user provides one of the two required inputs. I have made note of this issue on our end. |
@ChoiByungWook thank you! |
I am seeing that the subnet and security groups do not appear in the console (even when both are set using the xgboost estimator client). Seems like there not being forwarded. If I set them manually in the console I don't get errors so I don't think it is due silent failure |
Describe the bug
I'm trying to submit a job from a local environment to Sagemaker in script mode, with custom VPC. I'm using "sagemaker.xgboost.estimator.XGBoost" and security_group_ids parameter. Job is submitted successfully, but without any changes regarding VPC, also I did notice non-errors in a log.
To reproduce
Expected behavior
There are non-errors, also as non-changes regarding VPC.
No custom VPC settings applied.
The text was updated successfully, but these errors were encountered: