Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Interoperability with AWS Snowball #10458

Closed
cyberduck opened this issue Sep 11, 2018 · 9 comments
Closed

Interoperability with AWS Snowball #10458

cyberduck opened this issue Sep 11, 2018 · 9 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
6.8.0

Comments

@cyberduck
Copy link
Collaborator

28e9291 created the issue

Hello,

I am hoping to use Cyberduck to provide users access to AWS Snowball devices. I have begun testing using the "generic S3 profile" available here: https://trac.cyberduck.io/wiki/help/en/howto/s3#GenericS3profiles

Cyberduck is able to connect to S3 endpoint on the Snowball device, but there are errors when attempting to write data. I have attached a screenshot.

Reads from Snowball to local directories works fine, so it feels we are close!

I am able to put a single file to Snowball via Cyberduck, but writing multiple files or a directory fails with the attached screenshot.

Please let me know if any additional information is needed. I would like to be able to suggest Cyberduck to our customers using Snowball.

I have attached the debug log from system.log. Any help is appreciated.

Thanks!

David Green
AWS
greendm@amazon.com

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> PUT /mpp-goodbyestranger-sync/cyberduck/snowball2/ HTTP/1.1
5821	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Date: Tue, 11 Sep 2018 21:00:15 GMT
5822	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Expect: 100-continue
5823	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Content-Type: application/x-directory
5824	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
5825	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Host: 10.34.16.1
5826	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> x-amz-date: 20180911T210015Z
5827	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Authorization: AWS4-HMAC-SHA256 Credential=65DY3OLJ0NQLG327O1OK/20180911/us-east-1/s3/aws4_request,SignedHeaders=content-type;date;host;x-amz-content-sha256;x-amz-date,Signature=0129b6b6a4925f60005397b3fcda9be7adf62f729b18f8231ca2ed1b25c3761a
5828	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Content-Length: 0
5829	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> Connection: Keep-Alive
5830	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 >> User-Agent: Cyberduck/6.7.1.28683 (Mac OS X/10.13.3) (x86_64)
5831	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << HTTP/1.1 100 Continue
5832	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << Server: AmazonSnowball
5833	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << Keep-Alive: timeout=89
5834	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << HTTP/1.1 201 Created
5835	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << Content-Type: text/plain; charset=utf-8
5836	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << Content-Length: 0
5837	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << ETag: "d41d8cd98f00b204e9800998ecf8427e"
5838	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << Server: AmazonSnowball
5839	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.apache.http.headers - http-outgoing-9 << Keep-Alive: timeout=89
5840	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) INFO  ch.cyberduck.transcript.response - HTTP/1.1 201 Created
5841	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) INFO  ch.cyberduck.transcript.response - Content-Type: text/plain; charset=utf-8
5842	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) INFO  ch.cyberduck.transcript.response - Content-Length: 0
5843	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) INFO  ch.cyberduck.transcript.response - ETag: "d41d8cd98f00b204e9800998ecf8427e"
5844	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) INFO  ch.cyberduck.transcript.response - Server: AmazonSnowball
5845	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) INFO  ch.cyberduck.transcript.response - Keep-Alive: timeout=89


Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Response '/mpp-goodbyestranger-sync/cyberduck/snowball2/' - Received error response without XML content
5858	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: (http-snowball2-1) DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Rethrowing as a ServiceException error in performRequest: org.jets3t.service.ServiceException: Request Error. -- ResponseCode: 201, ResponseStatus: null, with cause: org.jets3t.service.impl.rest.HttpException: 201 Created

@cyberduck
Copy link
Collaborator Author

@dkocher commented

https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html#RESTObjectPUT-responses
We expect a response code of 200 or 204 for a PUT operation but get 201.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Upstream fix in 2a76aa5.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 50389e5.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

99373a5 commented

Do you expect it to work with Snowcone as well?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:9 elliott balsley]:

Do you expect it to work with Snowcone as well?

It looks like it only has a NFS interface.

@cyberduck
Copy link
Collaborator Author

99373a5 commented

Oops. Okay, I read somewhere it uses S3 but it looks like you’re right.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
6.8.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck