Can my software services communicate between different cloud providers safely?

Every Elestio project establishes a unique and secure encrypted virtual network, allowing services within the project to communicate through private IPv4 addresses.

This communication occurs with nearly line-speed throughput, regardless of location or service provider.

The driving force behind this distinctive capability is Nebula, initially developed by Slack and released as open-source software in 2020. you can learn about nebula from here.

It provides a virtual private cloud (VPC) Isolated per project.

How can I Enable/Disable the Global Private IP?

To toggle the Global Private IP on or off, follow these steps:

1. Navigate to the services section in the Elestio dashboard using the left sidebar.

2. Choose your specific service.

3. Locate the Network row in the same overview tab.

4. Within the Network row, find the Global Private IP switch on the right side and toggle it to enable or disable the ~~global~~Global ~~private~~Private IP.

How to associate the Service with the Private IP rather than the Public IP?

Taking the example of the MySQL service, if you want to bind it to the Private IP instead of the Public IP, making it accessible only within the global private network of your project in Elestio, follow these steps:

Navigate to the services section in the Elestio dashboard using the left sidebar.

Choose your specific MYSQL service.

Click the "Update Config" button in the Software row on the Overview tab.

Within the docker-compose file, locate the following section:
```
ports:
    - '24306:3306'
```
Replace it with:
```
ports:
    - 'GLOBAL_PRIVATE_IP:24306:3306'
```

Click the "Update & Restart" button to apply the changes.

Afterward, the MySQL port will only be accessible from the internal network through the global private IP address on port 24306.

This setup is akin to a Virtual Private Cloud (VPC), where all other services deployed in the same Elestio project coexist within the same Virtual VPC.