Connect to a cloud database with a FQDN Address via MySQL Workbench
Note: To complete this process, you will need both a cloud server and a cloud database.
Use the following steps to connect to Cloud Databases by using MySQL Workbench.
- Go to http://www.mysql.com/products/workbench/ and install MySQL WorkBench.
The following platforms are supported: Windows, Fedora, Ubuntu, Oracle and Redhat, and Mac OS X. Registration is required before you download.
- Launch MySQL Workbench, and select the New Server Instance option under Server Administration.
- In the next screen, select the Remote Host option and enter the URL that was returned to you when you created the database instance and click Continue.
- On the next screen, from the Connection Method menu, select Standard TCP/IP over SSH.
- Change the value for SSH HostName to the name or ip address of a Cloud Server that you have created and that is in the same data center as the database instance. For example, if the database instance that you created is in the DFW data center, select a cloud server in the DFW data center.
- For SSH Username, enter the user name that you use to log in to the cloud server that you just specified.
- For MySQL Hostname, enter the host name that was returned when you created the database instance via the API.
- For Username, enter the username that was created when you created the database instance.
- Click Continue.
You are prompted for the database instance password. If everything is correct, the following information is displayed:
After the database connection is tested, the following screen is displayed. You can now work with your database instance.
Note: If you did not save your password, when you perform any actions, you will be prompted for the password to either the instance or the server.
Carry on the conversation in the Rackspace Community.
© 2015 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER