> 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/stook-cloud-object-storage.md).

# Stook: Cloud Object Storage

Learn about Stook Object Storage, Medianova’s S3-compatible cloud object storage service.

Stook Object Storage is Medianova’s S3-compatible cloud object storage service.

Use it to store, retrieve, and manage object data through the [Medianova Control Panel](https://cloud.medianova.com) or S3-compatible clients and SDKs.

## Store Data in Stook Buckets

Stook Buckets organize objects such as backups, media files, and application data.

Create access keys to control access to individual Stook Buckets or specific paths. You can also use FTP accounts for file transfers without an S3-compatible client.

{% hint style="info" %}
See [Getting Started with Stook](/products/object-storage-stook/getting-started-with-stook.md) to create a Stook Bucket and configure initial access.
{% endhint %}

## Configure Stook Buckets

Use [**Bucket Configuration**](/products/object-storage-stook/bucket-configuration.md) to control access, request traffic, storage capacity, data protection, and event delivery for individual Stook Buckets.

Available settings include:

* **Public Access Block** — Control unauthenticated object access and prevent a Stook Bucket from being made public.
* **CORS Headers** — Control which browser origins can send cross-origin requests.
* **Rate Limit** — Set read and write request limits.
* **Quota** — Set a maximum storage capacity.
* **Server-Side Encryption** — Encrypt new objects at rest with AES-256.
* **Versioning** — Preserve previous versions of objects.
* **MFA Delete** — Require an authenticator code for protected versioning and deletion operations.
* **Object Lock** — Prevent object versions from being deleted until their retention periods expire.
* **Event Notifications** — Send object creation and removal events to HTTPS, Kafka, or AMQP destinations.

{% hint style="info" %}
See [Bucket Configuration](/products/object-storage-stook/bucket-configuration.md) for configuration details and feature dependencies.
{% endhint %}

## Manage Stook Access

Stook provides a master key pair for full access within a storage region. For applications and integrations, create dedicated access keys with permissions scoped to the required Stook Bucket, path, and S3 actions.

Access keys can also use authenticators for operations protected by [MFA Delete](/products/object-storage-stook/bucket-configuration/mfa-delete.md).

{% hint style="info" %}
See [Manage Access Keys](/products/object-storage-stook/manage-access-keys.md).
{% endhint %}

## Connect Stook to CDN

A Stook Bucket can be used as the origin for a Medianova CDN Resource.

The Stook Bucket must be publicly accessible while connected to a CDN Resource. Public access settings and CDN-related restrictions are managed through [**Public Access Block**](/products/object-storage-stook/bucket-configuration/public-access-block.md).

{% hint style="info" %}
See [Connect Stook Bucket to CDN](/products/object-storage-stook/connect-stook-bucket-to-cdn.md).
{% endhint %}

## Use Stook Object Storage Capabilities

* **S3 API compatibility** supports integrations with S3-compatible tools and SDKs.
* **Bucket replication** provides redundancy for high-availability and recovery workflows.
* **Granular access controls** provide bucket-, path-, and action-level access through dedicated credentials.
* **FTP accounts** support file transfers without an S3-compatible client.
* **Bucket configuration controls** provide access, traffic, capacity, data protection, and event notification settings.

## Use Stook Object Storage for Common Workloads

* **Backup and archiving** — Store data that requires durable, scalable storage.
* **Media storage** — Store images, video, and downloadable files.
* **Application data** — Connect applications through the S3-compatible API.
* **CDN origin storage** — Store objects in Stook and deliver them through a Medianova CDN Resource.
* **Event-driven workflows** — Trigger external workflows when objects are created or removed.

## Continue with Stook Object Storage

* [Getting Started with Stook](/products/object-storage-stook/getting-started-with-stook.md)
* [Bucket Configuration](/products/object-storage-stook/bucket-configuration.md)
* [Manage Access Keys](/products/object-storage-stook/manage-access-keys.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/stook-cloud-object-storage.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.
