Data Loading and IP Whitelisting

A common data loading use case involves extracting data from your local database and uploading it to your GoodData project. This can be impacted by firewalls in place to protect your internal database.

For general information about IP whitelisting on the GoodData platform, see IP Whitelisting.

Contents:

To connect to resources behind enterprise firewall systems, GoodData's data loading tools (such as CloudConnect Designer and Ruby Bricks) include a secured proxy so that all external traffic is passed through a consistent set of IP addresses that you can easily whitelist.

Whitelisted IP addresses

To enable data loading IP whitelisting, add the following IP addresses to your firewall:

IP addressDescription
108.171.171.238
23.253.9.202
For secure.gooddata.com, United States (US-1 / Chicago) Datacenter
148.62.70.170
148.62.70.171
For secure-na3.na.gooddata.com, United States (US-2 / Dallas) Datacenter
78.136.2.250
134.213.186.151
For secure.eu.gooddata.com, European Union (EU) Datacenter
209.151.86.53
209.151.86.60
For secure.ca.gooddata.com, Canada (CA) Datacenter

To find out what datacenter your data is physically stored, see GoodData Datacenters.

IP address 107.22.195.240 is no longer in use. Ensure that you replaced it with 108.171.171.238 in your firewall settings.

Common Database Ports

The following table describes the specific ports that are used by common database engines. Depending on the installed database, these ports must be enabled for communication between the GoodData's data loading tools and your database:

PortDescription
22SFTP
1433, 1434Microsoft SQL Server
1521Oracle
3050Firebird, Interbase
3306MySQL
5439Amazon Redshift JDBC driver
5432, 5433PostgreSQL

For more information, contact GoodData Support.

GoodData Connection Ports

For more information on GoodData ports, see Ports Used to Connect to GoodData.