> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/6.0/getting-started-with-weka/weka-cli-overview/cli-reference-guide/weka-cloud.md).

# weka cloud

Configure WEKA cloud connectivity and telemetry.

Manage observability via cloud services.

```sh
weka cloud
```

## weka cloud disable

Turn cloud features off.

```sh
weka cloud disable
```

## weka cloud enable

Turn cloud features on.

```sh
weka cloud enable [--cloud-url <string>]
```

| Parameter               | Description                    |
| ----------------------- | ------------------------------ |
| `--cloud-url` \<string> | Base URL of the cloud service. |

## weka cloud proxy

Manage proxy settings used when connecting to the cloud.

```sh
weka cloud proxy
```

### weka cloud proxy reset

Reset the HTTP proxy used when connecting to the cloud. Direct HTTP connections will be used.

```sh
weka cloud proxy reset
```

### weka cloud proxy set

Set the HTTP proxy used when connecting to the cloud.

```sh
weka cloud proxy set <proxy>
```

| Parameter | Description           |
| --------- | --------------------- |
| `proxy`\* | The proxy URL to set. |

## weka cloud quota-analytics

Manage quota analytics reporting.

```sh
weka cloud quota-analytics
```

### weka cloud quota-analytics disable

Turn quota analytics reporting off.

```sh
weka cloud quota-analytics disable
```

### weka cloud quota-analytics enable

Turn quota analytics reporting on.

```sh
weka cloud quota-analytics enable
```

### weka cloud quota-analytics redact-paths

Manage quota analytics path redaction.

```sh
weka cloud quota-analytics redact-paths
```

#### weka cloud quota-analytics redact-paths off

Turn quota analytics path redaction off.

```sh
weka cloud quota-analytics redact-paths off
```

#### weka cloud quota-analytics redact-paths on

Turn quota analytics path redaction on.

```sh
weka cloud quota-analytics redact-paths on
```

### weka cloud quota-analytics status

Show quota analytics reporting and path redaction configuration.

```sh
weka cloud quota-analytics status
```

**Columns:** `reporting`, `redactPaths`

## weka cloud status

Show cloud connectivity status.

```sh
weka cloud status
```

**Columns:** `container`, `health`, `size`, `lastException`, `error`, `lastUpload`

## weka cloud upload-rate

Get the cloud upload rate.

```sh
weka cloud upload-rate
```

### weka cloud upload-rate set

Set the cloud upload rate.

```sh
weka cloud upload-rate set --bytes-per-second <rate>
```

| Parameter                      | Description                              |
| ------------------------------ | ---------------------------------------- |
| `--bytes-per-second` \<rate>\* | Maximum upload rate in bytes per second. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/6.0/getting-started-with-weka/weka-cli-overview/cli-reference-guide/weka-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
