---
title: Create a bucket
description: "Create a new private bucket, or an Azure container, from the Overview page, and the naming rules a bucket has to follow to be created."
section: Files
order: 15
audience: [owner]
status: published
lastVerified: 2026-09-15
sources:
  - web/src/components/app/CreateBucketDialog.tsx
  - web/src/components/app/BucketSelection.tsx
  - src/objects/routes/providers.bucket-create.ts
  - src/objects/organisation.constants.ts
---

Owners can create buckets without leaving quickS3. The new bucket is private and billed by your provider like any other.

1. Open **Overview** and find the connection the bucket should belong to.
2. Select **Create bucket** on its card. On Azure connections the button says **Create container**.
3. Check the connection and region shown at the top of the dialog. The bucket is created there.
4. Enter a name and select **Create bucket**.

Names must be 3 to 63 characters long, use only lowercase letters, numbers, and hyphens, and start and end with a letter or number. Most providers share bucket names across all their customers, so a common name like `backups` is probably taken. Add something specific to your team.

The bucket appears on the connection's card straight away.

## Before you use it

Only Owners can open the new bucket at first. To let others in, add a rule for it to a [role](/docs/access/custom-roles/).

If the connection uses **Bucket scopes**, quickS3 tries to add the new name to them. If a message says the bucket was "created with follow-up problems", read it: the bucket exists, but something after creation failed, such as updating the scopes or setting CORS. Select **Open connections**, fix what the message describes, and run **Test connection**.

## When the button is missing or creation fails

- **No Create bucket button.** You're not an Owner, or it's a Google Cloud Storage connection. Create Cloud Storage buckets in the Google Cloud console instead.
- **Creation is refused.** The connection's key is probably limited to existing buckets. Creating buckets needs a broader key; each [provider guide](/docs/connections/overview/#supported-providers) says which permission. If you'd rather keep the narrow key, create the bucket in your provider's console and add it to **Bucket scopes**.
- **The name is taken.** Someone, possibly another company, already has a bucket with that name. Pick another.