Confidential S3

by Acme Corp · Storage · v0.1.2

S3-compatible object storage that runs in a confidential environment, with a console for buckets, keys and access. Objects can be kept in the deployment's own engine, passed through to a storage you already have, or encrypted so that only this deployment can read them.

s3object-storageencryptionattestationconfidential-computing

Deployment blueprint

What this version says it will deploy: its components and the exact images they run

Declared by the publisher

Evidence this version will attest to

Expected digest

97791a22bade4aff17c072f218a238cf997bb165843002f068c78e8bb3ef91c1

A deployment of this version measures itself and must arrive at this. A data owner can decide to trust it before anyone has deployed it — and a deployment that stops matching stops being served.

3 fields left out of the measurement

Ingress/confidential-s3-console /spec/rules/0/host
Ingress/confidential-s3-gateway /spec/rules/0/host
Deployment/confidential-s3-console /spec/template/spec/containers/0/env/3/value

Fields that legitimately differ between deployments — a namespace, a hostname. The list is measured along with everything else, so it cannot be widened without changing the digest.

Components

confidential-s3chart confidential-s3 · 0.1.1

Container images

ghcr.io/super-protocol/confidential-s3/gatewaysha256:63149695e3e69bc041e319e72f4c198d0cf14b18a56c8d6a4d8eb5a320f47509
ghcr.io/super-protocol/confidential-s3/apisha256:192a6d74ab493720ad817ba8e424307b1149c40a036e95eebc8791f2975894a2
ghcr.io/super-protocol/confidential-s3/consolesha256:63af03a01c7a79ff93f25b83d072016579e12a122834b66d502c69ad671b2870
dxflrs/garagesha256:a5706cf1f3d7b349ac5133ec59ad8181b709270b75e5f2fa7b3e1a5c07d67137
docker.io/bitnamilegacy/postgresqlsha256:51db17ce1aa19e1b4ba65bf4ff45f0afcde6b59e44623d0005142703b91f4a1e

Resource requirements

CPU

Memory

8Gi

Storage

64Gi

GPU

Not required

Minimums. A target cluster space must have at least this much free before the deployment is accepted.