Skip to content

Tenant management API #13

Closed
Closed

Description

@alanshaw

Driven by the FilOne on-ramp integration requirements. Mirrors what Aurora has, with room to propose iterations once we've learned from it.

References

Surface area to design

  • Admin API (global API key): create/setup/get tenant, set tenant status, create per-tenant API keys, query usage
  • Tenant management API (per-tenant key): create/list/get/delete S3 access keys
  • S3 gateway (per-tenant access key, AWS Sig V4): standard S3 ops scoped to the tenant's data
  • Tenant lifecycle states: active, write-locked, disabled — enforced by the S3 gateway
  • Usage metrics endpoint: hourly storage bytes / object count, daily egress bytes, queryable per tenant over time range
  • Idempotency across all admin operations
  • Tenant isolation as a non-functional requirement

Hard prerequisites surfaced

These items are outside the spike but blocked by a tenant model that isolates them, and are listed here for visibility (each becomes its own implementation issue once this proposal lands):

  • AWS Signature V4 authentication
  • Multipart upload
  • Pre-signed URLs
  • Server-side encryption of object payloads
  • x-amz-meta-* headers
  • Versioning, Object Lock, Retention
  • CORS (allowing pre-signed requests from the consumer's domain)
  • DNS-level forwarding (e.g. https://{region}.s3.<consumer>.example)

Approach guidance

Implement the same shape as Aurora's tenant API, learn from it, then propose an iteration or alternative as the team gets concrete.

Acceptance

  • Written proposal as markdown
  • Decomposition into follow-up implementation issues for the hard-prerequisite list
  • Aurora's API documented as the starting point + diff against proposed shape

Note

Same caveat as #42 — if it turns out this spike is bigger than "S3 on Forge" itself, easy to promote to a sibling epic.

Activity

  1. self-assigned this
    on Jun 3, 2026
  2. changed the title [-]Spike: tenant management API[/-] [+]Tenant management API[/+] on Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions