Connection Options

There are multiple ways to connect to your integrations depending on how you deploy Superblocks (Cloud or On-Premise Agent) as well as the integration type.

• Connect from Superblocks Cloud
  • Direct - Third-party SaaS APIs
  • IP allowlist - Databases and non-public internal APIs
  • SSH tunnel - Databases where direct access is restricted
• Connect from On-Premise Agent

Connect from Superblocks Cloud

By default, Superblocks Cloud acts as a proxy to your integrations. This makes it simple to get started and simple to manage.

Direct

For integrations with public third-party SaaS REST APIs, Superblocks Cloud can connect directly without any networking configuration.

IP allowlist

For databases and non-public internal APIs, we recommend using IP allowlists to protect your environment. When using the Superblocks Cloud deployment model, add the following IP addresses to your ingress allowlist in the network where your data sources reside.

US Instance

NAT hostname	Current DNS	Last Recorded IPs
nat.superblocks.com	A Records	107.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

EU Instance

NAT hostname	Current DNS	Last Recorded IPs
nat.eu.superblocks.com	A Records	52.17.136.219 99.81.159.1 54.220.65.107 13.50.50.66 13.50.81.30 13.51.231.18

note

Superblocks aims to rarely change these addresses. For the most up to date IP addresses, reference the current A records link above.

info

For configuring an IP allowlist for databases on AWS and GCP, see the implementation guide here

SSH tunnel

Superblocks supports connecting via an SSH tunnel for the following database integrations:

• Postgres
• MySQL

To setup SSH tunneling:

1. Select the Use SSH Tunnel checkbox in the Superblocks integration form, and configure the following settings:

Setting	Description
Authentication Method	Auth method used by the bastion server to connect to your instance. Choose between User-defined Private Key and Password.
Bastion Host	Bastion destination address to connect to for SSH port forwarding
Bastion Port	Bastion destination port to connect to for SSH port forwarding
Bastion Username	Username for bastion host

2. Configure authentication settings based on the previously chosen Authentication Method:

   • User-defined Private Key - Add your public and private keys in Superblocks. Both RSA and Ed25519 are supported.
   • Password - Add bastion password in Superblocks

3. Allow connections from Superblocks to your bastion host (see IP allowlist)

4. On the bastion host, make sure there is a user account associated with the bastion username. If creating a new account, add the public key into ~/.ssh/authorized_keys.

Connect from On-Premise Agent

When using the On-Premise Agent deployment model, an agent running inside your own network connects to your integrations. As such, you do not need to open any inbound firewall rules. See the On-Premise Agent docs for more details.