> 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/plan-aws-resources-and-permissions.md).

# Plan AWS Resources and Permissions

Prepare AWS capacity, images, permissions, and other resources for a Silk deployment.

Before deploying Silk on AWS, confirm that your AWS environment has the resources, capacity, and permissions required for your planned configuration. Early planning helps prevent delays when you deploy Flex, create a cluster, and provision DataPods.

Work with the Silk deployment team to complete the pre-installation site survey and identify the requirements for your environment. Use the guidance below to prepare your AWS account before beginning the AWS Marketplace deployment.&#x20;

{% stepper %}
{% step %}

## Define your deployment configuration

Your deployment configuration determines the AWS resources and capacity you need. As part of the pre-installation site survey, work with Silk to confirm:

* Target AWS account, region, and Availability Zone
* Expected cluster size and DataPod configuration
* Required instance types for Flex, c.nodes, and d.nodes
* Target VPC and subnet design
* Networking and connectivity requirements
* Expected growth and future scaling needs

Complete the site survey before requesting a cluster file from Silk Support. The cluster file contains configuration details specific to your environment and is required to create a Silk cluster.&#x20;

{% hint style="warning" %}
If key inputs change after Silk generates the file, such as subnet CIDR ranges or cluster size, you'll need to request a new one.
{% endhint %}
{% endstep %}

{% step %}

## Plan compute capacity and quotas

Silk uses Amazon EC2 instances for Flex and for DataPod c.nodes and d.nodes. Before deployment, confirm that the required instance types are available in your selected region and Availability Zone and that your AWS account has sufficient quota.&#x20;

{% hint style="info" %}
**Instance availability and quota are separate considerations.**

An instance type may be offered in your target location, but your deployment can still be blocked if your account doesn't have enough quota or AWS capacity is constrained.
{% endhint %}

When planning capacity:

* Include Flex and all planned DataPods and node types.
* Account for both the initial deployment and anticipated growth.&#x20;
* Review the applicable EC2 quotas for the instance families and vCPUs your deployment requires.
* Request any needed quota increases ahead of the deployment window.&#x20;
* Coordinate with Silk early if you're planning a larger environment.&#x20;

You can review your current quotas and request increases through **AWS Service Quotas**.&#x20;

### Consider sustained bandwidth

Some EC2 instance types provide higher network bandwidth for short periods but operate at a lower baseline during sustained activity. This behavior can affect workloads that consistently generate high network or storage throughput.

When selecting instance types, consider both peak and sustained workload requirements. This is especially relevant for sustained sequential I/O, workloads with non-compressible data, and smaller instance types. Bandwidth behavior varies by instance family, size, and deployment architecture.&#x20;

For sustained high-throughput workloads, consider larger instance sizes.&#x20;
{% endstep %}

{% step %}

## Prepare networking resources

Silk on AWS is deployed into an **existing Amazon VPC**. Before deployment, prepare the VPC, subnets, and connectivity required for Flex and cluster communication.

### VPC and subnets

Silk doesn't create subnets during installation, so all six required subnets must exist in the target VPC before deployment. Confirm that:

* The VPC is in the selected region and its CIDR range doesn't overlap with connected networks
* All required subnets are created in advance in the intended Availability Zone
* Subnet CIDR ranges and available IP addresses support the initial deployment and planned scaling

### Connectivity

Flex needs to reach Silk services and AWS services during deployment and ongoing operations. Confirm that:

* Routing allows communication between Silk subnets, from application hosts to the Data 1 subnet, and outbound to required services.&#x20;
* The Flex and External Management subnets have an outbound path to Silk Clarity and required AWS services (through NAT Gateway or VPC endpoints)
* DNS resolution is enabled in the VPC

{% hint style="info" %}
If you use VPC endpoints for outbound access, plan a larger Flex subnet (e.g., `/27`) to make room for the endpoint network interfaces.
{% endhint %}
{% endstep %}

{% step %}

## Plan IAM access

Silk deployment uses AWS CloudFormation to create and manage resources. The identity performing the deployment must have the permissions needed to launch the deployment and create or configure the required AWS resources.

You can deploy using permissions assigned directly to the deploying user or use a **predefined IAM role** (recommended). In either case, review the approach with your AWS administrator and Silk before deployment.&#x20;

The deployment requires capabilities across these areas:

<table><thead><tr><th width="187.0369873046875">Area</th><th>Access to plan for</th></tr></thead><tbody><tr><td><strong>AWS Marketplace</strong></td><td>Subscribe to and launch the Silk offering.</td></tr><tr><td><strong>CloudFormation</strong></td><td>Create and manage the stacks used for deployment.</td></tr><tr><td><strong>Amazon EC2</strong></td><td>Launch and manage instances, review instance availability, and access or copy the required AMIs.</td></tr><tr><td><strong>Networking</strong></td><td>Read the target VPC configuration and perform the networking operations required by the deployment.</td></tr><tr><td><strong>IAM</strong></td><td>Create or assign the roles and instance profiles required for deployment, including permission to pass roles where applicable. </td></tr></tbody></table>

During deployment, CloudFormation creates the IAM role, instance profile, and permissions that Flex uses to interact with AWS resources.&#x20;

{% hint style="info" %}
If your organization restricts administrative access, work with Silk Support to validate the exact permissions and any predefined roles needed for your environment.&#x20;

Confirm that SCPs or tagging poicies won't block the resources CloudFormation creates.&#x20;
{% endhint %}
{% endstep %}

{% step %}

## Prepare access to the Silk images

Silk provides the c.node and d.node images as Amazon Machine Images (AMIs) from a Silk-managed AWS account. Before creating DataPods, confirm that the required images have been shared with your AWS account and are available in the region where Flex is deployed.&#x20;

If the required images are unavailable, cluster creation may succeed, but DataPod creation will fail. Silk AMIs are version-specific and must be available in the region where you deploy Flex. Contact [Silk Support](https://support.silk.us) to confirm you have the latest images or if you need help accessing/copying them.
{% endstep %}

{% step %}

## Confirm your AWS Marketplace subscription

The Silk deployment package is available through AWS Marketplace. Before launching the deployment, confirm that:

* Your AWS account is subscribed to the Silk offering
* The subscription is active for the target region
* The deploying identity has permission to launch the Marketplace product
  {% endstep %}
  {% endstepper %}

For complete deployment requirements and instructions, see the [Silk on AWS Deployment Guide](https://support.silk.us/sys/document/preview/Silk-on-AWS-Deployment-Guide-260506104227604.pdf).


---

# 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/plan-aws-resources-and-permissions.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.
