Allowlisting restricts access to a Unqork environment to a set of trusted public IP addresses. Allowlists apply to both the IDE and Express. They cannot be configured separately.
Important: To maintain core platform operations, Unqork's service IPs must remain allowlisted alongside the organization's specified IP addresses.
How Allowlisting Works
Once an allowlist is active, only traffic originating from the specified IP addresses can access the environment. All other traffic is blocked by the firewall.
Being on the allowlist does not exempt an IP address from standard security blocks. Improperly defined allowlists can impact end-users' experience. Network engineers and IT administrators should review the list before a request is submitted.
Cloud Provider Differences
Allowlist behavior varies by cloud provider:
| Provider | Scope |
|---|---|
| AWS | Per environment, regardless of cluster. |
| GCP | Per environment, regardless of cluster. |
| Azure | Per cluster. Allowlisting one environment in a cluster affects all environments in that cluster. For example, adding an allowlist to the Staging environment in a non-production cluster also affects UAT and any other environments on the same cluster. |
Requesting an Allowlist
Allowlist requests are managed through Unqork Support. The IT department can help define the specific IP addresses or ranges.
IP address ranges are specified using CIDR notation. For example, the range 203.0.113.0 to 203.0.113.255 is represented as 203.0.113.0/24.
To submit a request:
- Gather the environment URL or URLs to restrict.
- Compile the list of IP addresses or CIDR blocks to allowlist.
- Submit a support ticket at support.unqork.com with the environment URLs and IP list.
Changelog
| Date | Change |
|---|---|
| 2026-06-03 | Initial publication. |