> 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/databases/mongodb/overview/resource-allocation.md).

# Resource Allocation

<code class="expression">space.vars.ionos\_cloud</code> allocates DBaaS MongoDB resources per contract. The resources refer to the MongoDB **Clusters**, number of **CPU** cores, **RAM**, and the **Storage** database quota. The default quota includes:

* 16 CPU Cores
* 32 GB RAM
* 5 database clusters
* 1500 GB Disk Space
* varying nodes within each cluster based on the chosen Edition

{% hint style="info" %}
**Note:** A single instance of your database cluster cannot exceed 16 CPU cores and 32 GB RAM.
{% endhint %}

You can view the number of resources that are available and can be used and the number of resources already consumed. Based on the resources available here, you can allocate resources during the creation of a database cluster. For resource allocation, contact [<mark style="color:blue;">IONOS CLOUD Support</mark>](https://docs.ionos.com/cloud/support/).

The database resources allocated as per your user contract are displayed in **Resource allocation**.

![Database Resource Allocation](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-bff9d548a79d63ce87c81835771dee1e0dc3e3ec%2Fmongodb-resource-allocation.png?alt=media)

## Resources based on MongoDB editions

The following table describes the resource allocation such as storage, RAM, CPU, and MongoDB instances based on the edition type:

| **Resources** | **MongoDB Playground** | **MongoDB Business** | **MongoDB Enterprise** |
| ------------- | ---------------------- | -------------------- | ---------------------- |
| **Storage**   | 50 GB                  | 50 – 1280 GB         | 50 – 4000 GB           |
| **RAM**       | 2 GB                   | 2 – 128 GB           | 2 – 230 GB             |
| **CPU**       | 1 vCPU                 | 1 – 32 vCPU          | 1 – 31 Core            |
| **Instances** | 1                      | 1, 3                 | 1, 3, 5, 7             |

## Templates configuration

You may choose between the eight template sizes for **MongoDB Business** edition. Each template varies by vCPU, RAM, and storage resources.

| **Business Edition** | **vCPU** | **RAM** | **Storage** |
| -------------------- | -------- | ------- | ----------- |
| **XS**               | 1        | 2 GB    | 50 GB       |
| **S**                | 2        | 4 GB    | 80 GB       |
| **M**                | 4        | 8 GB    | 160 GB      |
| **L**                | 6        | 16 GB   | 320 GB      |
| **XL**               | 8        | 32 GB   | 640 GB      |
| **XXL**              | 16       | 64 GB   | 960 GB      |
| **4XL**              | 32       | 128 GB  | 1280 GB     |
| **4XL\_S**           | 32       | 128 GB  | 2000 GB     |

{% hint style="info" %}
**Note:** The pricing varies based on the editions and templates chosen. For more information, see [<mark style="color:blue;">Prices</mark>](https://docs.ionos.com/cloud/support/general-information/price-list).
{% endhint %}


---

# 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.ionos.com/cloud/databases/mongodb/overview/resource-allocation.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.