-
Notifications
You must be signed in to change notification settings - Fork 860
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
Failed to download and register model using s3 presigned v4 url #669
Comments
@vishal-wiai: I was able to successfully register a model using an s3 pre-signed v4 URL. Note: I had to replace |
Yes thank you @harshbafna . It worked after encoding As a feature request, is it possible for TorchServe to do this encoding, under the hood? |
It works when you only provide the |
@vishal-wiai Can you provide the HTTPs URL alongwith the parameters you are using? |
This is the way an HTTP request works, where the parameters supplied in the URL using
You only need to encode the Example
|
@harshbafna CURL did work for me but using
|
@vishal-wiai: This seems to be a problem with the A simple approach would be URL formation through string concatenation:
Reference: psf/requests#1454 (comment) |
I tried all of the techniques suggested above but still could not get torchserve to download the model from s3 presigned url.
When I send this url as part of the POST request to register the model:
I get back a Any pointers would be appreciated. |
@dotel-saramsz : Are you able to download the mar file with a simple curl/wget command using this pre-signed-URL? |
@harshbafna Yes, I am able to download with a simple curl command using the pre-signed url |
@dotel-saramsz @harshbafna Was this issue resolved? I am facing a similar problem right now. This is what my code snippet looks like:
A simple get on the presigned uri is working but the model management API throws an error. I tried doing all the recommended things like replacing & with %26, etc. but nothing seems to work. |
I'm using management API to register a model with a HTTPs URL. It is a s3 presigned url. Torchserve successfully downloads and registers models from s3 v2 signature URLs but fails to download for v4 signature types. Is there any bug to it?
I checked this behaviour with 3 of the models and also verified URL permissions. Using
requests.get()
I'm able to download but not on TorchServe.The text was updated successfully, but these errors were encountered: