> ## 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.

Those IP addresses can be used to configure your VCS-allowed IP addresses or your Cloud resources. env zero undertakes to call your services through these addresses.

Those IP addresses used for [VCS](/guides/getting-started/connect-your-vcs) and also for SaaS runners

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 (1 here)\
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 (1 here)

If necessary, please prioritize IP addresses in us-east-1.  As env zero will utilize us-west-2 only during an event of a failover.

You can also use our [TF Provider](https://registry.terraform.io/providers/env0/env0/latest/docs/data-sources/ip_ranges) to fetch the 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.