> 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/connected-analytics/reference/r-resources/r-networksettings.md).

# Network Settings

The **Platform Core service connector client** and the **Platform Core CLI** use HTTPS on TCP port 443. To use the clients successfully, you must be able to make outbound connections on TCP port 443.

**Pipelines** can only reach out to the internet on ports 80 and 443.

## Locations

The following URLs must be accessible via TCP port 443.

<table><thead><tr><th width="250.0078125">Region</th><th>URL</th></tr></thead><tbody><tr><td>All</td><td>ica.illumina.com</td></tr><tr><td>Australia (AU)</td><td>stratus-gds-aps2.s3.ap-southeast-2.amazonaws.com<br>stratus-gds-aps2.s3.amazonaws.com</td></tr><tr><td>Canada (CA)</td><td>stratus-gds-cac1.s3.ca-central-1.amazonaws.com<br>stratus-gds-cac1.s3.amazonaws.com</td></tr><tr><td>Germany (EU)</td><td>stratus-gds-euc1.s3.eu-central-1.amazonaws.com<br>stratus-gds-euc1.s3.amazonaws.com</td></tr><tr><td>India (IN)</td><td>stratus-gds-aps3.s3.ap-south-1.amazonaws.com<br>stratus-gds-aps3.s3.amazonaws.com</td></tr><tr><td>Indonesia (ID)</td><td>stratus-gds-aps4.s3.ap-southeast-3.amazonaws.com<br>stratus-gds-aps4.s3.amazonaws.com</td></tr><tr><td>Israel (IL)</td><td>stratus-gds-ilc1.s3.il-central-1.amazonaws.com</td></tr><tr><td>Japan (JP)</td><td>stratus-gds-apn1.s3.ap-northeast-1.amazonaws.com<br>stratus-gds-apn1.s3.amazonaws.com</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><tr><td>South Korea (KR)</td><td>stratus-gds-apn2.s3.ap-northeast-2.amazonaws.com<br>stratus-gds-apn2.s3.amazonaws.com</td></tr><tr><td>United Kingdom (GB)</td><td>stratus-gds-euw2.s3.eu-west-2.amazonaws.com<br>stratus-gds-euw2.s3.amazonaws.com</td></tr><tr><td>United Arab Emirates (AE)</td><td>stratus-gds-mec1.s3.me-central-1.amazonaws.com<br>stratus-gds-mec1.s3.amazonaws.com</td></tr><tr><td>United States East (US-N. Virginia)</td><td>stratus-gds-use1.s3.us-east-1.amazonaws.com<br>stratus-gds-use1.s3.amazonaws.com</td></tr><tr><td>United States West (US-Oregon)</td><td>stratus-gds-usw2.s3.us-west-2.amazonaws.com<br>stratus-gds-usw2.s3.amazonaws.com</td></tr><tr><td>Taiwan (TW)</td><td>stratus-gds-ape2.s3.ap-east-2.amazonaws.com<br>stratus-gds-ape2.s3.amazonaws.com</td></tr></tbody></table>

## **Bench**

The Following URLs must be accessible to connect to Platform Core Bench

<table><thead><tr><th width="346.17578125">Region</th><th>URL</th></tr></thead><tbody><tr><td>Asia-Pacific East (Taipei)</td><td>ape2-bench.platform.illumina.com</td></tr><tr><td>Asia-Pacific Southeast (Singapore)</td><td>aps1-bench.platform.illumina.com</td></tr><tr><td>Asia-Pacific Southeast (Sydney)</td><td>aps2-bench.platform.illumina.com</td></tr><tr><td>Asia-Pacific Southeast (Jakarta)</td><td>aps4-bench.platform.illumina.com</td></tr><tr><td>Asia-Pacific Southeast (Mumbai)</td><td>aps3-bench.platform.illumina.com</td></tr><tr><td>Asia-Pacific Northeast (Tokyo)</td><td>apn1-bench.platform.illumina.com</td></tr><tr><td>Asia-Pacific Northeast (Seoul)</td><td>apn2-bench.platform.illumina.com</td></tr><tr><td>Canada Central</td><td>cac1-bench.platform.illumina.com</td></tr><tr><td>Europe Central (Frankfurt)</td><td>euc1-bench.platform.illumina.com</td></tr><tr><td>Europe West (London)</td><td>euw2-bench.platform.illumina.com</td></tr><tr><td>Israel Central</td><td>ilc1-bench.platform.illumina.com</td></tr><tr><td>Middle East Central (United Arab Emirates)</td><td>mec1-bench.platform.illumina.com</td></tr><tr><td>United States East (N. Virginia)</td><td>use1-bench.platform.illumina.com</td></tr><tr><td>United States West (Oregon)</td><td>usw2-bench.platform.illumina.com</td></tr></tbody></table>

## S3 Regions

<table><thead><tr><th width="288.01953125">Platform Core Project Region</th><th>AWS Region</th></tr></thead><tbody><tr><td>Australia (AU)</td><td>ap-southeast-2</td></tr><tr><td>Canada (CA)</td><td>ca-central-1</td></tr><tr><td>Germany (EU)</td><td>eu-central-1</td></tr><tr><td>India (IN)</td><td>ap-south-1</td></tr><tr><td>Indonesia (ID)</td><td>ap-southeast-3</td></tr><tr><td>Israel (IL)</td><td>il-central-1</td></tr><tr><td>Japan (JP)</td><td>ap-northeast-1</td></tr><tr><td>Singapore (SG)</td><td>ap-southeast-1</td></tr><tr><td>South Korea* (KR)</td><td>ap-northeast-2</td></tr><tr><td>United Arab Emirates (AE)</td><td>me-central-1</td></tr><tr><td>UK (GB)</td><td>eu-west-2</td></tr><tr><td>United States (US-N. Virginia)</td><td>us-east-1</td></tr><tr><td>United States (US-Oregon)</td><td>us-west-2</td></tr></tbody></table>

### Mapping S3 Locations to IP Addresses

Amazon provides a [JSON-based list ](https://ip-ranges.amazonaws.com/ip-ranges.json)of IP address ranges assigned to and used by AWS. **This is not a static list**, but can change several times per week. To map the S3 storage locations to IP addresses, this list must be actively polled and your security rules must be updated accordingly.

You can use [jq](https://jqlang.org/) to extract the addresses of your S3 storage locations as follows

1. If you do not have jq installed, install it from the [official source](https://jqlang.org/download/).
2. Download the [amazon IP address list](https://ip-ranges.amazonaws.com/ip-ranges.json).
3. Open your command prompt and navigate to the location of your address list
4. Run the following command to find the IP address ranges that AWS uses for S3 in the desired region. In this example we use the us-east-1 region.

{% code overflow="wrap" expandable="true" %}

```
jq -r '.prefixes[] | select(.region=="us-east-1") | select(.service=="S3") | .ip_prefix' < ip-ranges.json jq -r '.prefixes[] | select(.region=="us-east-1") | select(.service=="S3") | .ip_prefix' < ip-ranges.json
```

{% endcode %}


---

# 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/connected-analytics/reference/r-resources/r-networksettings.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.