> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/connectivity.md).

# Prerequisites and Connectivity

To ensure a smooth onboarding process, configure your environment to allow communication with essential Veza IP addresses and email domains.

#### Domain Filtering

The following domains should be allowed through email filters, proxies, and firewalls:

* **Email notifications**: When a Veza local account is created, an email is sent to the user to create their password. This email comes from `noreply@vezacloud.com`.
* **Veza tenant domain**: The domain for your Veza instance will be `*.vezacloud.com`, where `*` represents your Veza tenant name.
* **Insight Point**: If using an [Insight Point](/4yItIzMvkpAvMVFAamTf/integrations/connectivity/insight-point.md), allow access to `public.ecr.aws` for the initial image pull during installation (it is not required for upgrades). Controlled networks can instead pull the image from the tenant domain; see [Pulling Insight Point images from your tenant domain](/4yItIzMvkpAvMVFAamTf/integrations/connectivity/insight-point/insight-point-tenant-registry.md).

#### Firewall Rules and Filters

Veza integrations connect to data sources across your on-premise environment, cloud providers, and SaaS applications. Most integrations use API tokens or other credentials to query for authorization metadata.

By default, integrations run on the Veza SaaS platform. If your organization filters inbound connections to applications you want to integrate with Veza, allow traffic from the Veza NAT Gateway IP addresses for your deployment region in your firewall rules or filters.

{% hint style="info" %}
Only allowlist the IP addresses for your specific deployment region, which you can confirm by contacting your Customer Success Manager or Veza support.
{% endhint %}

For the full list of regions where Veza hosts its SaaS platform, see [Supported Regions](/4yItIzMvkpAvMVFAamTf/administration/administration/supported-regions.md).

| Region        | Cluster   | NAT Gateway IP Addresses                            |
| ------------- | --------- | --------------------------------------------------- |
| North America | Canada    | `15.223.136.14`, `15.157.157.132`, `3.96.111.11`    |
| North America | U.S. East | `18.221.224.60`, `3.18.38.252`, `52.14.66.128`      |
| North America | U.S. West | `44.245.33.160`, `44.234.11.33`, `54.70.152.6`      |
| EMEA          | UK        | `18.133.37.58`, `18.171.45.61`, `13.42.176.0`       |
| EMEA          | Germany   | `3.68.250.84`, `63.177.202.135`, `3.68.15.78`       |
| Asia-Pacific  | Japan     | `175.41.247.160`, `13.159.240.114`, `57.181.153.43` |
| Asia-Pacific  | Singapore | `47.128.164.72`, `47.128.160.212`, `52.221.27.137`  |
| Asia-Pacific  | Australia | `54.206.248.16`, `13.238.99.75`, `3.25.20.138`      |
| Asia-Pacific  | India     | `3.7.143.9`, `13.207.166.77`, `3.109.43.115`        |

#### Insight Point Connectivity

When configuring an integration, you can choose to use an Insight Point managed by your organization. An Insight Point allows querying authorization metadata within your environment, with no inbound calls from your Veza tenant to integrated data sources.

When using this option, outbound traffic must be enabled, to allow the Insight Point to transmit authorization metadata securely to your Veza tenant. The Insight Point must also be able to pull images from the Veza ECR repository, as detailed in [Insight Point: Ports and Connectivity](/4yItIzMvkpAvMVFAamTf/integrations/connectivity/insight-point.md#ports-and-connectivity).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/connectivity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.