FAQ

Is it really S3-compatible? Which tools work?

Yes — it speaks the S3 API, so standard S3 tools and SDKs work: the AWS CLI, s3cmd, rclone, MinIO client, and the AWS SDKs. Point them at the bucket's regional endpoint (shown on the bucket-create form and in bucket settings) with an access key.

How do I connect an app?

Create an access key, copy the Access Key ID and Secret (the secret is shown only once), and configure your S3 client with those plus the regional endpoint and region.

Can I make a bucket public?

Yes — toggle Public Access on the bucket's General tab, or apply a bucket Policy that allows anonymous (Principal: "*") access. The console warns you before applying a public policy. Only do this for content you intend to expose to the internet.

What's the difference between Delete bucket and Empty bucket?

Empty bucket deletes every object but keeps the (now-empty) bucket. Delete bucket removes the bucket itself and requires it to be empty first. Both are permanent and type-to-confirm.

Do I need versioning or object lock?

Versioning keeps prior versions of overwritten/deleted objects — useful for recovery. Object Lock (WORM) prevents objects being changed or deleted for a retention period — for compliance. Object Lock can only be enabled when the bucket is created, and it turns versioning on.

Should I use the root access keys or IAM?

Prefer IAM policies and roles for scoped, least-privilege access rather than sharing the root account's keys. Rotate any key you do share.

Why don't I see Users and Groups?

The IAM directory currently exposes Policies and Roles in the console; users and groups are being reconciled with the portal's existing team model. Policies and roles cover most access-control needs in the meantime.