Skip to main content
This guide explains how to connect your Google Cloud Storage (GCS) buckets to Mixpeek, enabling automated data ingestion and processing.

​
Prerequisites

  • An active Google Cloud project.
  • A GCS bucket containing the data you want Mixpeek to process.
  • Permissions to create service accounts and manage IAM policies in your Google Cloud project.

​
Configuration Steps

Connecting Mixpeek to GCS requires granting Mixpeek read access to your bucket. We recommend using a service account with appropriate IAM roles for enhanced security.
1

Create Service Account

First, create a service account that Mixpeek will use to access your GCS bucket.
  1. Navigate to the IAM & Admin > Service Accounts section in your Google Cloud Console.
  2. Click Create Service Account.
  3. Enter a name for the service account (e.g., mixpeek-gcs-access).
  4. Click Create and Continue.
  5. Grant the service account the following roles:
    • Storage Object Viewer (roles/storage.objectViewer)
    • Storage Legacy Bucket Reader (roles/storage.legacyBucketReader)
  6. Click Done.
2

Create and Download Service Account Key

To authenticate with GCS, you’ll need to create and download a service account key.
  1. Find your newly created service account in the list and click on it.
  2. Go to the Keys tab.
  3. Click Add Key > Create new key.
  4. Choose JSON as the key type.
  5. Click Create.
  6. Important: The JSON key file will be downloaded to your computer. Store this file securely as you’ll need it to configure the connection in Mixpeek.
3

Add GCS Connection in Mixpeek

In Studio, go to Settings > Connections > New Connection and pick Google Cloud Storage.
  1. Paste the service account JSON key you downloaded.
  2. Enter the bucket name. Omit the gs:// prefix.
  3. Optionally set a prefix to scope the sync to one folder.
  4. Save. Mixpeek tests the credentials before storing them.
To create the same connection over the API, POST /v1/organizations/connections:
Mixpeek uses the native google-cloud-storage SDK, not the S3-compatible XML API, so you do not need to mint HMAC interoperability keys. service_account_json takes the whole key object. private_key is redacted when you read the connection back.

​
Verification

Once connected, Mixpeek should start discovering files in your specified GCS bucket (and prefix, if provided). You can monitor the ingestion status within the Mixpeek Studio. Depending on your pipeline configuration, feature extraction and indexing will begin automatically for supported file types. If you encounter issues, double-check the service account permissions and the credentials provided in Mixpeek. Ensure the bucket name and project ID are correct.