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

# kubox cloud disconnect

Remove the account from Kubox and show the AWS access left to revoke

### Synopsis

DISCONNECT IS NOT REVOKE, and the difference is the whole command.

disconnect  removes the connection from Kubox
revoke      removes the AWS-side authorisation, which only you can do

This does the first and DELETES NOTHING in your account.

Not the role, not the keys, not the state bucket. Those are yours: the
record of what was built, the key that decrypts it, and the role that could
act on either. Kubox removing them would mean Kubox COULD remove them, which
is the custody this boundary exists to avoid.

So this forgets, and then tells you what is still there and what deleting
each one actually costs -- including the one people stop before, which is
that deleting the role does not revoke access to credentials Kubox has
already sealed.

It refuses while a cluster is still built into the account, because a
cluster whose connection is gone cannot be torn down by anything. Asks
before acting unless --yes.

```
kubox cloud disconnect <name> [flags]
```

### Options

```
  -h, --help   help for disconnect
      --yes    do not ask for confirmation
```

### Global options

See [global options](/cli-reference/kubox#global-options).

### SEE ALSO

* [kubox cloud](/cli-reference/kubox_cloud)	 - Connect and manage the cloud accounts Kubox builds into