Amazon Redshift

You can use CARTO with your data in an Amazon Redshift data warehouse.

If you want to create a connection to your Redshift data warehouse, you need to select the Redshift connector in the New connection dialog. After you select the connector click the Setup connection button.

These are the parameters you need to provide:

• Name for your connection: You can register different connections with the Redshift connector. You can use the name to identify the connections.

• Cluster: DNS name or IP address for your Redshift cluster.

• Username: Name of the user account.

• Password: Password for the user account.

• Database: Database your connection will use.

• Port: TCP port where your cluster is listening for connections.

Once you have entered the parameters, you can click the Connect button. CARTO will try to connect to your Redshift cluster. If everything is OK, your new connection will be registered.

CARTO will try to minimize and reuse the number of connections (sockets) made to the Redshift database. But in some cases the amount of connections can grow rapidly. If you have a strong requirement to control the incoming connections to your database, we recommend to put a proxy like PgBouncer between CARTO and your database.

The connections are only reused if they are going through the same CARTO-Redshift Connection. If you set up many Connections in your organization, the amount of database connections will grow faster.

Advanced options

• Analytics Toolbox location: This setting controls the location of the Analytics Toolbox used in SQL queries generated by Workflows components, Builder SQL Analyses, 'Create Tileset', 'Geocode Table' and 'Enrich Data' functionalities. By default, a carto schema will be used.

• Data Observatory location: This settings controls the location of the Data Observatory subscriptions. This setting will be observed by Data Explorer, Workflows and Enrichment to access your data subscriptions. By default, a cartoschema will be used.

• CARTO temp location

  Location to store temporary tables used during workflow execution. These include intermediate tables with hashed names created by nodes in a workflow. By default, CARTO uses a carto_temp schema per database. Example: my_redshift_db.carto_temp

• CARTO Workspace location

  Location to store persistent objects related to workflows, such as API stored procedures and imported files. By default, CARTO uses a carto_workspace schema per database. Example: my_redshift_db.carto_workspace

• Max number of concurrent queries: This setting controls the maximum number of simultaneous queries that CARTO will send to Redshift using this connection.

• Max query timeout: This setting controls the maximum allowed duration of queries that CARTO runs in Redshift using this connection.

• Restrict this connection to only use Named Sources: When this setting is enabled, this connection will only work within apps that use Named Sources, and it will NOT work in Data Explorer, Builder and Workflows. This prevents the usage of arbitrary SQL in applications for this connection.

IP Whitelisting

If you're using the cloud version of CARTO (SaaS), CARTO will connect to Amazon Redshift using a set of static IPs for each region. Check this guide to find the IPs you need to allow for your specific region.