Skip to main content
Object Storage — S3

Object Storage

S3-compatible object storage. Create buckets from the console or with kubectl, and access them with any S3 tool.

zsh — kubectl
❯
s3bucketclaim/uploads created
s3bucketaccess/web-app created
❯ kubectl get s3bucketclaims
NAME PHASE
uploads Bound
❯ aws s3 cp report.pdf s3://uploads/
upload: ./report.pdf to s3://uploads/report.pdf
❯
S3-compatibleboto3, AWS CLI, rclone, mc
Three copies of every objectAcross three independent data centers
Controlled accessSeparate keys per app
Pay for what you useStored volume and egress

Service components

S3BucketClaimBucketStorage for one project, with a Delete or Retain deletion policy.
S3BucketAccessApp accessA separate identity per app, limited to specific buckets with Read or ReadWrite access.
SecretEndpoint and keysAccess keys are written straight to a Secret.
ObjectsFilesFile browser in the console, multipart upload and time-limited links.
Policy · CORSAccess rulesBucket policies and CORS for browser access.
Lifecycle · WebsiteLifecycle and websiteAutomatic cleanup of old files and static website hosting.

Two ways to create a bucket

ConsoleCreate buckets and app access, with a built-in file browser.
1Bucket name2Deletion policy3App access4Access level5Endpoint and keys
kubectlOne YAML file you can keep in Git and apply with Helm or Flux.
!bucket.yaml×
production › bucket.yaml
1apiVersion: oss.tapsicloud.com/v1alpha1
2kind: S3BucketClaim
3metadata: {name: uploads, namespace: production}
4spec:
5 deletionPolicy: Retain
6---
7apiVersion: oss.tapsicloud.com/v1alpha1
8kind: S3BucketAccess
9metadata: {name: web-app, namespace: production}
10spec:
11 buckets:
12 - {bucketClaimName: uploads, accessMode: ReadWrite}
13 secretName: web-app-s3
✓ dry-runLn 13 · YAML
Connect your app with boto3 and AWS CLI →

Pricing

Based on stored volume and egress. Pricing will be announced soon.
Get a quote

Frequently asked questions

No. Point your endpoint at Tapsi Cloud; S3 SDKs work unchanged.

Both create the same resource. kubectl is recommended for teams using GitOps.

In three independent data centers in Iran, with three copies of every object.