> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/SaaS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/SaaS/configuration/application-configuration/reference-guides/deployment-options.md).

# Deployment Options

View the AWS regions in Immuta SaaS global segments and IP addresses that can be authorized so Immuta can connect to databases in a closed network

* **SaaS**: This recommended deployment option provides data access control through Immuta's integrations with automatic software updates and no infrastructure or maintenance costs.
* **Self-Managed**: When necessary, Immuta supports self-managed deployments for users who store their data on-premises or in private clouds, such as VPC. Users can connect to on-premises data sources and cloud data platforms that run on Amazon Web Services, Microsoft Azure, and Google Cloud Platform. [See our latest on-prem documentation for additional details](https://documentation.immuta.com/latest/configuration/self-managed-deployment).

{% hint style="success" %}
**Use the SaaS deployment option**

SaaS deployments get features first, have better tooling for support, and benefit from zero-downtime deployments.
{% endhint %}

### SaaS global segments

Immuta SaaS tenants are deployed into **global segments**, which are groups of cloud provider regions. Global segments are designed to help organizations with data locality restrictions meet their compliance needs, as data stored for a given tenant does not leave its global segment. Each global segment is built using multiple regions for disaster recovery purposes.

|        Name        | AWS regions                                                                                                                                                                                                                                    |
| :----------------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|  Asia Pacific (AP) | <ul><li>Sydney</li><li>Tokyo</li><li><a data-footnote-ref href="#user-content-fn-1">Seoul</a></li><li><a data-footnote-ref href="#user-content-fn-1">Singapore</a></li><li><a data-footnote-ref href="#user-content-fn-1">Mumbai</a></li></ul> |
|     Europe (EU)    | <ul><li>Frankfurt</li><li>Ireland</li><li>London</li><li><a data-footnote-ref href="#user-content-fn-1">Stockholm</a></li></ul>                                                                                                                |
| North America (NA) | <ul><li>N. Virginia</li><li>Oregon</li><li><a data-footnote-ref href="#user-content-fn-1">Ohio</a></li></ul>                                                                                                                                   |

### Connecting to databases running in closed networks

*The IP addresses below must be authorized in your network firewall configuration to allow Immuta to connect.*

#### Asia Pacific

* 3.106.147.24
* 13.114.123.176
* 13.238.102.94
* 13.55.39.43
* 13.55.159.66
* 18.176.33.125
* 35.74.60.182
* 35.79.88.51
* 52.63.167.163
* 52.68.224.114
* 54.79.122.121
* 52.196.249.32

#### Europe

* 3.9.86.222
* 3.72.210.214
* 3.74.143.208
* 3.126.62.66
* 13.41.25.70
* 18.158.34.136
* 18.169.27.181
* 18.169.63.243
* 18.169.76.225
* 18.195.8.208
* 35.158.87.229
* 35.179.66.5
* 52.16.117.91
* 52.211.82.12
* 54.171.9.121
* 63.34.27.228
* 63.34.155.116
* 108.129.45.8

#### North America

* 34.192.38.214
* 34.223.179.107
* 35.155.223.131
* 35.163.162.139
* 44.205.48.68
* 44.237.62.198
* 52.2.174.14
* 54.68.252.84
* 54.88.42.98
* 54.205.215.251
* 54.225.122.15
* 100.20.168.64

[^1]: Networking only.


---

# 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://documentation.immuta.com/SaaS/configuration/application-configuration/reference-guides/deployment-options.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.