Keep uploads, images and backups in a bucket. Any S3 client reaches it with an access key, so every application and script on your team works with the same files. Buckets are in beta.
outplane bucket create uploads
Shared by the team, not mounted into one app
A bucket belongs to the team, not to one application. Your code reads and writes files over HTTPS, so a bucket never limits how many instances an application runs, and one bucket can serve several applications at once. Need a disk for a single application instead? That is still a volume.
Private by default, public when you want
A new bucket is private: only requests signed with an access key can read its files. Make it public and anyone with a file's link can read it, while listing stays off. Switch at any time under Settings → Visibility, or with outplane bucket update.
A key for every bucket
Create access keys on the bucket's Access tab, read and write or read only. A key opens its own bucket and nothing else. The secret is shown once, together with the variables your application needs.
Connect an application in one paste
The bucket's Overview tab gives the connection as a .env block: AWS_ENDPOINT_URL_S3, AWS_REGION, the key pair and BUCKET_NAME. Paste it under Settings → Environment, or push it with outplane env push --app <app-name> --deploy.
From the console, the CLI and Otto
Everything works in the console and with outplane bucket and outplane bucket key. Otto can list your buckets, create one and change its visibility, each behind a plan you approve.
During the beta
A team can have five buckets, on every plan. Clients use virtual-hosted addressing and sign with the region auto.
Documentation is at docs.outplane.com/docs/console/buckets.