> 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-networking-and-connectivity.md).

# Plan AWS Networking and Connectivity

Plan the subnets, IP address capacity, and connectivity required to deploy and operate Silk in your AWS environment.

Before deploying Silk on AWS, prepare the subnets and connectivity that Silk Flex and your DataPods need for deployment and ongoing operation. Your network must support communication between Silk components, storage access from database hosts, administrative access, and outbound connections to required Silk and AWS services.&#x20;

Work with your networking and security teams to confirm subnet sizing, routing, and access rules before deploying Flex.&#x20;

{% stepper %}
{% step %}

## Prepare your VPC and subnets

Silk on AWS deploys into an existing Amazon VPC using customer-created subnets. Before deployment, create all six required Silk subnets in the Availability Zone selected for your Silk environment.

All six subnets must be in the same VPC. Their CIDR ranges don't need to be contiguous, but they must not overlap. Route tables and security controls must allow the required communication between subnets.&#x20;

### Plan subnet address space

Plan your subnet address space around your intended cluster size: Small (`/24`), Medium (`/23`), or Large (`/21`). These values indicate the address space reservation associated with each cluster size. The following table provides the recommended size for each individual subnet:

<table><thead><tr><th width="129.6295166015625">Subnet</th><th width="320.222412109375">Purpose</th><th width="73.9259033203125">Small</th><th width="81.333251953125">Medium</th><th width="67.2591552734375">Large</th></tr></thead><tbody><tr><td><strong>Flex</strong></td><td>Hosts the Flex management instance.</td><td><code>/28</code></td><td><code>/28</code></td><td><code>/28</code></td></tr><tr><td><strong>External Management</strong></td><td>Supports management access, administrative operations, and communication with external services.</td><td><code>/28</code></td><td><code>/27</code></td><td><code>/25</code></td></tr><tr><td><strong>Data 1</strong></td><td>Carries storage access traffic between database hosts and DataPods.</td><td><code>/28</code></td><td><code>/27</code></td><td><code>/25</code></td></tr><tr><td><strong>Data 2</strong></td><td>Carries replication traffic between DataPods.</td><td><code>/28</code></td><td><code>/27</code></td><td><code>/25</code></td></tr><tr><td><strong>Internal 1</strong></td><td>Supports internal communication between c.nodes and d.nodes.</td><td><code>/26</code></td><td><code>/25</code></td><td><code>/23</code></td></tr><tr><td><strong>Internal 2</strong></td><td>Supports additional internal communication between c.nodes and d.nodes.</td><td><code>/26</code></td><td><code>/25</code></td><td><code>/23</code></td></tr></tbody></table>

{% hint style="info" %}
**Plan additional IP capacity for VPC interface endpoints.**

If you use VPC interface endpoints, allocate a larger Flex subnet (for example, `/27` ) to accommodate the additional elastic network interfaces (ENIs).&#x20;
{% endhint %}

Cluster size determines the maximum number of Silk resources you can deploy, and it can't be changed after the cluster is created. Choose a size that supports your expected growth.&#x20;

### Plan network communication paths

Your network configuration must support the following communication paths:

<table><thead><tr><th width="188.5186767578125">Communication paths</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Database hosts</strong> <i class="fa-arrow-right">:arrow-right:</i> <strong>DataPods</strong></td><td>Provide connectivity to the Data 1 subnet for iSCSI storage access.</td></tr><tr><td><strong>Between DataPod components</strong></td><td>Allow the intra-cluster traffic required for data operations, internal services, and high availability.</td></tr><tr><td><strong>Between DataPods</strong></td><td>Allow replication traffic between DataPods over the Data 2  subnet.</td></tr><tr><td><strong>Flex</strong> <i class="fa-arrow-right">:arrow-right:</i> <strong>Silk subnets</strong></td><td>Allow Flex to reach all Silk subnets for deployment and management operations.</td></tr><tr><td><strong>Silk components</strong> <i class="fa-arrow-right">:arrow-right:</i> <strong>external services</strong></td><td>Provide outbound connectivity from the Flex and External Management subnets to the services required for their operations.</td></tr><tr><td><strong>Administrators</strong> <i class="fa-arrow-right">:arrow-right:</i> <strong>Flex</strong></td><td>Provide administrative access to Flex.</td></tr></tbody></table>

Use route tables, security groups, network access control lists (NACLs), and any additional network controls to support these paths. Routing alone isn't sufficient if security controls block the required traffic.&#x20;

For the complete subnet-by-subnet port and protocol requirements, see the [Silk on AWS Deployment Guide](https://support.silk.us/sys/document/preview/Silk-on-AWS-Deployment-Guide-260506104227604.pdf) (requires Silk Support Portal access).&#x20;

Flex administrative access uses TCP ports 22 and 443. Restrict this access according to your organization's security policies.&#x20;
{% endstep %}

{% step %}

## Choose an outbound connectivity method

Configure outbound connectivity before deploying Flex. Silk uses outbound connections for infrastructure operations, monitoring, call home uploads, and image delivery.&#x20;

The Flex subnet requires access to the applicable Silk and AWS services listed in the next step. The External Management subnet also requires access to Amazon S3 and Amazon ECR for supporting operations.

Choose internet-based access or private access through AWS VPC endpoints for connections to AWS services. Both approaches also require outbound HTTPS access to Silk Clarity.

### Internet-based access

For outbound connectivity, we recommend internet access through a NAT gateway or equivalent egress configuration.&#x20;

Ensure the required subnets have a valid outbound route and that security groups, NACLs, firewalls, and proxies allow the required HTTPS traffic over TCP port 443.&#x20;

### Private access to AWS services

AWS VPC endpoints provide connectivity to AWS services only (including AWS Systems Manager, EC2, ECR, and S3). Your outbound configuration must also allow HTTPS access to `hub.clarity.silk.us` over TCP port 443.&#x20;
{% endstep %}

{% step %}

## Allow access to required services

Account for the following destinations when planning outbound access:

<table><thead><tr><th width="221.1112060546875">Service</th><th>Used for</th></tr></thead><tbody><tr><td>Silk Clarity<br>(<code>hub.clarity.silk.us</code>)</td><td>Monitoring, telemetry, and platform communication </td></tr><tr><td>AWS service APIs<br>(like EC2)</td><td>Deployment and infrastructure operations</td></tr><tr><td>Amazon S3</td><td>Call home uploads</td></tr><tr><td>Amazon ECR</td><td>Container image pulls</td></tr><tr><td>AWS Systems Manager (SSM)</td><td>Deployment and lifecycle operations</td></tr></tbody></table>

On AWS, call home uploads use a region-specific S3 bucket. Confirm that the bucket is reachable from the Flex deployment environment.

DNS resolution must also be enabled and working within the VPC so that required service endpoints can be resolved.
{% endstep %}

{% step %}

## Confirm network readiness

Before deploying Flex, confirm that:

* [ ] All six subnets exist in the target VPC and intended Availability Zone.
* [ ] Subnet CIDR ranges don't overlap and provide enough available IP addresses for deployment, endpoints, and growth.
* [ ] Route tables and security controls allow required communication between Flex, DataPod components, and database hosts.&#x20;
* [ ] Administrators can access Flex.
* [ ] The Flex and External Management subnets can reach their required outbound destinations.
* [ ] DNS can resolve the required service endpoints.&#x20;

Keep the finalized subnet design and cluster size consistent with the information provided to Silk Support for your cluster file. If key inputs change after the file is generated, request a new cluster file.&#x20;
{% endstep %}
{% endstepper %}


---

# 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-networking-and-connectivity.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.
