Cyberduck Mountain Duck CLI

Version 46 (modified by dkocher, on Nov 8, 2011 at 4:02:09 PM) (diff)

--

Table of Contents

  1. Connecting to Google Storage
  2. Legacy Authentication
  3. OAuth 2.0 Authentication
    1. Creating a bucket
  4. Bucket Access Logging
  5. Folders
  6. Files
    1. Metadata
  7. ACLs
    1. Granting access to selected users
    2. Granting access to Google Apps domain
    3. Granting access to members of Google Group
  8. Limitations
  9. References

Cyberduck Help / Howto / Google Storage

​Google Cloud Storage is a S3 compatible service with ​pricing based on usage.

Refer also to S3 in general.

Connecting to Google Storage

Legacy Authentication

You must obtain the login credentials (Access Key and Secret) from the ​Google API Console under Legacy Access from the Google Cloud Storage tab.

In the login prompt of Cyberduck you enter the Access Key for the username and Secret for the password. This allows you to connect to one project configured in your account.

OAuth 2.0 Authentication

You must obtain the project ID (x-goog-project-id) of your project from the ​Google API Console under Storage Access from the Google Cloud Storage tab.

In the login prompt of Cyberduck you enter the x-goog-project-id for the username and enter the Authorization Code retrieved from the website where you grant Cyberduck acccess to your account.

You access the page with the authorization code from the link displayed in the login prompt. Click it to open it in a web browser window.

Creating a bucket

When connecting the first time, you must first create a new bucket with File → New Folder... (⌘-N). You can choose the bucket location in Preferences (⌘-,) → S3 The following locations are supported:

  • US
  • EU - Europe

Bucket Access Logging

You need the latest snapshot build.

When this option is enabled in the Google Cloud Storage panel of the Info (File → Info (⌘-I)) window for a bucket or any file within, available log records for this bucket are periodically aggregated into log files and delivered to root in the target logging bucket specified.

Folders

Creating a folder inside a bucket will create a placeholder object named after the directory, has no data content and the mimetype application/x-directory. Directory placeholder objects created in Google Storage Manager are ​not supported.

Files

Metadata

You can edit standard HTTP headers add custom HTTP headers to files to store ​metadata. Choose File → Info → Google Storage to edit headers.

ACLs

Granting access to selected users

You can give access to a specific user to a document by granting READ access to the email address registered with Google. The Web URL from the General tab in the Info window with the format https://sandbox.google.com/storage/<container>/<file> will verify access to the resource using the Google Account login credentials.

Refer also to ​Sharing files using Google Storage.

Granting access to Google Apps domain

Google Apps customers can associate their email accounts with an Internet domain name. When you do this, each email account takes the form ​username@yourdomain.com. You can specify a scope by using any Internet domain name that is associated with a Google Apps account.

Granting access to members of Google Group

Every Google group has a unique email address that is associated with the group. For example, the Google Storage for Developers group has the following email address: ​gs-discussion@googlegroups.com. You can find the email address that is associated with a Google group by clicking About this group, which appears on the homepage of every Google group.

Limitations

  • No content distribution (CDN) configuration.
  • Torrent URLs are not supported.
  • Signed URLs are not supported.

References