Cyberduck is a free, popular, cross-platform GUI application that can connect to your Swarm domain using Content Gateway S3.
Early Gateway and Cyberduck releases required forcing V2 signatures but that is no longer necessary since Cyberduck 7.2+ The default Amazon S3 profile in Cyberduck and V4 signatures work with recent Cyberduck releases and Gateway 6.2 + (the default Amazon S3 profile and V4 signatures work fine).
We now provide and later.
But we also provide Swarm S3 profiles which force "bucket in path" style requests. Recent Cyberduck defaults to "bucket in host" style requests which works fine with Swarm S3 but requires that your HTTPS proxy server certificates include both domains and domain wildcards (mydomain.example.com and *.mydomain.example.com). Rather than using our profiles you can disable "bucket in host" requests with a Cyberduck internal settings https://tracdocs.cyberduck.io/wikiprotocols/help/en/howto/s3#Disableuseofvirtualhoststylerequestss3/#disable-use-of-virtual-host-style-requests:% defaults write ~/Library/Preferences/ch.sudo.cyberduck.plist s3.bucket.virtualhost.disable true.
Warning: you shouldn't have to use it, but the (non-default) "S3 AWS2 Signature Version (HTTP)" connection type does not use bucket-in-path style access even with that setting. This can lead to a Login failed / request signature mismatch and a "Cannot read container configuration" error when opening a bucket, due to a GET /?location request. Using the default "Amazon S3" profile works as do the "Swarm S3 (HTTP)" and "Swarm S3 (HTTPS) profiles" below. When testing be sure to eject any current connection, restart Cyberduck, and create a new connection on any test – changing the connection type seems buggy.
...
Download and install Cyberduck from https://cyberduck.io.
Download and install these two Cyberduck profiles for Content Gateway:
https://support.cloud.caringo.com/tools/Swarm S3 (HTTP).cyberduckprofile
https://support.cloud.caringo.com/tools/Swarm S3 (HTTPS).cyberduckprofile
OLD:
https://support.cloud.caringo.com/tools/Caringo%20S3%20(HTTPS,V2).cyberduckprofile
https://support.cloud.caringo.com/tools/Caringo%20S3%20(HTTP,V2).cyberduckprofile
If these files do not open in Cyberduck you might have to right-click them in Explorer and explicitly choose Open With => Cyberduck.
Set this Preference (depends on your OS, see https://trac.cyberduck.io/wiki/help/en/howto/preferences) to use Using 100MB parts for multipart uploads , instead of the default 10MB. This improves the speed and storage efficiency of resulting streams.<setting name="s3.upload.multipart.size" value="104857600"/>. It's no longer necessary to set this as it's the default (https://docs.cyberduck.io/protocols/s3/?highlight=s3+upload+multipart+size#options).- Cyberduck should show a S3 configuration dialog. If not you can always choose File => Open Connection.
- In the drop-down at the top, select the connection type of "Caringo Swarm S3 (HTTP)" if http or the "Caringo Swarm S3 (HTTPS)" if you're using an SSL proxy in front of Content Gateway.
You'll need an S3 token for your domain. Generate a new access key (token) via a command-line curl or the Content Portal.
Enter a nickname for this connection, e.g. your domain name but note the name does not matter.
Enter
mydomain.example.comin Server and enter your S3 port (it is configured in /etc/caringo/cloudgateway/gateway.cfg).Verify the URL displayed is correct and accessible from your machine.
Enter the 32-character token uuid as the Token ID or access key. You'll enter the secret later.
Close the connection configuration window and double-click the new connection you just created.
Enter the secret when prompted.
You should now see a list of all the buckets in your domain. It will be empty if the domain is new.
- Create a new bucket with File => New Folder. You might have to press the Refresh button to see it.
- Now you can drag and drop files or folders in and out of your domain, sync directories, edit object metadata, or create temporary signed url's.
...