> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/lens/storage-connectors.md).

# Storage Connectors

Set up an Amazon S3, Google Cloud Storage, or Walrus storage connector for Chirp Lens recordings, with every form field explained.

A **storage connector** is the saved connection between Chirp Lens and the cloud account that holds your backed-up clips. If you want the overview first, read [Back Up Home Camera Recordings to the Cloud](https://docs.chirpwireless.io/lens/cloud-archive.md).

## Where do I add a connector?

1. Open **Cameras** from the main menu, which switches the sidebar to Lens.
2. Select **Storage** near the bottom of the sidebar. The page is titled **Storage connectors**; when empty it says there are no connectors yet and invites you to add the first.
3. Select **Add storage connector**. A small dialog asks for a **Connector type**: **Amazon S3**, **Google Cloud Storage**, or **Walrus**.
4. Choose one and select **Next**. Every form begins with a blue note that repeats the privacy rule, then a required **Name**, then the provider's fields. Required fields carry an asterisk, and **Add connector** stays disabled until they are complete.

## What is on the Storage connectors page?

<figure><img src="https://1153890212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxgYoHO4zlaBzHJcfIrto%2Fuploads%2Fgit-blob-c8fcae271819e4d9228bf64e3a137dae051dabfd%2Fchirp-lens-storage-connectors.jpg?alt=media" alt="The Storage connectors page listing one Amazon S3 connector with Active status, usage, creation date and the row buttons Verify, Edit, Mark key as compromised, Disconnect storage, Uploaded but not registered and Delete"><figcaption><p>The Storage connectors page with one connector.</p></figcaption></figure>

The table has the columns **Name**, **Type**, **Status**, **Usage**, **Details**, and **Created**. **Status** is one of **Active** (green), **Inactive**, **Error**, or **Disconnected**, and hovering it shows when Chirp last verified the connector. **Usage** adds up what Chirp has stored there. **Details** explains anything that needs your attention, for example:

* the provider's error message, or "Check the connector settings and verify it again." for a connector in **Error**;
* "The storage did not accept uploads on {date} (HTTP {status}). Check the settings and credentials of this storage." or "The storage could not be reached for uploads for 24 hours (marked on {date}). Check the address of this storage and its network access.";
* "Key compromised {date} by {user}" and "Disconnected {date} by {user}";
* for Walrus, "Walrus keeps files for the paid period. They can't be deleted earlier.";
* "Seeking support will be checked with the first recording." until the first clip arrives, and "Seeking is not available: this storage doesn't serve file parts. Use an aggregator that supports byte ranges." when playback cannot skip ahead;
* "The signing secret will be confirmed by the first uploaded recording." for a new connector.

A dash means there is nothing to report. **Add storage connector** sits at the top right. A connector that has not been disconnected ends each row with these buttons:

* **Verify** checks the connector again and shows "Connector reachable" or "Connector unreachable" (or the provider's message). Use it after you correct a setting or a credential.
* **Edit** opens the form again. Leave a secret blank to keep the stored one.
* **Mark key as compromised** asks you to type the storage name, then issues a fresh key for new clips and sends it to your cameras. Clips recorded earlier stay readable; cameras that have not received the key keep recording locally. If some cameras did not get the key, a dialog says "New key issued, but N cameras did not receive it." with a **Resend** button, or "N cameras will receive the new key when they next connect."
* **Disconnect storage** erases Chirp's keys for this connector after you type its name. Cameras that still write to it must be moved first, and the dialog names them. [Back Up Home Camera Recordings to the Cloud](https://docs.chirpwireless.io/lens/cloud-archive.md#how-do-i-stop-using-a-storage-account) has the details.
* **Uploaded but not registered** lists files that reached your storage during the last 30 days but whose upload never finished (with **Load more** for long lists, and "No orphaned uploads in the last 30 days." when it is clean). Chirp does not track them, so remove them in your own storage.
* **Delete** asks "Are you sure you want to remove connector ...?"; select **Yes, remove** to confirm.

A **Disconnected** connector shows **Reconnect** instead of **Verify**, **Edit**, **Mark key as compromised**, and **Disconnect storage**. It opens the form again, and because disconnecting erased the stored secrets you enter the credentials like a new connector. Reconnecting does not make older clips readable again. **Uploaded but not registered** and **Delete** stay available.

If the dialog for adding a connector shows "Connector catalog unavailable. Lens Bridge service is offline.", the list of connector types could not be loaded; try again in a few minutes. If another person deletes a connector while you have it open, a dialog says "This storage connector no longer exists."

## What do I enter for Amazon S3 or a compatible service?

* **Bucket** and **Region**: the bucket name (placeholder `my-recordings-bucket`) and its region (placeholder `eu-central-1`).
* **Access Key ID** and **Secret Access Key**: the credentials Chirp uses. The secret field is write-only, and its hint says the key must allow upload, metadata read, download, and delete for the bucket and prefix.
* **Custom Endpoint URL**: only for S3-compatible services outside Amazon. Setting it switches to path-style addressing. The address must be secure and publicly reachable; private or insecure addresses are refused.
* **Key Prefix**: a folder-like prefix so Chirp's files stay apart from anything else in the bucket.
* **Grant TTL (seconds)**: the lifetime of each upload permission. Zero uses the default of 86400, and the accepted range is 60 to 604800.
* **Max Object Size (MB)**: an upper limit per clip.

Tip: create a dedicated access key for Chirp with only those four permissions on only that bucket.

<figure><img src="https://1153890212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxgYoHO4zlaBzHJcfIrto%2Fuploads%2Fgit-blob-f80fafd9943aa1c2335fba4629b0c0d6a846e599%2Fchirp-lens-storage-s3.jpg?alt=media" alt="The Add storage connector form for Amazon S3 with a note about keys, and fields for Name, Bucket, Region, Access Key ID, Secret Access Key, Custom Endpoint URL, Key Prefix and Grant TTL"><figcaption><p>The Amazon S3 form.</p></figcaption></figure>

## What do I enter for Google Cloud Storage?

* **Bucket** and a large **Service Account JSON** box: paste the whole key file. It is write-only. The service account needs permission to create, read, and delete objects in the bucket, because Chirp uses it to sign upload and download links.
* **Object Prefix**, **Grant TTL (seconds)** (same rules as above, 60 to 604800), and **Max Object Size (MB)** are optional.

This storage type is new in this release. Test with one short clip and play it back before you rely on it.

<figure><img src="https://1153890212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxgYoHO4zlaBzHJcfIrto%2Fuploads%2Fgit-blob-e76cfbcbad3081397a9408e8989416cfcc595b68%2Fchirp-lens-storage-gcs.jpg?alt=media" alt="The Add storage connector form for Google Cloud Storage with fields for Name, Bucket, Service Account JSON, Object Prefix, Grant TTL and Max Object Size"><figcaption><p>The Google Cloud Storage form.</p></figcaption></figure>

## What do I enter for Walrus?

* **Publisher URL** and **Aggregator URL** (both required): where Chirp sends clips and where it reads them back. Pick an aggregator that supports range requests so playback can skip ahead.
* **Network** (required), for example `mainnet`.
* **Storage Epochs**: how many storage periods to buy; the default is 1. Think of it as the minimum retention for each clip.
* **Max Blob Size (MB)** and **Grant TTL (seconds)** (for Walrus the maximum is 86400, minimum 60, zero means 86400).
* An optional endpoint field that tells Chirp which network node to ask for the current storage period; empty uses the network's default.
* For a private publisher, **Publisher JWT secret** (write-only) and **Publisher JWT algorithm** (HS256 by default, or HS384 / HS512).

<figure><img src="https://1153890212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxgYoHO4zlaBzHJcfIrto%2Fuploads%2Fgit-blob-89effb8f0afd87146437be835ffa64869d5d1b39%2Fchirp-lens-storage-walrus.jpg?alt=media" alt="The Add storage connector form for Walrus with fields for Name, Publisher URL, Aggregator URL, Network, Storage Epochs, Max Blob Size and Grant TTL"><figcaption><p>The Walrus form.</p></figcaption></figure>

## How are my secrets handled after I save?

Secret fields never display their value again. Editing a connector and leaving a secret blank keeps the stored one, but changing the endpoint requires you to enter the credentials again. Rotate them in your cloud console if someone who knew them should no longer have access. What a rotated key does and does not protect is explained in [the privacy section](https://docs.chirpwireless.io/lens/cloud-archive.md#is-a-backed-up-clip-private).
