# Setting up PostGIS on GCP

Working towards online geospatial solutions

OK, so here we are, in the midst of COVID-19. What a great time to start a new project and learn a new skill. I’m focusing on developing a bit of my golang chops and the Google Cloud Platform knowledge to see if we can use these as our primary backends for teaching and research needs at work. My boss just gutted my server room and has maneuvered the only person who can actually do geospatial backend work to not work in my unit any longer so I’ve got to get creative.

This is an ongoing process, check out all the stuff related to this topic posted here under the GCP category.

## Setting up gcloud

First we need to download the Google Cloud Platform SDK. It can be found here. Download it and install it locally. This will provide you with the gcloud command line interface.

Here is the one I installed

rodney@mini ~ % gcloud version
bq 2.0.55
core 2020.03.17
gsutil 4.48


For this, you need to log into the Google Cloud Console and start a new project. You will also be required to enter a credit card so that any charges you incur are taken care of. For developers and all other people, Google gives $300 in monthly credit, which I have found to be more than enough for me to do everything I need to do to play around. I have yet to be hit with any charges (and you can put on hard limits to be safe). Once you have set up a project you can install a database. ## Installing PostgreSQL as CloudSQL There are serveal ways to install databases, you could spin up a Virtual Machine (VM) running some flavor of linux (I like Ubuntu myself) or you can do this serverless (which is what I’m going to do here). To run serverless, you do not need to worry about the underlying infrastructure of what is going on, just trust that Google can make a copy of PostgreSQL available to me. To get an instance going, select SQL from the hamburger menu on the left and follow the documentation on spinning up an instance. I’m using PostgreSQL because we can install PostGIS onto it, both MySQL and some Microsoft offering is also available if that is how you swing (no idea if the M$ can have geospatial data extensions).

Notes:

• Give the instance a reasonable name, you’ll be using it over and over.
• Make a good password and save it.

### Making an SSL Certificate - Failed

To be able to connect to this instance, we need to get an SSL Certificate. In the Connections tab do the following:

1. Set the database to be only allowing connections via SSL.
2. Configure a new client certificate and download the client-key.pem, client-cert.pem and server-ca.pem. These three files are needed to connect psql to this server.
3. Copy and save the connection information that is presented for you.
psql "sslmode=verify-ca sslrootcert=server-ca.pem \
sslcert=client-cert.pem sslkey=client-key.pem \
port=5432 \
user=postgres dbname=postgres"


This should be what you need. Run it from the same folder you downloaded the *.pem files and you should be good. For more information, see the connection documents here

I was rather unable to get this to work, so I tried another way to actually get it to work. Would like to get the IP way as this may scale a bit better than using Proxies…

### CloudSQL Proxy

This is another way of trying to connect to your instance online and simplifies stuff by hadling all the authentication stuff. You can see the documentation for this here.

###### Father, Husband, Brewer, Professor

Middle aged guy trying to keep it all together and figure out how to best navigate the world as it is. Technology geek, practitioner of fermentation sciences, researcher, biologist.