IP Addresses

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 Connection uses the below IP addresses. Please whitelist these IP addresses in your firewalls to allow Keboola Connection to successfully connect to your system. This applies to all components including all extractors and writers.

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 Connection Stack endpoints.

connection.keboola.com

For projects in the default AWS US region (AWS region us-east-1), the following IP addresses are currently used:

34.224.0.188
34.200.169.177
52.206.109.126
34.203.87.137
149.72.196.5

connection.eu-central-1.keboola.com

For projects in the AWS EU region (AWS region eu-central-1), the following IP addresses are currently used:

35.157.170.229
35.157.93.175
149.72.196.5

connection.north-europe.azure.keboola.com

For projects in the Azure EU region (Azure region north-europe), the following IP addresses are currently used:

40.127.144.42

IP Address Ranges in JSON

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 provider
region — cloud service region
service — Keboola application service (syrup for Keboola Connection components)

Sample JSON

{
    "syncToken": "1496657320",
    "createDate": "2017-06-05-10-08-39",
    "prefixes": [
        {
            "ipPrefix": "34.224.0.188/32",
            "vendor": "aws",
            "region": "us-east-1",
            "service": "syrup"
        },
        {
            "ipPrefix": "34.200.169.177/32",
            "vendor": "aws",
            "region": "us-east-1",
            "service": "syrup"
        },
        ...
    ]
}