This page contains information on configuring a volume that is associated with a repository in Google Cloud storage.
Authorization for the Platform to read from (and, optionally, write to) a Google Cloud storage bucket associated with a volume is provided by authenticating with a Google Cloud service account that has access to the bucket.
When making the API request to create a new volume , you must submit a
service array. In the case that the volume is associated with Google Cloud storage, the values of the parameters in the
service object are as follows:
|Google Cloud Platform service parameter
|Description of value
|This should be be set to
|The name of the Google Cloud storage bucket.
|The endpoint to use when talking to Google Cloud storage.
|If provided, the value of this parameter will be used to modify any object key before an operation is performed on the bucket.
Even though Google Cloud Platform is not truly a folder-based store and allows for almost arbitrarily named keys, the prefix is treated as a folder name. This means that after applying the prefix to the name of the object the resulting key will be normalized to conform to the standard path-based naming schema for files.
For example, if you set the
prefix for a volume to "a10", and import a file with
location set to "test.fastq" from the volume to the Platform, then the object that will be referred to by the newly-created alias will be "a10/test.fastq".
|The client email address for the Google Cloud service account to use for operations on this bucket.
|The private key for the Google Cloud service account to use for operations on this bucket.
In certain situations, however, it may be necessary to set up additional configuration on the bucket itself. For details, please see the documentation on enabling cross-origin resource sharing (CORS).
Updated 6 months ago