> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/dragen-stratamap/references/network-requirements.md).

# Network Requirements

Illumina Connected Software (e.g. BaseSpace Sequence Hub, Illumina Connected Analytics \[ICA], and Illumina Connected Multiomics \[ICM]) rely on cloud services for login, sequencing, and analysis.

The Illumina Spatial Solutions product utilizes Illumina Connected Software throughout the workflow. The following must be enabled to utilize Illumina cloud software.

• Outbound Connectivity on TCP Port 443:

\- All domains listed in this guide require secure (HTTPS) outbound access over TCP port 443.

• Allowed Domains:

\- Ensure that any proxy or firewall rules do not block secure connections (HTTPS) to the listed domains.

### Common Domains

The following domains are shared across all Illumina services and must always be reachable

* ica.illumina.com
* connected.illumina.com
* login.illumina.com
* \*.login.illumina.com

### BaseSpace Sequence Hub

Images processed using the Illumina Spatial Image Tool can be directly exported to BaseSpace Sequence Hub where they are selected for subsequent sequencing run planning and analysis steps. To enable this feature, region specific domains must be accessible by your workstation and sequencing instrument.

<table><thead><tr><th width="168">Region</th><th>Domain</th></tr></thead><tbody><tr><td>All</td><td>instruments.sh.basespace.illumina.com</td></tr><tr><td>US East (N. Virginia)</td><td><p>api.basespace.illumina.com</p><p>basespace-data-east.s3.amazonaws.com</p><p>basespace-data-east.s3.us-east-1.amazonaws.com</p><p>basespace-data-east.s3-external-1.amazonaws.com</p><p>stratus-gds-use1.s3.amazonaws.com</p><p>stratus-gds-use1.s3.us-east-1.amazonaws.com</p><p>use1.platform.illumina.com</p></td></tr><tr><td>Europe (London)</td><td><p>api.euw2.sh.basespace.illumina.com</p><p>eu-sh-euw2-prod-seq-hub-data-bucket.s3.amazonaws.com</p><p>eu-sh-euw2-prod-seq-hub-data-bucket.s3.eu-west-2.amazonaws.com</p><p>euw2.platform.illumina.com</p><p>euw2.sh.basespace.illumina.com</p><p>stratus-gds-euw2.s3.amazonaws.com</p><p>stratus-gds-euw2.s3.eu-west-2.amazonaws.com</p></td></tr><tr><td>Europe (Frankfurt)</td><td><p>api.euc1.sh.basespace.illumina.com</p><p>euc1.platform.illumina.com</p><p>euc1.sh.basespace.illumina.com</p><p>euc1-prd-seq-hub-data-bucket.s3.amazonaws.com</p><p>euc1-prd-seq-hub-data-bucket.s3.eu-central-1.amazonaws.com</p><p>stratus-gds-euc1.s3.amazonaws.com</p><p>stratus-gds-euc1.s3.eu-central-1.amazonaws.com</p></td></tr><tr><td>Singapore</td><td>api.aps1.sh.basespace.illumina.com<br>aps1-sh-prd-seq-hub-data-bucket.s3.amazonaws.com<br>aps1-sh-prd-seq-hub-data-bucket.s3.ap-southeast-1.amazonaws.com<br>aps1.platform.illumina.com<br>aps1.sh.basespace.illumina.com<br>stratus-gds-aps1.s3.amazonaws.com<br>stratus-gds-aps1.s3.ap-southeast-1.amazonaws.com</td></tr></tbody></table>

### ICA

In addition to the common domain (ica.illumina.com, listed above), ICA pipelines and clients require outbound connections to the following region-specific domains for storage

<table><thead><tr><th width="283">Region</th><th>URL</th></tr></thead><tbody><tr><td>United States (US)</td><td><p>stratus-gds-use1.s3.us-east-1.amazonaws.com</p><p>stratus-gds-use1.s3.amazonaws.com</p></td></tr><tr><td>United Kingdom (GB)</td><td><p>stratus-gds-euw2.s3.eu-west-2.amazonaws.com</p><p>stratus-gds-euw2.s3.amazonaws.com</p></td></tr><tr><td>Germany (EU)</td><td><p>stratus-gds-euc1.s3.eu-central-1.amazonaws.com</p><p>stratus-gds-euc1.s3.amazonaws.com</p></td></tr><tr><td>Singapore (SG)</td><td>stratus-gds-aps1.s3.ap-southeast-1.amazonaws.com<br>stratus-gds-aps1.s3.amazonaws.com</td></tr></tbody></table>

### ICM

Illumina Connected Multiomics (ICM) requires access to the following domain, in addition to the common domains listed above.

<table><thead><tr><th width="283">Region</th><th>URL</th></tr></thead><tbody><tr><td>United States (US)</td><td>use1.icm.illumina.com<br>*.use1.icm.illumina.com</td></tr><tr><td>United Kingdom (GB)</td><td><p>euw2.icm.illumina.com</p><p>*.euw2.icm.illumina.com</p></td></tr><tr><td>Germany (EU)</td><td><p>euc1.icm.illumina.com</p><p>*.euc1.icm.illumina.com</p></td></tr><tr><td>Singapore (SG)</td><td>aps1.icm.illumina.com<br>*.aps1.icm.illumina.com</td></tr></tbody></table>

### Summary/Checklist to Prepare your Network

1\. Allow Common Domains

\- ica.illumina.com

\- connected.illumina.com

\- login.illumina.com

\- \*.login.illumina.com

2\. Allow Region-Specific Domains for:

\- BaseSpace Sequence Hub

\- ICA

\- ICM

3\. Verify Proxy/Firewall Rules

\- Ensure no secure (HTTPS) connections are blocked or disrupted by network filtering.


---

# 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://help.bioinsight.illumina.com/dragen-stratamap/references/network-requirements.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.