> 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/manage/operate-your-silk-environment.md).

# Operate Your Silk Environment

Find where to handle everyday Silk administration, from managing access and provisioning storage to scaling capacity, protecting data, and planning upgrades.

After deployment, you manage your Silk environment through two interfaces:

* **Flex** manages the infrastructure and lifecycle of your DataPods, including scaling, validation, and upgrade preparation.
* The **SDP Management Console** manages the resources inside an individual DataPod, including volumes, hosts, snapshots, replication, connectivity, and user access.

This page describes the most common day-to-day tasks, where each one happens, and where to find more information.

{% hint style="info" %}
Available operations can vary by cloud provider, Silk version, configuration, and user role.
{% endhint %}

## Choose the right tool

Use this table to find where the most common operational tasks are performed:

<table data-search="false"><thead><tr><th width="181.4815673828125">Interface</th><th>Task</th></tr></thead><tbody><tr><td rowspan="4"><strong>Flex</strong></td><td>Scale DataPod performance or capacity</td></tr><tr><td>Modify, migrate, or decommission a DataPod</td></tr><tr><td>Validate connectivity and collect logs</td></tr><tr><td>Configure single sign-on and application tokens</td></tr><tr><td rowspan="5"><strong>SDP Management Console</strong></td><td>Create volumes, volume groups, hosts, and volume mappings</td></tr><tr><td>Configure snapshots, snapshot schedules, and retention policies</td></tr><tr><td>Configure replication peers and sessions</td></tr><tr><td>Manage DataPod users, roles, and audit logs</td></tr><tr><td>Set capacity policies</td></tr></tbody></table>

You can open the SDP Management Console for any DataPod directly from Flex. Silk also supports programmatic DataPod management through the command-line interface and the [REST API](https://docs.silk.us/api-reference/).

## Manage access

Each DataPod controls access through user roles in the SDP Management Console:

{% tabs %}
{% tab title="Admin" %}
Manages DataPod resources and system configuration, but can't perform security administration.
{% endtab %}

{% tab title="Security" %}
Manages users, roles, passwords, security settings, and audit logs.
{% endtab %}

{% tab title="Viewer" %}
Provides read-only access to configuration, health, events, capacity, and performance.
{% endtab %}

{% tab title="mgmt-app" %}
Supports applications and integrations that manage volumes and volume mappings.
{% endtab %}
{% endtabs %}

Assign each user the least-privileged role that covers their responsibilities. For example, give monitoring teams and auditors the Viewer role.

Flex also supports SAML single sign-on through Okta or Microsoft Entra ID, and application tokens for integrations.

For more information, see [SDP Management Console Overview](/learn/products-and-core-concepts/datapod-architecture/sdp-management-console-overview.md) and [Silk Security Overview](/manage/protect-your-environment/silk-security-overview.md).

## Provision storage

Volumes provide storage to your applications and databases. Volume groups organize related volumes so you can manage their capacity, snapshots, and replication together.

To make storage available to a workload, use the SDP Management Console to:

1. Create a volume group and the volumes it contains.
2. Define the hosts, or host groups, that need access.
3. Map the volumes to those hosts.

Hosts connect to DataPods over iSCSI. You can configure CHAP authentication to help prevent unauthorized initiators from connecting.

For more information, see [Volumes and Volume Groups](/learn/data-management-concepts/volumes-and-volume-groups.md).

## Manage capacity

The SDP Management Console dashboard shows each DataPod's allocated and physical capacity, along with capacity trends and thresholds. Use capacity policies to define how the DataPod responds as capacity is consumed.

When workload requirements change, use Flex to scale the DataPod. Silk scales performance and capacity independently: c.nodes provide performance, while m.nodes and d.nodes provide capacity.

For more information, see:

* [Plan DataPod Capacity](/deploy/plan-your-deployment/plan-datapod-capacity.md)
* [Silk Platform Configuration Limits](/learn/references/silk-platform-configuration-limits.md)
* [Monitor Your Silk Environment](/manage/monitor-and-automate-silk/monitor-your-silk-environment.md)

## Protect your data

Use the SDP Management Console to configure data protection for your volume groups:

* **Snapshots** create recovery points. Snapshot schedules and retention policies automate when they're taken and how long they're kept.
* **Replication** copies volume groups to a peer DataPod to support disaster recovery.

For more information, see [Replication and Recovery](/manage/protect-your-environment/replication-and-recovery.md).

## Maintain the platform

**Upgrades.** Silk Support coordinates software upgrades. Flex is upgraded first and prepares the resources the target release needs, and DataPods are then upgraded non-disruptively so data services remain available. For more information, see [Non-Disruptive Upgrade (NDU)](/learn/data-management-concepts/non-disruptive-upgrade-ndu.md).

**Remote support access.** SecureLink provides an optional remote connection for Silk Support troubleshooting and upgrades. Once configured, it's disabled by default, and you control when to enable it and for how long. For more information, see [Silk Security Overview](/manage/protect-your-environment/silk-security-overview.md).

**Health and performance.** Review health, events, performance, and replication status regularly so you can address issues early. For more information, see [Monitor Your Silk Environment](/manage/monitor-and-automate-silk/monitor-your-silk-environment.md).

## Related resources

{% content-ref url="/spaces/jI1rjszhUJU6LG8J53d0/pages/Bdgy6vFNs8TdYaGxD5vF" %}
[Silk Flex Overview](/learn/products-and-core-concepts/silk-product-fundamentals/silk-flex-overview.md)
{% endcontent-ref %}

{% content-ref url="/spaces/jI1rjszhUJU6LG8J53d0/pages/dJ71QO0yxR6EjT0w1Vfw" %}
[SDP Management Console Overview](/learn/products-and-core-concepts/datapod-architecture/sdp-management-console-overview.md)
{% endcontent-ref %}


---

# 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/manage/operate-your-silk-environment.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.
