> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/api-reference/storage-and-backup/ionos-object-storage/ionos-object-storage-for-contract-owned-buckets.md).

# IONOS Object Storage for Contract-Owned Buckets

Use this S3-compatible API to manage objects in contract-owned buckets using HMAC credentials.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Get started</strong></mark></td><td>Authentication, base URL, and a working API example.</td><td><a href="/cloud/api-reference/readme/getting-started.md">Getting Started</a></td></tr><tr><td><mark style="color:blue;"><strong>API Status</strong></mark></td><td>Check service availability and current incidents.</td><td><a href="https://status.ionos.cloud/">https://status.ionos.cloud/</a></td></tr></tbody></table>

## Base URL

```
https://s3.eu-central-3.ionoscloud.com
```

Additional regional endpoints are available. See the spec for the full server list.

## Authorization

Contract-owned bucket operations use HMAC-based authentication (AWS Signature Version 4). Sign requests with your contract S3 access key and secret key.

## Version

`2.0.4`

## HTTP Status Codes

| Status Code                 | Message                | Description                                                             |
| --------------------------- | ---------------------- | ----------------------------------------------------------------------- |
| `200 OK`                    | Request succeeds.      | The request was successful.                                             |
| `201 Created`               | Resource created.      | The resource was successfully created.                                  |
| `204 No Content`            | Success, no content.   | The request was successful, but there is no content to return.          |
| `400 Bad Request`           | Invalid request.       | The request is malformed or contains invalid parameters.                |
| `401 Unauthorized`          | Authentication failed. | Authentication credentials are missing or invalid.                      |
| `403 Forbidden`             | Access denied.         | The authenticated user does not have permission to access the resource. |
| `404 Not Found`             | Resource not found.    | The requested resource does not exist.                                  |
| `409 Conflict`              | Resource conflict.     | The request conflicts with the current state of the resource.           |
| `429 Too Many Requests`     | Rate limit exceeded.   | Too many requests have been sent in a given time.                       |
| `500 Internal Server Error` | Server error.          | An unexpected error occurred on the server.                             |
| `503 Service Unavailable`   | Service unavailable.   | The service is temporarily unavailable.                                 |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/api-reference/storage-and-backup/ionos-object-storage/ionos-object-storage-for-contract-owned-buckets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.