> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/storage/object-storage.md).

# Object Storage

## Description

cegedim.cloud provides an **Object Storage Service**, delivering dedicated **Object Stores**, allowing your application to store documents without taking care of capacity, security and availability, with highest standards already built-in.

This is a great way to improve your applications' availability and offload documents, media, structured or unstructured data you usually store on file systems or databases, and reduce your storage costs.

This Object Storage Service is **compatible** with **AWS S3 APIs**, facilitating integration within your applications by using SDKs provided by AWS, in Java, Python, JavaScript, .NET, Go and a lot of other languages.

## Object Storage as a Service

### **Security**

Data is transferred using **HTTPS**, so all transferred data is encrypted over the network. Data is also encrypted **server-side, on disks.** Additionally you can also use a **client-side encryption with your own key** by using a S3 encrypted client from AWS SDK.

### **Simplicity**

cegedim.cloud **Object Storage Service** is a fully managed service, so you don't have to worry about management of a Filesystem, its capacity or its security. You can focus on your application while cegedim.cloud takes care of these details.

### **Reduced Costs**

Costs are far cheaper than traditional block storage. You can reduce your bill up to 90% by offloading your data to this service.

### **High availability**

cegedim.cloud **Object Storage Service** relies on redundant components, with integrated and transparent fail-over / fallback solutions.

### **Multi-Regions Capability**

You can choose to create **Object Stores** with Geo-replication, improving your applications capability to handle DR concerns.

**Data is automatically replicated** to two different regions, and you can access to your data with read/write operations on all regions.

## Billing

The pricing model is entirely based on storage usage, you pay what you use. There is no setup costs.

There are two services:

* **Standard Object Storage** : data is not Geo-replicated
* **Replicated Object Storage** : data is Geo-replicated in two regions

### **Billing Formula**

You will be billed on usage, in gibibytes (2^30 bytes = 1 GiB) per month, based on the average storage allocated in the month.

Monthly price is calculated on a yearly basis (365.25 days) and may therefore vary slightly from one month to another depending on number of days in the month concerned.

To determine your monthly bill, we convert "bytes per hour" to "gibibytes per month".

For detailed information about the billing, please contact cegedim.cloud.


---

# 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://academy.cegedim.cloud/storage/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.