> 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/products-and-core-concepts/silk-product-fundamentals/silk-flex-overview.md).

# Silk Flex Overview

Learn how Silk Flex orchestrates your Silk environment, from deploying and scaling DataPods to managing cloud resources and platform operations.

## Silk Flex Introduction

Flex gives cloud and infrastructure administrators a central place to manage the lifecycle of your organization's Silk environment. As application requirements change, you can use Flex to provision DataPods, adjust performance and capacity resources, validate your environment, and perform other platform operations.&#x20;

{% hint style="info" %}
**New to the Silk Cloud Data Platform?**

See [Silk Product Overview](/learn/get-to-know-silk/silk-product-overview.md) to learn how Flex works with Silk DataPods, Silk Echo, and Silk Clarity.&#x20;
{% endhint %}

### What Flex does

Flex connects the Silk platform with your cloud infrastructure, coordinating the resources that support your Silk environment. It dynamically composes and manages cloud resources as workload requirements change, helping you align infrastructure with application needs.

Use Flex to:

* **Deploy Silk infrastructure.** Configure a Flex cluster and provision DataPods using supported resources in your cloud environment.
* **Manage DataPod resources.** View your DataPods and their underlying infrastructure from a centralized interface.&#x20;
* **Scale performance and capacity.** Add or remove resources as workload requirements change, taking advantage of the DataPod architecture's ability to scale performance and capacity independently.&#x20;
* **Manage the DataPod lifecycle.** Modify, scale, migrate, and decommission DataPod infrastructure.&#x20;
* **Validate your environment.** Run supported validation workflows to verify connectivity and communication with required Silk and cloud services.&#x20;
* **Support platform upgrades.** Prepare Flex and its associated resources for Silk software upgrades and subsequent DataPod upgrade operations.
* **Access other Silk services.** Open individual DataPods for detailed data management and access Silk Echo when it's deployed in your environment.&#x20;

The current Flex management experience supports these operations through a web-based interface, with additional automation and programmatic management capabilities available for supported workflows.

### Automation and resilience

Flex does more than respond to administrator actions. It continuously helps manage the infrastructure supporting your Silk environment, reducing the amount of hands-on intervention required to keep DataPods available and operating efficiently.&#x20;

Silk automatically monitors system health and responds to infrastructure changes and component events. This includes proactively handling known cloud-provider maintenance, recovering from component failures, and adjusting resources as the environment changes. Many recovery and maintenance operations occur in the background while data services remain available.

This self-healing architecture helps minimize manual infrastructure management while maintaining DataPod availability and resiliency.&#x20;

### Flex and DataPods

Flex and DataPods have different responsibilities within the Silk platform.

{% tabs %}
{% tab title="Flex" %}
**Flex manages the infrastructure and lifecycle of your Silk environment.**

A Flex deployment contains one cluster, which organizes the DataPods and cloud resources managed through that Flex instance.&#x20;
{% endtab %}

{% tab title="DataPods" %}
**DataPods provide the data services used by your applications and databases.**&#x20;

Their resources are composed of c.nodes for performance and data processing, and m.nodes and d.nodes for capacity. Flex deploys and manages the cloud infrastructure supporting these components. &#x20;
{% endtab %}
{% endtabs %}

This separation allows Silk to independently adjust performance and capacity resources as workload requirements evolve.&#x20;

<figure><img src="https://4755877-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjI1rjszhUJU6LG8J53d0%2Fuploads%2F3jqeBb284uKS5buADewy%2Fimage.png?alt=media&amp;token=03aee964-39fe-4235-9afd-d4faa5e82803" alt=""><figcaption></figcaption></figure>

{% hint style="success" icon="lightbulb" %}
**Think of Flex as the orchestration layer and DataPods as the data layer.**&#x20;

Use Flex to deploy and manage DataPod infrastructure. Use DataPod management capabilities for operations involving volumes, hosts, snapshots, replication, connectivity, and other data services.&#x20;
{% endhint %}

The SDP Management Console is accessible from Flex for detailed administration of an individual DataPod.&#x20;

### Where Flex fits into the Silk platform

