-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
Add support for Cloudflare R2 #13376
Comments
Using S3 mode I can connect to R2 and list buckets but attempting to list objects in a bucket gives the following error:
|
Can you check whether forcing path style requests works for R2? You can enable this profile in Cyberduck Preferences -> Profiles -> search for "S3 (Deprecated path style requests)" There is a bunch of unsupported APIs which Cyberduck may depend on (Unimplemented object-level operations) - specifically Cloudflare isn't that great of making sure their blog posts are accurate, though. |
Relates to #13379. |
@AliveDevil I can confirm S3 (Deprecated path style requests) profile seems to allow R2 connections to work as expected I can list buckets, download and upload files without any problems. Cloudflare docs do leave a lot to be desired - sigh! |
Yep I've also managed to get R2 working as desired with path style access 👍 |
Hint for the deprecated path style was this sample for the aws-sdk-js1, which explicitely forces the client to use path style.
Footnotes |
@juliancox @deepybee
|
Querying the bucket location is not supported
|
it is not clear how to make objects publicly available
|
At this stage R2 buckets are private only. The only way to make them public seems to be via a cloudflare worker. There is a public access setting under the bucket's settings tab on the cloudflare dashboard but this says "Private - This bucket and its objects are only visible to users, Workers, or services that have been granted explicit access. It is not publicly visible on the Internet." with not option to make it public. The learn more link just after leads to this page: https://developers.cloudflare.com/r2/get-started/#6-bucket-access-and-privacy |
@dkocher Cloudflare R2 will be global for every bucket once out of beta, so trying to get location/region is probably not necessary. |
Allow to set placeholder for hostname in connection profile
Skip querying for multipart uploads when disabled in profile.
Is there any documentation on how to setup R2 on Cyberduck? |
Documentation pending in iterate-ch/docs#198. You can enable the connection profile in Preferences → Profiles.. |
Is your feature request related to a problem? Please describe.
Cloudflare is launching a new S3 compatible object storage service called R2.
Cyberduck (and Mountain Duck) should definitely add support for this new service as it has a lot of benefits over AWS S3 in different cases. (One of which being zero cost on egress)
Describe the solution you'd like
I'd like to see support added for Cloudflare R2 (which is currently in open beta)
Describe alternatives you've considered
In the meantime, I'll see if I can create a custom profile to work with R2 but long term official support would be great.
Additional context
There is some official documentation along with the most relevant doc being the current API implementation status.
Additionally the document about using Wrangler to create and manage buckets might be important.
The text was updated successfully, but these errors were encountered: