Google Cloud Storage Service Account Connectivity

• Google Cloud administrator configuration
• Collect connection information for database role creation

Google Cloud Administrator Configuration

The following section refers to the configuration steps on Google Cloud Storage for the Service Account authentication method.

Create a Proper Role to Access Google Cloud Storage

A proper role is necessary to assign a user enough permission to access Google Cloud Storage.

1. Go to Google Cloud Platform and authenticate.
2. Select your billing project.

3. From the left navigation menu, click IAM & Admin > Roles.

   

4. Create a custom role and assign the following permissions.

   • storage.buckets.get
   • storage.buckets.list
   • storage.objects.get
   • storage.objects.list

Create and Configure the Service Account

1. From the left navigation menu, click APIs & Services > Service Accounts.

   

2. Click Create Accounts.

3. Enter the account name and description fields.

   

4. Click Create.

5. From the Select a role drop-down, select the role created above. This grants the proper permission for the service account to access Google Cloud Storage data.

   

6. Click Done.

Generate a Key for the Service Account

1. Go to the Keys tab of your newly created service account.

   

2. Click ADD KEY > Create New Key.
3. In the dialog, select the JSON key type.
4. Click Create. A JSON file is downloaded with the information required to access the service account. Keep the JSON file in a safe place.

Collect Connection Information to Create a Database Role

The following parameters are required to access Google Cloud Storage via Service Account authentication. The parameters are included in the JSON file that was received in the above step.

Parameter Name	Description	How to Find it
Billing Project	The Project ID where the Google Cloud Storage was built.	project_id in the JSON file
Client ID	The ID of the service account.	client_id in the JSON file
Client Email		client_email in the JSON file
Private Key ID		private_key_id in the JSON file
Private Key		private_key in the JSON file