Google Cloud Storage

Object storage for installs already on GCP, authenticated by service account so access stays scoped and auditable in Google IAM.

Google Cloud Storage is the right choice when your infrastructure already lives on GCP, or when the governance conversation calls for it. Authentication uses a service-account JSON key, stored encrypted, which means access is scoped and auditable at the Google IAM layer rather than resting on a long-lived credential pair — a meaningful difference when someone asks who can reach your media and how that access is revoked.

Creatives offload automatically on creation with optional local deletion, and public or Cloud CDN URLs handle delivery. Because the plugin behaves identically to the other storage backends, keeping media in the same project as the rest of your workloads costs nothing in complexity. Storage classes remain available at the bucket level for cost tuning, and installing the plugin only makes GCS selectable — the admin decides when to activate it.

Key features

• Service-account JSON authentication, stored encrypted, with scoping and auditing handled in Google IAM.
• Automatic offload on creation with optional local deletion.
• Public or CDN URL support for delivery, including Cloud CDN.
• Native fit for GCP-hosted installs, keeping media in the same project as your other workloads.
• Key prefix support for organised bucket layouts.
• Storage-class flexibility at the bucket level for cost tuning.
• Selectable, not forced — installing makes GCS available; the admin decides when to activate it.

Powered by

Google Cloud Storage connects to Google Cloud Storage using a service-account JSON credential you provide. No AI vendor is involved.

Ideal for

• Installs already running on Google Cloud Platform.
• Organisations that require IAM-scoped, auditable access to stored media.
• Teams consolidating media alongside existing GCP workloads.
• Operators who need storage-class tuning for long-term cost control.