https://s3-us-west-2.amazonaws.com/secure.notion-static.com/402b4f79-292a-40de-b570-116be58cf47c/gcp-overview.png

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/6bd3d265-f1b4-4052-b4a3-b57bde7957b9/ScreenShot2018-09-30at2.03.04PM.png

To view information about the Compute Engine instance you just launched, type the following into your SSH terminal:

cat /proc/cpuinfo

Projects:

We do billing in GCP on a project level, so by placing a bucket inside a project, you're essentially assigning who will be charged for it.

Picking Zones:

A zone in GCP is a datacenter. You ideally want to have multiple zones to reduce service disruptions.

Control your latency by choosing the closest zone/region.

Choose multiple zones in a region to reduce service disruptions.

Use multiple regions to provide global access to the application.

Store data in Cloud Storage

git clone to get data into local directory, from console, use gsutil to copy files into bucket.

In your SSH terminal, type the following, replacing <YOUR-BUCKET> with the name of the bucket you created in the previous task:

gsutil cp earthquakes.* gs://<YOUR-BUCKET>/earthquakes/