{"id":8987,"date":"2026-09-18T10:11:13","date_gmt":"2026-09-18T10:11:13","guid":{"rendered":"https:\/\/prwatech.in\/blog\/?p=8987"},"modified":"2026-09-19T15:34:54","modified_gmt":"2026-09-19T15:34:54","slug":"creating-cloud-sql-instance-using-cloud-shell","status":"publish","type":"post","link":"https:\/\/prwatech.in\/blog\/google-cloud-platform\/cloud-sql\/creating-cloud-sql-instance-using-cloud-shell\/","title":{"rendered":"Creating Cloud SQL Instance using cloud shell"},"content":{"rendered":"\r\n

Creating a Cloud SQL Instance With gcloud<\/h1>\r\n

Cloud SQL<\/b><\/strong>\u00a0is Google Cloud’s managed relational database service, running MySQL, PostgreSQL, or SQL Server without you having to patch, back up, or maintain the underlying server yourself. Everything shown in the console, creating an instance, setting a password, opening network access, has an equivalent gcloud command, and that command line path is what this walks through.<\/p>\r\n

Doing this through Cloud Shell instead of clicking through the console matters once you go beyond a single, one time setup. A command you have already written can be rerun exactly, copied into a script, or handed to a teammate, none of which a sequence of console clicks gives you. It is also simply faster once you know the commands, since creating an instance, setting its password, and opening it up for a connection are three commands here instead of three separate screens.<\/p>\r\n

This creates a Cloud SQL for MySQL instance entirely from Cloud Shell, sets a password for it, opens network access to it, then connects directly using the mysql client, the same end result as using the console, reached a different way.<\/p>\r\n

Step by Step Process of Creating a Cloud SQL<\/h2>\r\n

Step One: Activate Cloud Shell<\/h3>\r\n

Open the console and click Activate Cloud Shell.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Two: Set Your Project ID as a Variable<\/h3>\r\n

export PROJECT_ID=$(gcloud info –format=”value(config.project)”)
echo $PROJECT_ID<\/p>\r\n

The first line saves your current project ID into a variable. The second prints it back, so you can confirm it picked up the right one.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Three: Name a Bucket Variable<\/h3>\r\n

export BUCKET=${PROJECT_ID}-ml
echo $BUCKET<\/p>\r\n

This saves a bucket name based on your project ID into a variable, then prints it. This does not create the bucket itself, it just prepares the name for later use.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n

Step Four: Create the Instance<\/h3>\r\n\r\n\r\n\r\n

$\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 gcloud sql instances create taxi –tier=db-n1-standard-1<\/p>\r\n\r\n\r\n\r\n

It will create a sql instance with name taxi.<\/p>\r\n\r\n\r\n\r\n

It will take a little bit time to create.<\/p>\r\n

Accessing the Instance<\/strong>:<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Five: Set a Password<\/h3>\r\n

gcloud sql users set-password root –host % –instance INSTANCE_NAME –password<\/p>\r\n

Leave off the password value itself here, and just add –password with nothing after it. gcloud will prompt you to type it interactively instead, which keeps it out of your shell history, unlike typing the actual password directly into the command.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Six: Authorize a Network<\/h3>\r\n

gcloud sql instances patch INSTANCE_NAME –authorized-networks 0.0.0.0\/0<\/p>\r\n

Press y to confirm.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

As covered above, this specific range opens the instance to the entire internet, which is fine for a five minute throwaway test and a genuinely bad idea for anything real. If you know the specific IP address you will be connecting from, authorize just that address instead, for example replacing 0.0.0.0\/0 with YOUR_IP_ADDRESS followed by \/32. The section below covers a better option than authorized networks entirely.<\/p>\r\n

Step Seven: Find the Instance’s IP Address<\/h3>\r\n

Open the console, then the menu, then SQL.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Copy the instance’s IP address.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Eight: Save the IP Address as a Variable<\/h3>\r\n

MYSQL=IP_ADDRESS
echo $MYSQL<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Nine: Connect With the MySQL Client<\/h3>\r\n

mysql –host=$MYSQL –user=root –password<\/p>\r\n

Enter the password you set earlier when prompted. It will not be shown on screen as you type it, this is normal, just press enter once you are done.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Ten: Run a Test Command<\/h3>\r\n

show databases;<\/p>\r\n

This lists the databases currently on the instance.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Step Eleven: Exit<\/h3>\r\n

exit<\/p>\r\n

This closes the mysql console and returns you to Cloud Shell.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n

A Safer Way to Connect Than Authorized Networks<\/h2>\r\n

Rather than opening a public IP to a wide range of addresses, Google’s own recommended approach is the Cloud SQL Auth Proxy. It runs alongside your application or on your own machine, handles authentication through IAM permissions instead of a password sitting in a connection string, and encrypts the connection automatically, all without needing to add any address to authorized networks at all. For anything beyond a quick, disposable test, this is the option worth reaching for instead of widening authorized networks.<\/p>\r\n

Common Mistakes to Avoid<\/h2>\r\n