Object storage, built into your Pod
Store uploads, exports and generated files in private Buckets, browse them in the console, and connect your apps with scoped S3 credentials.
Your project can now keep files in a Bucket alongside its apps and databases. Use object storage for uploads, reports, generated assets and exports without attaching a disk to your app.
Buckets belong to a single Brainpod Pod. You create them through the same resource workflow as the rest of your project, and manage their files from the console's Storage page.
Create a Bucket and browse your files
Open your Pod, select Resources → Create resource → Bucket, then choose a name, provider and region. Save it and deploy your changes. Once the Bucket is ready, open Storage and select it to:
- browse files and folders;
- upload individual files up to 25 MiB;
- create folders;
- download files;
- delete files and empty folders.
Downloads use short-lived links to the storage provider. Uploads go through the authenticated console and Brainpod's S3 gateway. You do not need to create an API key to use the file browser.
Connect your app without copying credentials
A Bucket exports its S3 endpoint, region, bucket name and bucket-scoped credentials. Reference them in your app's environment variables rather than pasting secrets into its configuration.
For a Bucket named uploads, an app might use:
S3_ENDPOINT=${s3.uploads.endpoint}
S3_REGION=${s3.uploads.region}
S3_BUCKET=${s3.uploads.bucketName}
S3_ACCESS_KEY=${s3.uploads.accessKeyId}
S3_SECRET_KEY=${s3.uploads.secretAccessKey}
Use the environment variable names your app expects and configure its S3 client for path-style addressing. Brainpod delivers the credentials to the workload; your app connects directly to the S3 provider with native S3 authentication.
Manage objects from the CLI
S3 commands are already available in Brainpod CLI v0.0.7 and later. Use your normal Brainpod login and select the Pod:
brainpod --pod my-pod s3 ls
brainpod --pod my-pod s3 cp ./photo.png s3://uploads/photo.png
brainpod --pod my-pod s3 cp s3://uploads/photo.png ./downloaded.png
The CLI also includes mv, upload, download and rm. Copies and
file-based uploads are limited to 25 MiB; explicit streaming commands cover
larger transfers. Paths use the logical Bucket name within your selected Pod,
not the provider's physical bucket name.
Your API key needs explicit s3:list, s3:read or s3:write permissions
for the Pod. Existing keys are not expanded automatically, and write access
includes replacement and deletion.
Two ways to connect
Scripts using a Brainpod Bearer API key can call the gateway at
https://<pod-name>.s3.brainpod.io/<bucket-name>/<object-key>.
The CLI handles this authentication for you.
The gateway is not a drop-in endpoint for AWS CLI or SDK authentication: it uses Brainpod Bearer keys rather than AWS Signature Version 4. Apps using an S3 SDK should use the direct provider connection above.
Get started
Provider and region choices depend on the available storage catalog, and a Bucket's placement cannot be changed after creation.
Stored objects are not silently removed when you delete the resource: empty the Bucket before removing it and deploying the change.
Read the Bucket guide for the resource definition, CLI examples and supported gateway operations, or open the console to add storage to your Pod.