docs(security): document the US region

Adds the US region to the data regions table and its egress IP to the networking page, so customers can reach cloud.us.prowler.com and allowlist the region they are hosted in.
2026-08-20 10:00:40 +00:00 · 2026-07-28 17:23:08 +02:00
2 changed files with 12 additions and 6 deletions
@@ -9,7 +9,9 @@ Prowler Cloud runs on AWS with high availability built in.
 | Region | URL | Location |
 |--------|-----|----------|
 | **EU** | [cloud.prowler.com](https://cloud.prowler.com) | Ireland (`eu-west-1`) |
-| **US** | On-Demand | On-Demand |
+| **US** | [cloud.us.prowler.com](https://cloud.us.prowler.com) | N. Virginia (`us-east-1`) |
+
+Each region is fully isolated: data stays in the region where the account was created and is never replicated to the other.


 ## Business Continuity
@@ -6,18 +6,22 @@ title: 'Networking'

 Prowler Cloud makes outbound API calls to scan cloud provider accounts and connect to integrations. Allowlist these IPs in firewalls or security groups to restrict access to Prowler Cloud only.

-| Region | IP Address |
-|--------|------------|
-| EU (Ireland) | `52.48.254.174` |
+Allowlist only the region hosting the account. Each region egresses from its own IP address.
+
+| Region | IP Address | DNS |
+|--------|------------|-----|
+| EU (Ireland) | `52.48.254.174` | `egress.prowler.com` |
+| US (N. Virginia) | `18.213.69.80` | `egress.us.prowler.com` |

 Resolve the egress IP via DNS:

 ```bash
-dig egress.prowler.com +short
+dig egress.prowler.com +short      # EU
+dig egress.us.prowler.com +short   # US
 ```

 <Note>
-The egress IP address is stable, but it is recommended to periodically verify it remains current by querying `egress.prowler.com`.
+The egress IP addresses are stable, but it is recommended to periodically verify they remain current by querying the DNS names above.
 </Note>

 ## Use Cases