A good security practice is to block connections from unrecognized sources on the network level using a firewall or AWS security groups. This applies especially to the production database whose connections should not be publicly available. For an extra layer of security, setting up an SSH Tunnel is also recommended.
To access external systems (including your database), Keboola uses the below IP addresses. Please whitelist these IP addresses in your firewalls to allow Keboola to successfully connect to your system. This applies to all components including all data source and destination connectors.
Important: These IP addresses can change in the future! For your convenience, you can programmatically fetch and process the list of existing IP addresses in JSON format. Below are listed the available Keboola Stack endpoints.
For ease of identification, our outbound IP addresses on AWS stacks (except for legacy services) now have reverse DNS records.
Each IP address has a unique name like outbound-if-issue-contact-support-at-keboola-com.keboola.com
, embedding a reference for a support email.
This enhancement helps us promptly tackle network issues or unauthorized access.
For projects in the default AWS US region (AWS region us-east-1
),
the following IP addresses are currently used for all new projects:
52.7.83.136
52.20.72.254
3.213.250.110
107.22.113.103
54.144.9.113
54.204.61.145
34.239.7.70
3.217.232.144
3.222.3.15
34.206.78.206
149.72.196.5
- Used only for email delivery.For projects running on legacy Queue V1 the following IP Addresses are used:
34.224.0.188
34.200.169.177
52.206.109.126
34.203.87.137
149.72.196.5
- Used only for email delivery.For projects in the AWS EU region (AWS region eu-central-1
),
the following IP addresses are currently used for all new projects:
3.66.248.180
3.64.150.30
3.74.28.187
18.158.155.128
35.157.208.189
3.72.243.47
18.193.225.37
3.127.158.56
35.157.62.225
3.71.156.204
149.72.196.5
- Used only for email delivery.For projects running on legacy Queue V1 the following IP Addresses are used:
35.157.170.229
35.157.93.175
149.72.196.5
- Used only for email delivery.For projects in the Azure EU region (Azure region north-europe
),
the following IP addresses are currently used:
40.127.144.42
20.82.252.94
20.82.252.129
20.82.252.124
20.67.181.161
149.72.196.5
- Used only for email delivery.For projects in the GCP EU Frankfurt region (GCP region europe-west3
),
the following IP addresses are currently used:
35.234.119.197
34.141.46.49
35.246.230.46
34.107.122.61
34.141.48.196
34.159.107.55
35.198.95.119
34.141.105.82
34.159.221.111
34.141.110.244
34.159.45.34
34.159.249.35
34.141.102.89
34.141.53.119
34.107.117.166
34.89.161.253
149.72.196.5
- Used only for email delivery.For projects in the GCP US Virginia region (GCP region us-east4
),
the following IP addresses are currently used:
35.245.113.124
35.186.177.208
34.48.52.58
34.145.229.110
34.48.69.223
35.245.169.222
35.236.206.220
35.221.29.130
35.245.146.94
34.85.153.249
34.48.67.21
35.245.10.93
34.86.101.13
35.199.50.163
35.245.139.246
35.245.222.156
149.72.196.5
- Used only for email delivery.We are publishing our current IP addresses in JSON format. To view them, download the kbc-public-ip.json file.
To determine whether there have been changes since the last time you saved the file, check the publication
time in the current file (syncToken
attribute) and compare it to the publication time in the last file you saved.
The JSON file contains an array of ranges (attribute prefixes
), each of which has the following attributes:
ipPrefix
— subnet mask (CIDR)vendor
— cloud service providerregion
— cloud service regionservice
— Keboola application service
queue
- for Keboola componentssyrup
- for Keboola components using legacy Queue V1email-delivery
- for outbound emails