> 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.1/fs/managing-object-stores/managing-object-stores.md).
# Manage object stores using the GUI
Using the GUI, you can perform the following actions:
* [Edit the default object stores](#edit-the-default-object-stores)
* [View object store buckets](#view-object-store-buckets)
* [Add an object store bucket](#add-an-object-store-bucket)
* [Edit an object store bucket](#edit-an-object-store-bucket)
* [Show recent operations of an object store bucket](#show-recent-operations-of-an-object-store-bucket)
* [Delete an object store bucket](#delete-an-object-store-bucket)
## Edit the default object stores
Object store buckets can reside in different physical object stores. To achieve good QoS between the buckets, WEKA requires mapping the buckets to the physical object store.
You can edit the default local and remote object stores to meet your connection demands. When you add an object store bucket, you apply the relevant object store on the bucket.
Editing the default object store provides you with the following additional advantages:
* Set restrictions on downloads from a remote object store.\
For on-premises systems where the remote bucket is in the cloud, to reduce the cost, you set a very low bandwidth for downloading from a remote bucket.
* Ease of adding new buckets.\
You can set the connection parameters on the object store level and, if not specified differently, automatically use the default settings for the buckets you add.
**Procedure**
1. From the menu, select **Manage > Object Stores**.
2. On the left, select the pencil icon near the default object store you want to edit.
3. On the **Edit Object Store** dialog, set the following:
* **Type**: Select the type of object store.
* **Buckets Default Parameters**: Set the protocol, hostname, port, bucket folder, authentication method, region name, access key, and secret key.
{% hint style="info" %}
If using the AWS object store type and access from the WEKA EC2 instances to the object store is granted by the IAM roles, it is not mandatory to set the access and secret keys in the Edit Object Store dialog.
{% endhint %}
## View object store buckets
The object store buckets are displayed on the **Object Stores** page. Each object store indicates the status, bucket name, protocol (HTTP/HTTPS), port, region, object store location (local or remote), authentication method, and error information (if it exists).
**Procedure**
1. From the menu, select **Manage > Object Stores**.
The following example shows two object store buckets.
## Add an object store bucket
Add object store buckets to be used for tiering or snapshots.
**Procedure**
1. From the menu, select **Manage > Object Stores**.
2. Select the **+Create** button.
3. In the **Create Object Store Bucket** dialog, set the following:
* **Name**: Enter a meaningful name for the bucket.
* **Object Store**: Select the location of the object store. For tiering and snapshots, select the local object store. For snapshots only, select the remote object store.
* **Type**: Select the type of object store: AWS, AZURE, or OTHER (for GCP and others).
* **Buckets Default Parameters**: Set the protocol, hostname, port, bucket folder, authentication method, region name, access key, and secret key.
{% tabs %}
{% tab title="AWS" %}
Create object store bucket on AWS
{% endtab %}
{% tab title="GCP" %}
Create object store bucket on GCP
{% endtab %}
{% tab title="Azure" %}
Create object store bucket on Azure
{% endtab %}
{% endtabs %}
5. To validate the connection to the object store bucket, select **Validate**.
6. Optional**:** If your deployment requires a specific upload and download configuration, select **Advanced**, and set the parameters:
* **Download Bandwidth**: Object store download bandwidth limitation per core (Mbps).
* **Upload Bandwidth**: Object store upload bandwidth limitation per core (Mbps).
* **Max Concurrent Downloads**: Maximum number of downloads concurrently performed on this object store in a single IO node.
* **Max Concurrent Uploads**: Maximum number of uploads concurrently performed on this object store in a single IO node.
* **Max Concurrent Removals**: Maximum number of removals concurrently performed on this object store in a single IO node.
* **Enable Upload Tags**: Whether to enable [object-tagging](/4.1/fs/tiering/data-management-in-tiered-filesystems.md#object-tagging) or not.
7. Select **Create**.
{% hint style="info" %}
If an error message about the object store bucket configuration appears, to save the configuration, select **Create Anyway**.
{% endhint %}
## Edit an object store bucket
You can modify the object store bucket parameters according to your demand changes over time.
**Procedure**
1. From the menu, select **Manage > Object Stores**.
2. Select the three dots on the right of the object store you want to modify, and select **Edit**.
3. In the Edit Object Store Bucket dialog, modify the details, and select **Update**.
## Show recent operations of an object store bucket
For active object store buckets connected to filesystems, the system tracks this activity and provides details about each activity on the Bucket Operations page.
The details include the operation type (download or upload), start time, execution time, previous attempts results, cURL errors, and more.
**Procedure**
1. From the menu, select **Manage > Object Stores**.
2. Select the three dots on the right of the object store bucket you want to show its recent operation, and select **Show Recent Operations**.
Show recent operations of an object store bucket
The recent operations page for the selected object store bucket appears. To focus on specific operations, you can sort the columns and use the filters that appear on the top of the columns.
Bucket Operations page
## Delete an object store bucket
You can delete an object store bucket if it is no longer required. The data in the object store remains intact.
**Procedure**
1. From the menu, select **Manage > Object Stores**.
2. Select the three dots on the right of the object store bucket you want to delete, and select **Remove**.
3. To confirm the object store bucket deletion, select **Yes**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.weka.io/4.1/fs/managing-object-stores/managing-object-stores.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.