> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# ankra bucket

> Manage object storage buckets Ankra creates on your provider credentials

## ankra bucket

Create, list, inspect and delete object storage buckets on the organisation's Hetzner, Scaleway, DigitalOcean or UpCloud credentials. Ankra creates the bucket, verifies it and keeps its access keys; the keys are never printed.

## ankra bucket create

Create an object storage bucket on one of the organisation's provider
credentials (Hetzner, Scaleway, DigitalOcean or UpCloud). Ankra creates the
bucket, verifies it and keeps its access keys; the bucket shows "provisioning"
until that finishes.

The credential defaults to the only one Ankra can create buckets with, the
region to that provider's usual one (fsn1, fr-par, fra1, europe-1) and the
provider-side bucket name to a unique one derived from \<name>.

Hetzner's Cloud API cannot mint Object Storage keys. Store the key pair on the
Hetzner credential once and every bucket after that needs nothing more, or
pass --access-key-id here: the secret key is then prompted for, hidden, so it
stays out of your shell history. --secret-access-key exists for automation;
a value passed that way is recorded wherever the command line is.

Examples:
ankra bucket create registry-storage --credential hetzner-main --region fsn1 --wait
ankra bucket create custody --credential upcloud-main --region europe-1 --bucket acme-custody

```bash theme={null}
ankra bucket create <name> [flags]
```

**Flags**

| Flag                  | Default | Description                                                                                                                                                                                                |
| --------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `--access-key-id`     |         | Hetzner Object Storage access key (Hetzner only; omit to use the pair stored on the credential)                                                                                                            |
| `--bucket`            |         | Provider-side bucket name (default: a unique name derived from \<name>)                                                                                                                                    |
| `--credential`        |         | Provider credential (name or id) the bucket is created with (default: the only one Ankra can use)                                                                                                          |
| `--region`            |         | Provider region (default: that provider's usual one - fsn1, fr-par, fra1, europe-1)                                                                                                                        |
| `--secret-access-key` |         | Hetzner Object Storage secret key (Hetzner only). Prefer the hidden prompt you get by passing only --access-key-id: a flag value lands in your shell history and process list. Use the flag for automation |
| `--timeout`           | `25m0s` | Maximum time to wait when --wait is set                                                                                                                                                                    |
| `--wait`              | `false` | Wait for the operation to finish and report success or failure (default: submit and return immediately)                                                                                                    |

## ankra bucket delete

Stop managing an object storage bucket in Ankra.

By default this removes only Ankra's record of the bucket and the access keys
it kept: the bucket and every object in it stay in your cloud account.

\--destroy-provider-resources also empties and deletes the bucket and removes
the UpCloud object storage service or DigitalOcean Spaces key Ankra created
for it. Everything in the bucket is gone for good. A bucket that is still
being created is always torn down, because the half-finished run may already
have made something billable.

```bash theme={null}
ankra bucket delete [bucket-name|bucket-id] [flags]
```

**Flags**

| Flag                           | Default | Description                                                                                                      |
| ------------------------------ | ------- | ---------------------------------------------------------------------------------------------------------------- |
| `--destroy-provider-resources` | `false` | Also empty and delete the bucket at the provider (everything in it is lost) and remove what Ankra created for it |
| `--yes`                        | `false` | Skip the confirmation prompt                                                                                     |

## ankra bucket get

Show a bucket's details and status

```bash theme={null}
ankra bucket get [bucket-name|bucket-id] [flags]
```

**Flags**

| Flag             | Default | Description                                           |
| ---------------- | ------- | ----------------------------------------------------- |
| `-o`, `--output` |         | Output format: json or yaml (default: human-readable) |

## ankra bucket list

List the organisation's object storage buckets

```bash theme={null}
ankra bucket list [flags]
```

**Flags**

| Flag             | Default | Description                                           |
| ---------------- | ------- | ----------------------------------------------------- |
| `-o`, `--output` |         | Output format: json or yaml (default: human-readable) |