IP whitelisting
This section provides the list of Quickwork public IP addresses and guidance on how to whitelist them in your network or firewall settings.
To ensure secure and reliable communication between Quickwork and your services, you may need to whitelist Quickwork’s public IP addresses in your firewall, database, or API gateway settings. IP whitelisting allows outbound requests from Quickwork’s servers to reach your application endpoints.
IP addresses by region
Purpose : Production
Region / Environment | IP address(es) | URL |
|---|---|---|
Tokyo (AWS) | 54.95.226.138 | |
Germany (OTC) | 80.158.47.145 | |
Mumbai (AWS) | 3.109.174.62 |
- Multiple IP addresses on production improve reliability of our services in the event where one of the NAT gateways is unresponsive.
- Whitelist these IPs in your application, database or API gateway to allow communication.
Port configuration
Quickwork does not define or enforce port numbers. The client system determines which ports must be opened based on the service you are connecting to. Typical examples include:
| Service | Default Port |
|---|---|
| PostgreSQL | 5432 |
| MySQL | 3306 |
Refer to your service documentation or contact your system administrator for the correct port details.
Recommended whitelisting procedure
- Add the Quickwork IPs listed above to your firewall allowlist or network security group.
- Ensure the correct port(s) are open for the service being accessed.
- Test connectivity by performing a simple API or database request from your Quickwork journey.
- Confirm successful communication by checking the History tab in Quickwork.
Example use case
If you are connecting Quickwork to your organization’s internal PostgreSQL database hosted on AWS, you should:
- Whitelist the production IPs (3.109.174.62, 65.1.254.60, 13.235.211.222).
- Allow TCP port 5432 for outbound traffic.
- Verify connectivity by running a sample Execute custom SQL query step using the PostgreSQL app.
Updated about 1 month ago