> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/learn/references/silk-platform-configuration-limits.md).

# Silk Platform Configuration Limits

Review supported limits for Silk Flex clusters, DataPods, capacity, networking, replication, and system resources when planning or scaling an environment.

Use this reference to review the supported limits and configuration boundaries for Silk Flex clusters, DataPods, networking, capacity, replication, and system resources.&#x20;

These limits can help you:

* Select a Flex cluster size that supports expected growth.
* Plan DataPod capacity and node configurations.
* Allocate sufficient network address space.
* Validate whether an environment can support additional volumes, hosts, replication sessions, or other resources.
* Identify feature-specific requirements before deployment or expansion.

{% hint style="info" %}
**Version considerations**

Supported limits may vary by Silk version, cloud provider, deployment architecture, and DataPod configuration. To view the limits configured for a specific environment, run the `system limitation-show` CLI command.
{% endhint %}

## Flex deployment limits

Each Flex VM supports one Silk cluster. A separate Flex VM is required for each region or availability zone that contains a Silk cluster. You can also deploy multiple Flex VMs — and therefore multiple clusters — within the same region or availability zone.&#x20;

During Flex deployment, you select a small, medium, or large cluster. The selected cluster size establishes the maximum number of DataPods, m.nodes, and c.nodes the cluster can support.

## Cluster limits

The resources supported by each cluster size vary by cloud provider.&#x20;

<table><thead><tr><th width="108.14813232421875">Cluster size</th><th width="164.296142578125">Maximum m.nodes</th><th width="143.3330078125">Maximum c.nodes</th><th width="154.74072265625">Maximum supported DataPods</th><th>Required address range</th></tr></thead><tbody><tr><td><strong>Small</strong></td><td><ul><li>AWS: 2</li><li>Azure: 3</li><li>Google Cloud: 3</li></ul></td><td><ul><li>AWS: 9 </li><li>Azure: 9</li><li>Google Cloud: 10</li></ul></td><td>2</td><td><code>/24</code></td></tr><tr><td><strong>Medium</strong></td><td><ul><li>AWS: 4</li><li>Azure: 6</li><li>Google Cloud: 6</li></ul></td><td><ul><li>AWS: 23</li><li>Azure: 23</li><li>Google Cloud: 24</li></ul></td><td>4</td><td><code>/23</code></td></tr><tr><td><strong>Large</strong></td><td><ul><li>AWS: 17</li><li>Azure: 25</li><li>Google Cloud: 25</li></ul></td><td><ul><li>AWS: 98</li><li>Azure: 99</li><li>Google Cloud: 100</li></ul></td><td><ul><li>AWS: 17</li><li>Azure: 24</li><li>Google Cloud: 24</li></ul></td><td><code>/21</code></td></tr></tbody></table>

These limits describe the total resources supported within the cluster. Individual DataPods remain subject to their own node and capacity limits.

## Network address requirements

Silk uses separate subnets for platform management, host access, replication, and internal DataPod communication.

<details>

<summary><strong>Flex subnet</strong></summary>

Hosts the management interface for the Silk Flex VM. The Flex subnet always requires a `/28` address range.

</details>

<details>

<summary><strong>External Management subnet</strong></summary>

Provides management access to DataPods, including the GUI, API, and administrative SSH when required.

</details>

<details>

<summary><strong>External Data 1 subnet</strong></summary>

Carries storage traffic between database hosts and DataPods.

</details>

<details>

<summary><strong>External Data 2 subnet</strong></summary>

Carries replication traffic between DataPods.

</details>

<details>

<summary><strong>Internal Data 1 subnet</strong></summary>

Supports internal communication between c.nodes and d.nodes.

</details>

<details>

<summary><strong>Internal Data 2 subnet</strong></summary>

Supports internal communication between c.nodes and d.nodes.

</details>

The Flex subnet is separate from the DataPod subnets and always requires a `/28` range. The point at which each subnet is created or assigned depends on the cloud provider and deployment workflow. See the applicable cloud deployment documentation for provider-specific networking requirements.&#x20;

## DataPod configuration limits

DataPod limits depend on the cloud provider, workload profile, storage architecture, and node configuration.&#x20;

Silk supports the following workload profiles:

{% tabs %}
{% tab title="High Performance (Default)" %}
Provides balanced performance and scalability for most production workloads.&#x20;

This is the default profile.
{% endtab %}

{% tab title="Accelerated Performance (Premium)" %}
Supports higher sustained throughput and low-latency workloads by adding read cache to c.nodes.

Additional cloud infrastructure cost and quota may apply.
{% endtab %}

{% tab title="Limited Capacity" %}
Provides lower-capacity configurations for smaller-scale deployments.&#x20;
{% endtab %}
{% endtabs %}

See [DataPod Deployment Profiles](/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md) for guidance on choosing a profile. The selected profile affects the VM configuration and supported capacity options, but it doesn't replace the cluster- and DataPod-level limits described in this article.&#x20;

### m.node limits

Every DataPod requires at least one m.node. The maximum number of supported m.nodes depends on the storage architecture.&#x20;

| Deployment architecture                                                            | Maximum m.nodes per DataPod | d.nodes per DataPod | Resiliency configuration |
| ---------------------------------------------------------------------------------- | --------------------------- | ------------------- | ------------------------ |
| <p><strong>VM Local Disk</strong><br><strong>(AWS)</strong></p>                    | 4                           | 14                  | `12+2`                   |
| <p><strong>VM Local Disk</strong><br><strong>(Azure and Google Cloud)</strong></p> | 4                           | 16                  | `14+2`                   |
| <p><strong>Managed Disk</strong><br><strong>(Azure Pv2)</strong></p>               | 3                           | 9                   | `7+2`                    |

