Cloud credentials let an organization connect its own AWS, GCP, or Azure account so Allternit runtimes can provision isolation into the customer’s cloud instead of Allternit’s infrastructure.

Authentication and authorization

Cloud credential endpoints require a Clerk JWT and an active organization. Only organization owners and admins can create or revoke credentials. Members can list and view credentials.

Provider support

The exact fields inside secret are provider-specific; the API stores the entire object as a single sealed blob.

Endpoints

List cloud credentials

Response 200 OK

Create a cloud credential

Response 201 Created

Retrieve a credential

The secret value is never included in the response.

Revoke a credential

Revocation is soft — the row is kept for audit purposes but its status is set to revoked.
Response 204 No Content

Request/response fields

Create request body

Credential object

Error codes

  • Vault — Encrypted OAuth and provider token storage
  • BYOC runtime — Deploy Allternit on customer-managed infrastructure
  • Security model — Trust boundaries and data flows