> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/security-and-support/technical-reference/network-whitelisting.md).

# Network Whitelisting

{% hint style="warning" %}
**Attention users: you may not be reading the full documentation**

This page contains additional hidden content tailored specifically to users. 

If you are a user, select the *Help* menu from within the system to return to this documentation tailored for your role and your system.
{% endhint %}

If you run in a filtered network environment, you may need to whitelist some domains to use the system.

### Required domains

The system requires access to the following domains:

* `app.<application domain>`
* `auth.<application domain>`
* `graphql.<application domain>`
* `api.<application domain>`

The system requires access to the following AWS service endpoints:

* `cognito-identity.ap-southeast-2.amazonaws.com`
* `cognito-idp.ap-southeast-2.amazonaws.com`
* `<application bucket>.s3.ap-southeast-2.amazonaws.com`

{% hint style="info" %}
Ask your system administrator for the exact value for `<application domain>`  and `<application bucket>.`&#x20;
{% endhint %}

### Recommended domains

The system also uses the following domains for system telemetry and map rendering, which are optional but recommended:<br>

* `tile.openstreetmap.org`
* `fonts.googleapis.com`
* `fonts.gstatic.com`
* Other map domains may be configured by administrators

### IP addresses

Our services do not map to fixed IP addresses due to the use of AWS serverless services. You should set your allowlist based on the domains.&#x20;

— &#x20;


---

# 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.cw.crisisworks.com/security-and-support/technical-reference/network-whitelisting.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.