In each configuration, two d.nodes provide data protection and recovery capacity.&#x20;

A DataPod can use a combination of supported small, medium, large, and extra-large m.node sizes. The selected sizes determine its maximum physical capacity. Beginning with Silk v9.5.20, DataPods can support multiple m.node VM types during configuration. Available VM types vary by cloud provider, deployment profile, and storage architecture.&#x20;

{% hint style="info" %}
Integral checkpointing is automatically enabled on all m.nodes as of Silk v8.5.70. This feature regularly saves NVRAM contents to the m.node without affecting system performance.&#x20;
{% endhint %}

### c.node limits

{% columns %}
{% column %}
**AWS** supports 2–7 c.nodes per DataPod.
{% endcolumn %}

{% column %}
**Azure** and **Google Cloud** support 2–8 c.nodes per DataPod.
{% endcolumn %}
{% endcolumns %}

The number of c.nodes selected during DataPod creation affects performance, resiliency requirements, and maximum supported capacity.&#x20;

Azure Managed Disk deployments can also be configured for either 40,000 or 80,000 read IOPS per c.node.&#x20;

## Capacity allocation limits

A DataPod’s maximum allocated capacity is set during its initial configuration and can't be changed after the DataPod is created. Plan for both current and future capacity requirements before provisioning the DataPod.&#x20;

By default, Silk supports logical capacity configurations of 512 TiB and 1,024 TiB.

| Minimum c.nodes | Minimum online c.nodes | Maximum physical capacity | Maximum logical capacity |
| --------------- | ---------------------- | ------------------------- | ------------------------ |
| 2               | 1                      | 324 TiB                   | 512 TiB                  |
| 3               | 2                      | 360 TiB                   | 1,024 TiB                |

For High Performance and Accelerated Performance deployments, two-c.node DataPods support up to 324 TiB or physical capacity and 512 TiB of logical capacity. DataPods with three or more c.nodes support up to 360 TiB of physical capacity and 1,024 TiB of logical capacity.&#x20;

Scale-in operations require the minimum number of online c.nodes shown for the configuration, plus one additional c.node to maintain resiliency during c.node recovery.&#x20;

### Azure Managed Disk capacity requirements

Azure Managed Disk deployments use Azure Premium SSD v2 storage. These deployments:

* Aren’t compatible with Azure availability sets
* Require sufficient Azure storage quota for the selected m.node size
* Depend on regional availability of Azure Premium SSD v2

<table><thead><tr><th width="164.44439697265625">m.node size</th><th width="304.66607666015625">Required Azure quota</th></tr></thead><tbody><tr><td>5 TiB</td><td>9,855 GiB / 10,582 GB</td></tr><tr><td>10 TiB</td><td>17,280 GiB / 18,555 GB</td></tr><tr><td>20 TiB</td><td>33,480 GiB / 35,950 GB</td></tr><tr><td>40 TiB</td><td>66,420 GiB / 71,320 GB</td></tr><tr><td>80 TiB</td><td>132,210 GiB / 141,960 GB</td></tr><tr><td>120 TiB</td><td>198,045 GiB / 212,649 GB</td></tr></tbody></table>

## Replication limits

Silk replication supports physical bandwidth of up to **40,000 Mb/s**.

| Replication resource                | Maximum |
| ----------------------------------- | ------- |
| Replication sessions                | 128     |
| Replication peers per target system | 4       |
| Replicated volume groups            | 128     |
| Replicated volumes                  | 500     |
| Snapshots per volume group          | 40      |
| Replicas or views per snapshot      | 24      |

The following restrictions apply when configuring replication relationships:

* A volume group can have only one one-way replication session.
* A volume group can have one one disaster recovery session.
* Disaster recovery sessions cannot be configured as cascading sessions.
* For cascading replication, configure the upstream replication session with a shorter recovery point objective (RPO) than its downstream cascading session.&#x20;

## System resource limits

The following limits are generally enforced per DataPod. Run `system limitation-show` to verify the configured values for your environment.

| Resource                       | Maximum      |
| ------------------------------ | ------------ |
| Exposable volume snapshots     | 2,000        |
| Exposed NVMe-oF volumes        | 1,024        |
| Host groups                    | 64           |
| Hosts                          | 256          |
| IP addresses                   | 512          |
| NVMe-oF hosts                  | 50           |
| Replication peers              | 4            |
| Replication capacity           | 4,194,304 GB |
| Snapshot schedulers            | 20           |
| Users                          | 512          |
| Volume group capacity policies | 16           |
| Volsnaps                       | 16,384       |
| Volume groups                  | 1,000        |
| Volumes                        | 2,000        |

Additional DataPod limits include:

| Resource                             | Maximum    |
| ------------------------------------ | ---------- |
| Snapshots and views per volume group | 40         |
| Views per snapshot                   | 24         |
| Volume size                          | 128,000 GB |
| Volumes per volume group             | 256        |

## Plan your configuration

Before deploying or expanding a Silk environment:

1. Review cluster and DataPod sizing when selecting supported node, capacity, and VM configurations.
2. Review [DataPod Deployment Profiles](/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md) to choose a profile for your workload and understand any associated infrastructure requirements.&#x20;
3. Review the deployment documentation for your cloud provider to confirm networking, quota, regional availability, and feature prerequisites.&#x20;
4. For an existing DataPod, run `system limitation-show` to view the limits configured for that environment.&#x20;


---

# 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.silk.us/learn/references/silk-platform-configuration-limits.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.
