-
Notifications
You must be signed in to change notification settings - Fork 24
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
Access to vhive-tuning S3 bucket denied. #336
Comments
@jingren1021 thank you for reporting the issue. In fact, we should allow vSwarm users to configure their own buckets to avoid high bills to our side (except for the inputs). @shyamjesal are the S3 buckets for ephemeral transfers all hardcoded, do you know? |
Yes, they are hardcoded currently. |
@jingren1021 would you be able to contribute a fix? if you agree, we would try to help you find the LoC where the values are hardcoded |
I have created a pull request on this. Please review #341 . Thank you very much. Edit: I was working on my forked repository and some unwanted changes were added to pull request #338 . I have undone the unwanted changes and created a new pull request. Please review #341 . |
This has been fixed. |
I was trying to run Hyperparameter Tuning Halving benchmark and came across this issue where my access to vhive-tuning S3 bucket is denied.
Kubectl logs as follow:
I have exported AWS_ACCESS_KEY and AWS_SECRET_KEY environment variables and is able to run video analytics benchmark without issue. Is the public access to vhive-tuning S3 bucket denied by default or is it some issue with my setting on AWS account?
Thank you very much.
The text was updated successfully, but these errors were encountered: