> 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/deploy/deploy-on-aws/aws-deployment-overview.md).

# AWS Deployment Overview

Explore the AWS deployment architecture, understand the role of each component, and follow the path from environment preparation to storage provisioning.

Silk runs within your AWS environment, providing storage for your database and application workloads. A deployment includes Silk Flex for orchestration and management along with Silk DataPods that provide storage to connected hosts.

You deploy Flex through AWS Marketplace using AWS CloudFormation, then use Flex to create a cluster and provision DataPods. Before installation, prepare the AWS networking, permissions, images, and compute capacity required for your planned environment.

## AWS deployment architecture

The following architecture diagram shows how Silk Flex, DataPods, and application hosts fit within an AWS environment, along with Silk Clarity.

<figure><img src="https://3771785211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRoeFiUtkaS7g8f3vjz5%2Fuploads%2Fj2QLq0xUDHclFD7xRSLN%2Faws-architecture.png?alt=media" alt="Silk on AWS architecture: Silk Flex, DataPods, and application hosts inside the customer VPC, with outbound HTTPS to Silk Clarity"><figcaption><p>Silk on AWS deployment architecture</p></figcaption></figure>

Application hosts access storage provided by DataPods over iSCSI. Flex manages the deployment and lifecycle of Silk resources, while network connections support host access, communication between Silk components, and access to required external services.

## Key deployment components

<table><thead><tr><th width="269.6295166015625">Component</th><th>Deployment role</th></tr></thead><tbody><tr><td><strong>Amazon VPC and subnets</strong></td><td><p>Provide the network environment for Silk.</p><p>Deploy into an existing VPC with dedicated, pre-created subnets for Flex, external management, data traffic, and internal communication.</p></td></tr><tr><td><strong>Silk Flex</strong></td><td><p>Runs on an Amazon EC2 instance and orchestrates the Silk cluster and DataPods.</p><p>After installation, Flex continues to provision and manage resources within your AWS environment.</p></td></tr><tr><td><strong>Silk DataPods</strong></td><td><p>Provide storage to application hosts.</p><p>DataPod compute nodes (c.nodes) process storage I/O, while data nodes (d.nodes) provide the underlying storage resources. d.nodes are grouped into protected media nodes (m.nodes), and the compute and storage layers scale independently.</p></td></tr><tr><td><strong>Application hosts</strong></td><td>Run your databases and applications and connect to DataPod volumes over the data network.</td></tr><tr><td><strong>AWS deployment and infrastructure services</strong></td><td><ul><li><strong>AWS Marketplace</strong> - Provides the deployment package</li><li><strong>CloudFormation</strong> - Provides the initial Flex infrastructure</li><li><strong>EC2</strong> - Supplies compute resources</li><li><strong>IAM roles and policies</strong> - Authorize deployment and ongoing resource management</li></ul></td></tr><tr><td><strong>Supporting AWS and Silk services</strong></td><td><p>Silk Clarity provides monitoring, telemetry, and call home over outbound HTTPS. No inbound access from Silk is required.</p><p>Flex also uses AWS services such as the EC2 APIs, Amazon S3 (call home uploads), Amazon ECR (image pulls), and AWS Systems Manager. These connections must remain available after deployment.</p></td></tr></tbody></table>

## Network connections

The AWS deployment uses six dedicated subnets:

* **Flex:** Hosts the Flex VM management instance.
* **External Management:** Supports administrative access and management communication.
* **Data 1:** Carries storage traffic between application hosts and DataPods.
* **Data 2:** Carries replication traffic between DataPods.
* **Internal 1 and Internal 2:** Support communication between DataPod components.

All required Silk subnets must exist in the same VPC before installation. Plan their address space for both the initial deployment and expected growth.

Flex also requires connectivity to Silk services and AWS services used during deployment and operation. Depending on your network design, access to AWS services can use outbound internet connectivity or supported VPC endpoints. Because VPC endpoints reach only AWS services, your design must also include an outbound path to Silk Clarity.

## Deployment workflow

{% stepper %}
{% step %}

### Plan the deployment

Work with the Silk deployment team to complete the pre-installation site survey. Confirm the target AWS account and region, planned cluster and DataPod configuration, network design, and expected growth.

Use these decisions to validate instance availability and service quotas before deploying Flex.
{% endstep %}

{% step %}

### Prepare the AWS environment

Prepare the target VPC and required subnets, configure connectivity, validate IAM permissions, and verify access to the required Silk Amazon Machine Images (AMIs).

Obtain the environment-specific cluster configuration file from Silk Support after the deployment inputs are finalized. You'll upload this file when creating the cluster.
{% endstep %}

{% step %}

### Deploy Flex

Subscribe to the Silk offering in AWS Marketplace and launch the CloudFormation deployment. Supply the target VPC, Flex subnet, and instance configuration.

CloudFormation provisions the Flex instance and associated resources using the permissions configured for the deployment.
{% endstep %}

{% step %}

### Create the Silk cluster

Sign in to Silk Flex and upload the cluster configuration file. Select the cluster size, assign the prepared subnets, and configure cluster settings, including administrator credentials and call home.

The cluster size determines the deployment's supported scale and cannot be changed after cluster creation. Choose a size that accommodates your expected growth.
{% endstep %}

{% step %}

### Provision storage and connect hosts

After the cluster is created, use Flex to provision DataPods. Create the required storage resources, configure host access, and connect your application hosts using the applicable host connectivity guidance.
{% endstep %}
{% endstepper %}

## Next steps

For guidance on configuration planning, see [Plan a Silk Deployment](/deploy/plan-your-deployment/plan-a-silk-deployment.md) and [Cluster and DataPod Sizing](/deploy/plan-your-deployment/cluster-and-datapod-sizing.md).


---

# 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/deploy/deploy-on-aws/aws-deployment-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.
