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 54.79.178.25 3.24.174.157 54.66.91.180 af-south-1 13.247.8.169 13.246.95.241 13.246.203.137 eu-central-1 18.158.40.109 18.159.175.142 18.193.1.236 us-east-1 44.210.12.91 44.208.143.30 52.5.150.139 52.4.58.41 44.195.57.218 us-west-2 35.160.167.162 54.203.83.22 44.226.160.138 52.36.183.59 AWS PrivateLink AWS PrivateLink allows Decodable to access services, including Amazon RDS and Amazon Managed Service for Kafka (MSK), 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. 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.