Repositories

A Storage Repository (or “Repo”) aggregates one or more Storage Buckets under a single API interface compatible with AWS, GCP, and Azure APIs and SDKs. You generate one or more API key/secret pairs for the repo, and each key grants access—using the chosen API type—to all buckets within that repository.

---

Properties

The properties in the repo card are:

• Name A human-readable label for the repository.

• API type The protocol clients will use. Supported values: S3, GCS, Azure Blob.

• Storage Buckets A list of one or more buckets you’ve previously configured.

• API keys

  Multiple key/secret pairs, each following the conventions of the selected API:

  • S3: API Key ID & API Secret.

  • GCS: Client Email & Private Key.

  • Azure Blob: (no additional client identifier) & Credential.

Note: You must save the Repo before adding API keys. Click Add API Key, then immediately copy the secret—secrets are shown only once.

---

Naming Constraints

⚠️ Several constraints for the naming:

• S3 & GCS: Bucket names within the same Repo must be unique. You cannot mix an S3 bucket named “mybucket” with a GCS bucket named “mybucket.”

• Azure Blob: Storage account names must not collide with any S3/GCS bucket names in the same Repo. You cannot combine an S3 or GCS bucket called “mystorage” with an Azure container under account “mystorage.” However, you may include multiple containers from the same Azure storage account.

In order to add/manage API keys in a new Repo, we must first save the Repo.

---

API Key Properties

The platform automatically generates API keys by clicking on the “Add API key” button. Then, you can edit the description or the access mode, or delete the whole entry.

Each key entry shows:

• Description A text describing the API key purpose such as "Read-only key for data analytics."

• Access Mode: Three possible selections that are READ, WRITE or READ/WRITE.

• Key:

  • S3 API → API Key ID

  • GCS API → Client Email

  • Azure Blob API → (empty)

• Secret:

  • S3 API → API Secret

  • GCS API → Private Key

  • Azure Blob API → Credential

• Created: Date & timestamp

Important: The API secret is encrypted in our database and can only be decrypted in-memory by Bridge nodes. Once you navigate away or reload the page, the secret cannot be recovered—you must generate a new key if you lose it.