The procedure below will explain how to attach a Google Cloud Storage volume for use on the Seven Bridges Platform's visual interface.
- A Google Cloud Platform (GCP) account
- One or more buckets on this GCP account.
- Navigate to the Volumes dashboard.
- Choose the cloud storage provider for your volume.
- Obtain IAM user details.
- Enter IAM user credentials on the Seven Bridges Platform.
- Authorize the IAM user to access your GCS bucket.
- Provide bucket details.
- Review volume details and connect your volume.
- On the Seven Bridges Platform, click on the Data tab of the top navigation bar.
- Select Volumes from the drop-down menu.
- On the Volumes Dashboard of the Platform, click + Connect Storage.
- Select Google Cloud Platform as your cloud storage provider.
- Click Next.
Prior to attaching your GCS bucket to the Platform, you must register it as a volume on the Google Cloud Platform console.
- Log into the Google Cloud Platform console.
- From the menu on the left select IAM & Admin > Service accounts.
- Click + Create service account below the search bar.
- Fill in account details:
- Service account name - Descriptive name to label the account.
- Service account ID - Generated automatically based on the entered service account name. Can be modified if necessary.
- Service account description - More elaborate description of the account’s purpose.
- Click Create. The Service account permissions screen opens.
- In the Select a role dropdown, select Storage > Storage Object Viewer.
- Click Continue. The final screen of the wizard opens.
- In the Create key section click + Create key. Key options are displayed on the right.
- In the Key type list select JSON.
- Click Create. Your browser will download a JSON file containing the credentials for this user. Keep this file safe.
On the Seven Bridges Platform, enter your IAM credentials in the Credentials tab as found in the downloaded JSON from the previous step.
- In the Service account email field enter the email address from the client_email key in the downloaded JSON file..
- From the downloaded JSON file, copy the entire value of the private key.
- Paste the key into the Private key field on the Seven Bridges Platform.
- Click Next.
If you have not authorized the IAM user to access your GCS bucket, follow the directions below on the Google Cloud Platform console.
- On the Google Cloud Platform console, click in the top-left corner and navigate to the Storage section
- Select Storage > Browser.
- Locate your bucket and click the three vertical dots to the far right of your bucket's name.
- Click Edit bucket permissions.
- Click Add members.
- In the New members field enter the service account client's email. This email is located in the JSON downloaded in the previous section.
- From the Select a role drop-down menu, select Storage Legacy > Storage Legacy Bucket Reader.
- Click Save. You have now authorized the newly-created IAM user to access the storage bucket.
- On the Seven Bridges Platform, click Next until you reach the Bucket tab in the Connect a Volume wizard.
- Enter your GCS bucket name.
- Optionally, define a new name for the volume created from this GCS bucket on the Platform. The following characters are allowed for naming a volume: A-Z, a-z, 0-9, and “_”. An underscore can only be used between characters. The minimum number of characters is 3, while the maximum is 32.
- Optionally enter a description for your volume.
- Select access privileges: choose Read only (RO). Read and Write (RW) mode is currently not supported for GCS Volumes.
- Optionally enter a prefix. Learn more about prefixes.
- Click Next.
In this tab, review the details for your volume and click Connect.
Congratulations! You've attached your volume to the Platform. You can make individual data objects within it available as "aliases" on the Platform. Aliases point to files stored on your cloud storage bucket and can be copied, executed, and organized like normal files on the Platform. We call this operation "importing". Learn more about working with aliases.
Pease note that a snapshot of file-related information (such as file size) is taken when the file is imported to the Platform. If the file is subsequently changed directly in the mounted storage, this might result in inconsistent behavior when the file is used in analyses on the Platform.
Updated about 2 years ago