Google Cloud Storage

Add your own custom Google Cloud storage to store your app builds.

Set up Google Cloud Storage

For those considering using Google Cloud Storage, the following steps outline the process of integrating this custom storage option into your Updraft setup.

What you need

• Google Cloud storage bucket: You need to create a google cloud storage bucket.

• Project ID: Google Project ID where your bucket is located.

• Service Account Key: Service Account key to access the bucket. See create service account key.

Step 1: Create a google cloud project

1. In the Google Cloud Console, open the menu and navigate to "IAM & Admin," then select "Create Project."

2. On the "Create Project" page, enter a meaningful name for your project in the "Project Name" field. Optionally, you can click "Edit" to modify the project ID. Keep in mind that the project ID cannot be changed after the project is created, so choose one that will meet your needs for the entire project lifecycle.

3. In the "Location" field, click "Browse" to view potential locations for your project. After selecting the desired location, click "Select."

Note: If you cannot find your Google Workspace organization, it means you're not signed in to a Google Workspace account. Some of the features described in the Google Workspace Developer documentation are only available for projects associated with an organization.

1. Finally, click "Create." The Google Cloud Console will take you to the dashboard, and your project will be created within a few minutes.

Step 2: Create a Google Cloud Storage Bucket

To store your backups in Google Cloud, you need to create a Cloud Storage bucket within your project.

1. Log in to your Google Cloud Console.

2. In the navigation menu, go to Storage > Browser.

3. Click Create Bucket.

4. Provide a unique name for your bucket.

5. Choose a storage class based on your needs. For regular backups, Standard is recommended.

6. Select the location where you want your data to be stored.

7. Configure the access control. You can use either fine-grained or uniform access.

8. Click Create to finalize the bucket creation.

Step 3: Set Up Service Account and Key

For Updraft to communicate with Google Cloud, you need to create a service account and download a key.

1. In the Google Cloud Console, navigate to IAM & Admin > Service Accounts.

2. Click Create Service Account.
3. Name your service account (e.g., updraft-google), and provide a description if necessary.

4. In the Role section, assign the service account the Storage Admin role to allow full access to the Cloud Storage bucket.

1. Once created, navigate to the Keys section.

2. Click Add Key > Create New Key and select JSON format.

3. Download and save the JSON key file securely. You will use this key in Updraft.

Step 4: Connect Google Cloud Storage with your Updraft organization

1. Log in to Updraft and go to "Profile -> Overview"

2. Click in the section "Custom Storage" the button "Enable"
3. In the next step choose the option "Google Cloud Storage"

4. Enter your google cloud storage configuration in the next step

• Project ID: The google cloud project ID of your project

• Credentials: The Service Account Key you created to access the bucket as a .json file

• Bucket name: The name of the google cloud bucket.

• Password: type in your Updraft Account password to confirm

1. Click on enable to add your Google Cloud custom storage.

Deactivate Google Cloud Custom Storage

Custom storage provides flexibility for storing your uploaded data, but there may be occasions when you need to deactivate or reactivate it.

Steps

1. Accessing Custom Storage Settings: Navigate to your account overview settings and find the "Custom Storage" section.

2. Click on the "Deactivate Custom Storage" option.

3. Confirm your action by entering your account password.

Uploading new app versions/builds:

• Once custom storage is deactivated, new data will be stored on the Updraft DB system again.

• Ensure that you're aware of this change when uploading new builds.

Old app versions/builds

• Each previously uploaded build will not be available anymore

• If a build is stored on inaccessible custom storage, a proper information message will be displayed when attempting to download it.

• Custom storage settings are not removed from the database until the custom storage integration is deleted.

• Reactivating Custom Storage: If you choose to reactivate custom storage, the URLs from previously uploaded builds on custom storage become valid again.

Conclusion: Managing custom storage settings ensures control over where your data is stored. Following these steps allows for a seamless transition between storage options, maintaining accessibility and clarity regarding your uploaded builds.

Note: Make sure to keep your account password secure and be mindful of the storage location information when interacting with builds.

If you are using custom storage, new app versions (.aab, .apk, .ipa), app icons, custom AAB keystore will be stored on your custombucket.

Previous uploaded app versions

When you activate Custom Storage all previous uploaded app versions and installation-links will get unanvailable.

Previous uploaded custom AAB keystore

If you setup a custom AAb keystore and activate later custom storage, you need to re-upload the custom AAB keystore.

To get more infos and to enable this feature, please reach out to [e-mail]