> 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-buckets-management.md).

# S3 buckets management

This page describes how to manage S3 buckets.

You can manage buckets by either standard S3 API calls or using the Weka API/CLI.

You determine the bucket permissions by the user's IAM policy for authorized access or by setting bucket policies for anonymous access. 

Buckets and objects created through the S3 protocol have root POSIX permissions by default. When creating a user with an S3 role, you can set specific POSIX permissions for objects created with this user access/secret keys. Objects created using anonymous access (for buckets with IAM policy allowing that) get the anonymous UID/GID.

By default, all buckets are created within the filesystem specified when creating the S3 cluster configuration. You can create a bucket in a different filesystem by calling the Weka API/CLI.

**Related topics**

[S3 users and authentication](/4.0/additional-protocols/s3/s3-users-and-authentication.md#s3-user-role)

[S3 supported APIs and limitations](/4.0/additional-protocols/s3/s3-limitations.md#naming-limitations)

[Manage S3 buckets using the GUI](/4.0/additional-protocols/s3/s3-buckets-management/s3-buckets-management.md)

[Manage S3 buckets using the CLI](/4.0/additional-protocols/s3/s3-buckets-management/s3-buckets-management-1.md)


---

# 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-buckets-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.