Documentation Data Sources

Allow Chartio's IP Address

A prerequisite for setting up direct connections to your data source in Chartio is allowing communication from Chartio’s IP address ( We’ve provided instructions for how to do this for some of our most popularly connected data source types:

Amazon RDS

For Chartio to connect to your Amazon RDS database, you’ll need to modify your RDS Security Group to allow Chartio’s inbound IP address. To view your Security Groups, access your RDS Dashboard.

Add a new Inbound Rule

  1. From the AWS Management Console, click Services > EC2 > Network & Security > Security Groups.
  2. Next, you’ll need to edit the Security Group you want to use.
    • If you have an existing Security Group you’d like to modify…
      Select it from the list then click Actions > Edit Inbound Rules.
    • If you don’t have a Security Group yet
      Click Create Security Group to add a new one.
  3. Select the Inbound tab then click Add Rule, completing the CIDR (Classless Inter-Domain Routing) form and allowing incoming connections.
    • For the Port Range, use the corresponding port number for your database type:
      • MySQL or MariaDB: 3306
      • Postgres: 5432
      • SQL Server: 1433
      • Oracle: 1521
    • For the IP address, use

    Add new inbound rule

  4. Click Apply (for existing Security Groups) or Create (for new Security Groups) to save your new rule.

Connect your new Security Group to your RDS database

If you created a new Security Group, you need to apply it to your RDS database.

  1. Click Databases > {your database instance name} > Modify.

  2. Scroll to the Network & Security section.
  3. Select your newly created Security Group from the list to add it.

  4. Click Continue.
  5. Under Scheduling of modifications, select when you’d like to apply your changes:
    1. If you choose Apply immediately, your changes are applied right away.
    2. If you choose Apply during the next scheduled maintenance window, you can minimize the risk of possible downtime to your database instance.

  6. Click Modify DB Instance to apply your changes. You’ll be taken back to your database instance’s summary page, where your newly added Security Group should appear under the VPC security groups.

Refer to our Amazon RDS page for further instructions on connecting Amazon RDS to Chartio.

Amazon Redshift

For Chartio to connect to your Redshift database, you’ll need to allow our inbound IP address ( ) in your Cluster’s Security Group settings:

  1. Log in to the Redshift Management Console.
  2. Select Clusters from the left sidebar then select the cluster you want to connect to Chartio.
  3. From the Cluster Details page, navigate to the Properties tab and scroll to the Network and security section.

  4. Under VPC Security Groups, click the Security Group you want to use to allow communication from Chartio.

  5. Click the Inbound Rules tab at the bottom of the page then click Edit.

  6. Click Add Rule to add a new Inbound Rule.
    a. Set the Type to Redshift.

    b. Adjust the Port, if needed.

    c. Enter the following into the Source field:

  7. Click Save.

Refer to our Amazon Redshift page for further instructions on connecting Amazon Redshift to Chartio.

Google Cloud SQL

Ensure that the Chartio IP address has been allowed to access the Google Cloud SQL instance. To do this, open the Google Cloud console and do the following:

  1. Navigate to the SQL server instance.
  2. View the Connections tab.
  3. Ensure the Public IP option is selected and click Add Network.

    Use a Public IP and add a new network

  4. Enter Chartio as the name of the network with the following CIDR:

    Enter Chartio's IP information

  5. Click Done to add the new network, then click Save to save your connection changes.

Refer to our Google Cloud SQL page for further instructions on connecting Google Cloud SQL to Chartio.

Microsoft Azure

  1. Log in to your Microsoft Azure account.
  2. Select SQL Databases from the navigation, then select the name of the database you’d like to connect to.
  3. Go to the Overview page for your database and click Set server firewall near the top of the page.

    Click Set server firewall from the Overview page

  4. Select No for Deny public network access. If you select Yes, you won’t be able to connect to Chartio.
  5. Add a new rule using the following IP address:

    Rule name: Chartio
    Start IP Address:
    End IP Address:

    Allow public network access and add Chartio's IP address with a new rule

  6. Click outside of the text fields to add and save the new rule.

Refer to our Microsoft Azure page for further instructions on connecting Microsoft Azure to Chartio.

Microsoft SQL Server

For connections from a local machine

There are a couple configurations you’ll need to make to use Chartio with a local SQL Server:

  1. Forward traffic from our external IP ( ) on port 1433 to the internal IP address of your desktop computer.
  2. Allow access to SQL Server via the Windows firewall. For more information, refer to Microsoft’s page about configuring the Windows firewall.

If you have an IT person or a network administrator, they’ll know how to do this for you.

Refer to our Microsoft SQL Server page for further instructions on connecting Microsoft SQL Server to Chartio.


By default, PostgreSQL restricts connections to hosts and networks included in the pg_hba.conf file. You may need to add Chartio’s IP address to this file to allow connectivity to your database; you’d add the line to pg_hba.config in the following format:

host databaseName username md5

Here’s an example, where the username is chartio_read_only and the database is mydatabase:

host mydatabase chartio_read_only md5

You may need to restart your PostgreSQL server for the changes to take effect.

For more details on modifying the pg_hba.conf file consult the PostgreSQL documentation.

Refer to our PostgreSQL page for further instructions on connecting PostgreSQL to Chartio.


By default, Snowflake instances are open to every IP address, so no action is required. However, you can set up network policies to restrict the IP addresses communicating with your Snowflake instance. If you have any network policies in place, you’ll need to modify those policies to allow Chartio’s IP address (

There are two types of network policies you can set up in your Snowflake instance: account level and user level. Account level policies apply to all users unless the policy is overridden by a user level policy. User level policies only apply to the users that the policy is assigned and user level policies will override account level policies.

  • If you’ve configured account level network policies, you’ll need to edit your network policy to allow incoming connections from Chartio’s IP address. Please refer to the Snowflake documentation for more information on modifying account level network policies.
  • If your organization uses user level network policies, you’ll need to create a new policy to apply to the read-only user you create, allowing incoming connections from Chartio’s IP address. Please refer to the Snowflake documentation for more information on modifying user level network policies.

Refer to our Snowflake page for further instructions on connecting Snowflake to Chartio.