Network connectivity
Decodable Connectors require network connectivity to resources, like databases, to read or write data. These connections can be made in different ways:
-
Public internet
-
Private connectivity with AWS PrivateLink
-
SSH Tunnels
See below for more details.
Public internet
By default Decodable will attempt to connect to your systems over the public internet. As a result, things like host names must be resolvable, and IP addresses must be routable. If you need to explicitly approve connections, our public IP addresses per AWS region are as follows:
AWS Region | IP Addresses |
---|---|
ap-southeast-2 |
|
af-south-1 |
|
eu-central-1 |
|
us-east-1 |
|
us-west-2 |
|
AWS PrivateLink
AWS PrivateLink allows Decodable to access services in your private VPC without exposing them to the public Internet. To connect with PrivateLink you must create a Network Load Balancer and VPC Endpoint Service in your VPC, and provide the Endpoint Service to Decodable support to establish connectivity.

AWS MSK multi-VPC connectivity
AWS Managed Service for Kafka (MSK) offers Multi-VPC Connectivity to connect private MSK clusters without exposing them on the public Internet.
To connect your private MSK cluster to Decodable you must enable multi-VPC connectivity, and provide the cluster ARN to Decodable support to establish connectivity.
SSH tunnels
SSH tunnels allow Decodable to connect securely to resources that can’t be exposed to the internet. To connect using SSH Tunnels you will configure a public SSH server and add a Decodable-provided public key to your authorized keys.

Contact Decodable support for help managing connectivity to your data infrastructure, or to configure PrivateLink or SSH tunnels for your connections.
For instructions on how to create a connection to a specific data source or sink, refer to the topic in the documentation specific to the connector that you are using.