Networking
To ensure optimal security when connecting to your environments, DinMo offers two secure access methods: SSH tunneling and IP whitelisting.
SSH tunneling allows us to establish a secure, encrypted connection through a bastion host, ensuring that your data remains protected in transit.
In addition, you can whitelist our static IP addresses to restrict access strictly to DinMo’s services.
Both methods limit exposure to external threats and comply with enterprise-grade security standards.
Of course, you can use both methods. Choosing the right approach depends on your internal policies and infrastructure. We recommend collaborating with your security team to implement the method that best fits your requirements.
IP Addresses
To enhance network security and ensure seamless connectivity with DinMo, we provide specific IP addresses that you can whitelist. By doing so, you will allow uninterrupted access to DinMo's services while protecting your network from unauthorized access.
IP Addresses for Whitelisting
To optimize your network security and ensure reliable communication with DinMo, please whitelist the following IP addresses based on our cloud service providers:
Google Cloud Platform (GCP) (europe-west1)
IP Address:
34.38.245.85
Amazon Web Services (AWS) (eu-west-1)
IP Addresses:
52.50.105.47
79.125.91.50
99.80.131.31
SSH Tunneling
How it works
SSH tunnel requires an sshd
service running on a bastion host that is accessible from the public internet. Our systems initiate an SSH connection to this bastion and then forward traffic from there to the private service you define.
Setup
When creating a new source, select “SSH Tunnel” as the connection type.
Fill out the SSH Host or IP and the SSH Port
These are the connection details for your public-facing bastion server host.
The port is most likely 22, standard for
sshd
. The field is filled with this information by default
Enter a username for this SSH connection
Click on "Generate SSH Tunnel" and copy the public key which is generated. Add this to the
~/.ssh/authorized_keys
file for the user you've just filled in.
Last updated