Before configuring CloudM Archive, ensure you have the following Google Cloud Platform (GCP) and CloudM components in place.
1. Google Cloud Platform prerequisites
CloudM Archive operates on a "Bring Your Own Storage" model. You must configure the following resources in your own GCP environment:
| Requirement | Detail |
|---|---|
| GCP access | Access to the Google Cloud Platform Console. |
| Billing account | A valid GCP Billing Account. |
| GCP project | A new, customer-owned GCP Project with the Billing Account assigned to it. |
| Service account | A standard GCP Service Account created within the project above. |
| Cloud KMS API | The Cloud Key Management Service (KMS) API must be enabled. Search for "KMS" in the GCP search bar or navigate to Security > Cryptographic Keys and select Enable if prompted. |
| Cloud Storage bucket | A storage bucket to hold your archived data. Refer to Supported Google Cloud Storage Classes for CloudM Archive for advice on bucket configuration. |
2. CloudM prerequisites
| Requirement | Detail |
|---|---|
| CloudM platform | The CloudM Google Workspace Marketplace app must be installed. |
| Subscription | CloudM Archive is available on Essential, Pro, and Enterprise tiers. Each archived user consumes one licence from your subscription. Refer to the CloudM Automate Licensing Policy for details. |
| Domain-wide delegation | A GCP Service Account with Domain-Wide Delegation is required to authorise access to your data. Follow the steps in Provide a Google Cloud service account with domain-wide delegation. |
Need help? Contact CloudM Support