Flex is one part of the connected Silk product experience:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h3>Flex</h3></td><td>Orchestrates Silk infrastructure and manages DataPod lifecycles and their cloud resources.</td></tr><tr><td><h3>DataPods</h3></td><td>Deliver high-performance, scalable data services for application and database workloads.</td></tr><tr><td><h3>Echo</h3></td><td>Creates and manages full database copies for development, testing, analytics, AI, and other secondary workloads.</td></tr><tr><td><h3>Clarity</h3></td><td><p>Provides monitoring and analytics across the Silk </p><p>environment.</p></td></tr></tbody></table>

Together, these products separate infrastructure orchestration, data services, database copy workflows, and analytics while providing a connected management experience.

## Manage Your Environment with Flex

Flex provides a web-based management interface for viewing and operating your Silk infrastructure.&#x20;

From Flex, you can see the clusters and DataPods in your environment and inspect details like DataPod configuration, capacity, cloud provider, location, and underlying resources. An activity view provides visibility into ongoing operations like provisioning, scaling, and decommissioning.&#x20;

Administrative tools also support workflows such as environment validation, log collection, SSO configuration, application tokens, software image management, and upgrade preparation.&#x20;

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

For operations inside an individual DataPod, you can open the SDP Management Console from Flex. The DataPod management experience provides more granular control over resources like volumes, hosts, snapshots, replication, connectivity, and capacity policies.&#x20;

## Use Flex throughout the Silk lifecycle

You use Flex at several stages of your Silk environment's lifecycle.

### Deploy

A new Silk deployment begins with preparing your cloud environment and deploying Flex. Once Flex is available, it becomes the orchestration layer used to create and manage your DataPods.&#x20;

Deployment requirements and workflows vary by cloud provider, so follow the deployment instructions for your environment.

{% columns %}
{% column %}

#### [Deploy Silk on AWS](/deploy/deploy-on-aws/aws-deployment-overview.md)

{% endcolumn %}

{% column %}

#### [Deploy Silk on Azure](/deploy/deploy-on-azure/azure-deployment-overview.md)

{% endcolumn %}

{% column %}

#### [Deploy Silk on Google Cloud](/deploy/deploy-on-google-cloud/google-cloud-deployment-overview.md)

{% endcolumn %}
{% endcolumns %}

### Operate and scale

After deployment, Flex becomes the central interface for infrastructure-level DataPod operations.&#x20;

As your workloads evolve, you can scale DataPod resources to accommodate changes in performance or capacity. Silk's architecture separates these resource layers, allowing the infrastructure supporting a DataPod to evolve without requiring you to redesign the application environment.&#x20;

You may also use Flex for routine administrative workflows like validating connectivity, reviewing activities, downloading logs, managing cluster configuration, and accessing other Silk management experiences.&#x20;

### Upgrade

Flex also plays an important role in keeping your Silk environment current.&#x20;

During a Silk software upgrade, Flex itself is upgraded and prepares the system resources and software images required by the target release. DataPod upgrades are coordinated separately so that  data services remain available during the non-disruptive upgrade process.&#x20;

Silk Support coordinates the upgrade process and can help determine the required sequence for your environment. &#x20;

## Related resources

{% content-ref url="/pages/EhouDwXJNquf2nIc2p1R" %}
[Silk Product Overview](/learn/get-to-know-silk/silk-product-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/jbwHJE9XlrTdPS1lXZgj" %}
[Clusters and DataPods](/learn/products-and-core-concepts/datapod-architecture/clusters-and-datapods.md)
{% endcontent-ref %}

{% content-ref url="/pages/RACFGQWRzeDLCRkQE8tg" %}
[DataPod Deployment Profiles](/learn/products-and-core-concepts/datapod-architecture/datapod-deployment-profiles.md)
{% endcontent-ref %}

{% content-ref url="/spaces/7UwK9S9vo5qr2qGPjCUv/pages/I6xRg2jHBGXmxZTlP81r" %}
[Operate Your Silk Environment](/manage/operate-your-silk-environment.md)
{% endcontent-ref %}

{% content-ref url="/pages/vQzNzEEeYriLZWZiFaBJ" %}
[Non-Disruptive Upgrade (NDU)](/learn/data-management-concepts/non-disruptive-upgrade-ndu.md)
{% endcontent-ref %}

{% content-ref url="/spaces/FUE8J62COhtwFAOs7gSo" %}
[Releases](https://docs.silk.us/releases/)
{% 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/learn/products-and-core-concepts/silk-product-fundamentals/silk-flex-overview.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.
