---
title: "Configure a GCS Origin"
slug: "configure-a-gcs-origin"
updated: 2025-07-08T13:08:53Z
published: 2025-07-08T13:08:53Z
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwilt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure a GCS Origin

Media Delivery supports configuring a Google Cloud Storage (GCS) bucket as an origin. For comprehensive instructions on configuring origins, see [Configure an Origin](/v1/docs/configure-an-origin). Specific details for configuring a GCS bucket as an origin are provided in this article.

## Configure the Origin

**To configure a GCS origin:**

1. When configuring a [Single Origin](/v1/docs/configure-a-single-origin), or an [Origin with Failover](/v1/docs/configure-a-failover-origin), set the parameters described in the following steps.
2. In the Add Host Origin dialog, from the Origin Authentication dropdown, select **Signature V4**.

![SignatureV4Fields80.png](https://cdn.document360.io/fa039225-513b-46a1-ba78-a57a1f1cb7c6/Images/Documentation/SignatureV4Fields80.png)

1. Define these fields:

| Attribute | Description |
| --- | --- |
| Access Key | The access key ID associated with the GCP account or IAM user that has permissions to access the GCS bucket. |
| Private Secret Key | Select the secret access key used to authenticate and authorize requests to the GCS bucket. If needed, first [add the key](/v1/docs/configure-a-gcp-origin#add-the-key) to the dropdown menu. |
2. In the **Origin Hostname** field, enter `storage.googleapis.com`. The bucket name itself is added to the origin request path.

![GCSbucketOrigin1.png](https://cdn.document360.io/fa039225-513b-46a1-ba78-a57a1f1cb7c6/Images/Documentation/GCSbucketOrigin1.png)
3. Optionally, define the other attributes, as described in [Configure an Origin](/v1/docs/configure-an-origin).
4. Save the origin.

## Add the Key

To make your key available for selection when configuring a GCS origin, upload it to the CDN. Note that all keys uploaded by users in your organization will be available to all projects created by users in your organization.

Here, we'll describe how to add a key using the Delivery Services Management UI. Alternatively, you can use the [Keys Manager API](https://api-docs.qwilt.cqloud.com/docs/CDN%20APIs/Keys%20%20Manager%20API/keys-manager-start-here).

**To upload a key:**

1. When [configuring the origin](/v1/docs/configure-a-host-or-path-origin), set **Origin Authentication** to **Signature V4**. Additional fields and the **Manage all keys** button are displayed. ![s3OriginManageAllKeys80.png](https://cdn.document360.io/fa039225-513b-46a1-ba78-a57a1f1cb7c6/Images/Documentation/s3OriginManageAllKeys80.png)
2. Select **Manage all Keys**.
3. In the Key Management dialog, select **Add Key**.
4. In the Add Key dialog:
  - **Key Name** - Enter a descriptive Key Name.
  - **Key** - Copy the Base64 encoded cryptographic key (hashed with SHA-256).
  - **Description** - Enter a short text that describes the key.  

  
  

![addKey1.png](https://cdn.document360.io/fa039225-513b-46a1-ba78-a57a1f1cb7c6/Images/Documentation/addKey1.png)
5. Select **Add Key**.