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.
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.
Workflows temp. location: This setting controls the location (database.schema) where Workflows will create temporal tables for each node. By default, it's a workflows_tempschema that will be created in the connection's project during the execution of a workflow. Learn more about it here.