Store files and connect a Ghost Bucket

Upload and organise files with File Manager

1. 1Open Storage > File Manager and confirm the current folder.
2. 2Upload a small file first and wait for completion.
3. 3Open its preview or download it to confirm the expected content.
4. 4Move or rename only after checking links or application references that depend on the old path.
5. 5Before deletion, review whether the item can be recovered and how long recovery is available. A deleted listing is not a substitute for a backup.

Create or attach a bucket

1. 1Open Storage > Ghost Buckets and choose Create Ghost Bucket, or select the bucket option while deploying an app.
2. 2Choose a new bucket for independent uploads, or an eligible existing bucket when you intend to reuse its contents.
3. 3Review the name, access mode and storage settings, then create or attach it.
4. 4Open Connection Guide. Copy the bucket identifier and endpoint shown there, even when the display name or stage tag looks different.
5. 5Configure the application's storage adapter and test an upload, read and deletion of a disposable test file.

Create a credential pair

1. 1Open the bucket's Access Keys tab and create a clearly labelled entry for the integration.
2. 2Grant only the needed actions and folder scope. A read-only consumer does not need deletion rights.
3. 3Treat the access key ID and secret from that same entry as one pair. Do not use the ID from one entry and the secret from another.
4. 4Complete any verification required to reveal the secret, then copy it securely.
5. 5For S3-compatible clients, use the S3 connection guide's endpoint, bucket, signing region and path-style setting. Do not paste an HTTP authorisation-header value into an AWS credential field.
6. 6Test the integration before switching production traffic.

Rotate or revoke access

To rotate, create a replacement pair, update the integration and verify it, then revoke the old entry. To stop access immediately, revoke the affected key and expect integrations using it to fail until reconfigured. Revoking a key does not delete the files. Multiple integrations can have separate keys so one can be revoked without replacing all the others.

Share files with people

Use Share Links when recipients should open specific content without receiving storage credentials. Review expiry and access restrictions before sharing. Test the link as the intended recipient. If sharing must stop, revoke or expire the link; do not assume changing its label removes access.

Control storage and recovery

Review Usage & billing and the workspace storage defaults. If a bucket inherits workspace settings, a workspace change can affect it; use a deliberate override when available. Review automatic growth limits before enabling them. Version history and recycle-bin recovery depend on retained versions and policy; verify what is available before replacing or deleting important files.

Expected result

Your client can perform only its intended operations, share links have the intended access, and a downloaded test file matches what you uploaded.