Skip to main content

Connection Options

There are three ways to connect Superblocks to your integration:

  1. Direct Connection
  2. IP Allowlists
  3. On-premise Agent

Direct Connection

By default, Integrations are connected to the Superblocks Cloud via direct connection. This makes it simple to get started and simple to manage. Superblocks Cloud acts as a proxy to your Integrations. For production databases and non-public internal APIs, we recommend using IP allowlists to protect your environment, see next section for more details.

IP Allowlists

When using Superblocks' cloud-only deployment model, it is vital that Superblocks is able to connect to your configured integrations. In order to keep your environment secure the following IP addresses must be added to an allowlist within your environment.

NAT hostnameCurrent DNSLast Recorded IPs
nat.superblocks.comA Records107.22.228.244
3.93.101.124
34.209.17.50
34.227.169.51
35.155.119.178
35.171.116.214
35.86.18.137
44.232.244.93
54.148.33.216

While we do our best to never change these addresses, the best way to keep an updated allowlist is to use the current A records for the NAT hostname shown above.

A simple implementation guide is found below for both AWS and GCP.

  • Log in to the AWS Console
  • Navigate to the resource that you would like Superblocks to connect to
  • If you are applying an allowlist to an RDS instance, the instance must be set to Publicly accessible (this is found under Connectivity -> Additional configuration)

  • Select an existing Security Group or create a new one
  • Select the Inbound tab at the bottom and click edit

  • Choose the port to connect over (defaults for Postgres: 5432, MySQL: 3306, MSSQL: 1433)
  • Set Source to Custom and enter the following IP addresses
    107.22.228.244/32, 3.93.101.124/32, 34.209.17.50/32, 34.227.169.51/32, 35.155.119.178/32, 35.171.116.214/32, 35.86.18.137/32, 44.232.244.93/32, 54.148.33.216/32

  • Click Save rules

On-premise Agent

See the On-premise Agent page for more details.