Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
After a lot of searching, I finally found where the bind address was hiding: It was in
/etc/mysql/mariadb.conf.d/50-server.cnf
Once I commented out the bind address and restarted mariadb, I was able to connect remotely.
I thought I’d post this in case it helps anyone else.
As per my understanding , changing bind address to your server IP address allow everyone to connect to your database, which might pose security risk . keeping bind to 127.0.0.1 only allows server users to connect and manage database. you could use SSH over TCP to tunnel to your database as a user with SSH enabled on your server , if you have SSH enabled for the user that will mange your database. i use workbench for connecting to mysql remotely , and i have bind set to 127.0.0.1 and have no issue connecting.