> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/object-storage-stook/bucket-configuration/rate-limit.md).
# Rate Limit
Limit the number of read and write requests per minute served by a Stook Bucket.
Configure request rate limits to control the number of read and write requests served by a Stook Bucket.
**Rate Limit** applies separate request ceilings to read and write operations. Use these limits to control request traffic and reduce the impact of excessive requests from applications, integrations, or misconfigured clients.
{% hint style="info" %}
Rate limits apply per storage gateway. Requests to a Stook Bucket can be served by multiple storage gateways. As a result, the total number of requests served by the bucket in one minute can exceed the configured ceiling.
{% endhint %}
{% hint style="info" %}
For complete request parameters, response schemas, and error responses, see [Bucket Settings API](/api-documentation/object-storage-stook/buckets/settings.md).
{% endhint %}
## How Rate Limit Works
Rate Limit uses two independent ceilings, measured in requests per minute:
* **Read ceiling** applies to operations that read data, including object downloads, metadata requests, and bucket listings.
* **Write ceiling** applies to other operations, including uploads, copies, and deletes.
When a ceiling is reached, additional requests of that type receive an HTTP `503` response with the `SlowDown` error code.
S3-compatible clients with retry logic can retry these requests. Clients without retry logic receive the error response.
Rate limits apply to all requests made to the Stook Bucket, including requests from:
* CDN Resources connected to the bucket
* FTP accounts
* S3-compatible clients and applications
## Configure Rate Limit
{% stepper %}
{% step %}
### **Open the Stook Bucket**
In the [Medianova Control Panel](https://cloud.medianova.com), select **Stook Object Storage → Buckets**, then select the Stook Bucket you want to configure.
{% endstep %}
{% step %}
### **Open Rate Limit**
On the **Bucket configuration** page, select **Rate limit**.
{% endstep %}
{% step %}
### **Enable Rate Limit**
Turn on **Enabled**.
{% endstep %}
{% step %}
### **Set the request ceilings**
Enter the maximum number of requests per minute in **Read ceiling** and **Write ceiling**.
At least one ceiling must be greater than `0`.
{% endstep %}
{% step %}
### **Save the configuration**
Select **Save Changes**.
{% endstep %}
{% endstepper %}
## Configuration Fields
Field
Description
Default
Enabled
Enables or disables request rate limiting for the Stook Bucket.
Off
Read ceiling
Maximum number of read requests served per minute.
0
Write ceiling
Maximum number of write requests served per minute.
0
## Disable Rate Limit
To remove the configured request limits:
{% stepper %}
{% step %}
### **Open Rate Limit**
On the **Bucket configuration** page, select **Rate limit**.
{% endstep %}
{% step %}
### **Disable Rate Limit**
Turn off **Enabled**.
{% endstep %}
{% step %}
### **Save the configuration**
Select **Save Changes**.
{% endstep %}
{% endstepper %}
Requests to the Stook Bucket are no longer rate limited.
## Configure Rate Limit with the API
Use the bucket settings endpoint to configure Rate Limit:
```http
PATCH /api/v2/stook/{organization_uuid}/bucket/{bucket_uuid}/settings
```
Send:
```json
{
"is_rate_limit": true,
"rate_limit": {
"max_read_ops": 5000,
"max_write_ops": 500
}
}
```
The request enables Rate Limit and configures separate read and write ceilings:
* `max_read_ops` corresponds to **Read ceiling**.
* `max_write_ops` corresponds to **Write ceiling**.
To disable Rate Limit, send:
```json
{
"is_rate_limit": false
}
```
## Troubleshooting
### Rate Limit cannot be enabled
If both **Read ceiling** and **Write ceiling** are set to `0`, Rate Limit cannot be enabled.
Set at least one ceiling to a value greater than `0`, or disable **Enabled**.
### Requests return HTTP 503 SlowDown
The configured read or write ceiling has been reached.
Clients with retry logic can retry the request. If the configured limit is too restrictive for the expected workload, increase the corresponding ceiling and save the configuration.
### Request volume exceeds the configured ceiling
Rate limits apply per storage gateway rather than as a single global limit for the Stook Bucket.
Because requests can be served by multiple storage gateways, the total request volume observed for the bucket can exceed the configured per-gateway ceiling.
## Related Topics
* [Bucket Configuration](/products/object-storage-stook/bucket-configuration.md)
* [Quota](/products/object-storage-stook/bucket-configuration/quota.md)
* [Connect Stook Bucket to CDN](/products/object-storage-stook/connect-stook-bucket-to-cdn.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://clients.medianova.com/products/object-storage-stook/bucket-configuration/rate-limit.md?ask=&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.
