This page contains information on configuring a volume that is associated with a repository in Google Cloud Storage.
For details about using a volume associated with an AWS S3 bucket, please see the Amazon Web Services S3 Volumes page.
Authorization for Seven Bridges 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.
The Google Cloud Storage tutorial explains the process of configuring a volume associated with a Google Cloud Storage repository in detail. In short, the process is:
- Create a Google Cloud service account that has access to the repository associated with your volume. This account should be:
(a) A Reader account for read-only volumes, or or Writer account for read-write volumes;
(b) A Reader account on the objects within those bucket(s).
- Submit the Google Cloud service account credentials (email address and private key) in the
storage.credentialsobject in the API request to create the volume. For the syntax of this object, see below.
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.
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 almost 2 years ago