> ## Documentation Index
> Fetch the complete documentation index at: https://docs.envzero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IP addresses

> env zero IP addresses across us-east-1 and us-west-2 for allowlisting in VCS providers and cloud resources, with a Terraform provider for dynamic IP lookups.

Use these IP addresses to configure your VCS allowed IP list or firewall rules for cloud resources. env zero calls your services through these addresses. They are also used for SaaS runners.

Prioritize the us-east-1 addresses. env zero uses us-west-2 only during a failover event.

| Availability zone | IP addresses |
| :- | :- |
| us-east-1a | 18.214.210.123, 44.195.170.230 |
| us-east-1b | 44.212.144.113, 52.73.227.111 |
| us-east-1c | 3.222.51.117, 3.226.24.146 |
| us-east-1d | 3.209.36.240, 54.165.19.49 |
| us-east-1e | 44.205.134.220 |
| us-east-1f | 18.214.49.142, 54.88.50.2 |
| us-west-2a | 35.81.146.242, 54.68.137.240 |
| us-west-2b | 44.228.227.2, 44.240.181.100 |
| us-west-2c | 35.85.88.233, 54.149.16.114 |
| us-west-2d | 44.227.16.37 |

You can also use the [env zero Terraform provider](https://registry.terraform.io/providers/env0/env0/latest/docs/data-sources/ip_ranges) to fetch IP addresses dynamically.

## Next steps

* [Security overview](/guides/overview/security-overview) - Review env zero's full security architecture.
* [Manage VCS connections](/guides/admin-guide/manage-vcs) - Configure VCS integrations that require IP allowlisting.
* [Self-hosted Kubernetes agent overview](/guides/admin-guide/self-hosted-kubernetes-agent/overview) - Run deployments from within your own network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.