> 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/4.0/additional-protocols/s3/s3-cluster-management/s3-cluster-management.md).

# Manage the S3 service using the GUI

This page describes how to set up, update, monitor, and delete an S3 cluster using the GUI.

Using the GUI, you can:

* [Create an S3 cluster](#create-an-s3-cluster)
* [Update an S3 cluster configuration](#update-an-s3-cluster-configuration)
* [Delete an S3 cluster configuration](#delete-an-s3-cluster)

## Create an S3 cluster

An S3 cluster configuration includes a filesystem, port, and list of hosts.

**Procedure**

1. From the menu, select **Manage > Protocols**.
2. From the Protocols pane, select **S3**.
3. On the Configuration tab, select **Configure**.
4. In the S3 Cluster Configuration dialog, set the following properties:
   * **Filesystem**: The filesystem to use for the S3 service. By default, when adding a bucket, it will be created in this filesystem.
   * **Port**: Default 9000. If required, modify the port through which the cluster exposes the S3 service. Do not set port 9001.
   * **Anonymous Posix UID:** If required, modify the Posix UID assigned to anonymous users.
   * **Anonymous Posix GID:** If required, modify the Posix GID assigned to anonymous users.
   * **Hosts**: To use all available hosts for the S3 configuration, switch on **All Hosts**. If new hosts are deployed later, they do not participate in the S3 cluster automatically.\
     To use specific hosts, switch off **All Hosts**, and select the available hosts from the list to participate in the S3 cluster, based on the host IDs in Weka.&#x20;
5. Select **Save**.

Once the system completes the configuration process, the host statuses change from not ready (red X icon) to ready (green V icon).

<figure><img src="https://661826007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuOB5D2WMRjXBnChPFTrk%2Fuploads%2Ftp1IxmonZJtJk2FjTnnS%2Fwmng_S3_cluster_configuration.gif?alt=media&amp;token=8e0abbd8-9866-4f65-9dd0-f538fad6c06a" alt=""><figcaption><p>S3 Cluster Configuration</p></figcaption></figure>

## Update an S3 cluster configuration

You can update the port and the hosts to participate in the S3 cluster.

**Procedure**

1. From the menu, select **Manage > Protocols**.
2. From the Protocols pane, select **S3**.
3. On the Configuration tab, select the pencil icon next to the S3 cluster configuration.

![Edit an S3 cluster configuration](https://661826007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuOB5D2WMRjXBnChPFTrk%2Fuploads%2F44dEpfyVV6fvGoef16NB%2Fwmng_s3_edit_configuration_button.png?alt=media\&token=8d73d5f1-8f2f-4090-abe2-1cab293a8204)

4\. Update the properties as required.

5\. Select **Save**.

![Edit S3 Cluster Configuration](https://661826007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuOB5D2WMRjXBnChPFTrk%2Fuploads%2FgnrEzMSeYQJ0fYtIwaRM%2Fwmng_s3_edit_configuration_dialog.png?alt=media\&token=00908480-cd49-4c9e-a9ba-7d950a712a49)

## Delete an S3 cluster configuration

Deleting an existing S3 cluster managed by the Weka system does not delete the backend Weka filesystem but removes the S3 bucket exposures of these filesystems.

**Procedure**

1. From the menu, select **Manage > Protocols**.
2. From the Protocols pane, select **S3**.
3. On the Configuration tab, select the trash icon next to the S3 cluster configuration.

![Delete an S3 cluster configuration](https://661826007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuOB5D2WMRjXBnChPFTrk%2Fuploads%2Fpk0SMZhLXbTKZLsFgrgx%2Fwmng_s3_delete_configuration.png?alt=media\&token=af450ccf-b730-49f4-954f-27d4994a2681)

4\. In the S3 Configuration Reset message, select **Reset**.&#x20;


---

# 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/4.0/additional-protocols/s3/s3-cluster-management/s3-cluster-management.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.
