cloud engineer
If you have trouble logging in (SSH) to your GCP instance, you may have to enable OS Login.
gcloud compute instances add-metadata server-name \ --metadata enable-oslogin=TRUE \ --zone us-central1-c \ --project project-id |
When done, you can set it back to FALSE.
Here’s the command to authenticate as a service account.
gcloud auth activate-service-account --key-file=key.json |
To log out.
gcloud auth revoke |
If you’re trying to access GCS (Google Cloud Storage) and you’re getting “Your credentials are invalid. Please run gcloud auth login”, you most likely have a previous key stored in the ~/.boto file. This happens if you previously configured gsutil with your own credentials, then switched over to Google SDK mode. To fix the invalid credentials, edit the ~/.boto file and comment out the auth key.
vim ~/.boto |
Comment out.
#gs_oauth2_refresh_token = <token redacted> |
Rerun the gsutil ls command. It should work.
After logging in, I tried to run Terraform in GCP and received this error:
oauth2: cannot fetch token: 400 Bad Request |
Here’s the fix. Login using application-default.
gcloud auth application-default login |
You can then Terraform.
terraform apply |
SCP is similar to the CP or copy command, but it’s done via a secure network.
Here’s a CP command.
cp /dir1/filename /dir2 |
You can use SCP to copy file to another system. It requires login.
scp /dir1/filename user@server:/home/user |
This is using SCP to copy a file from 2 remote systems.
scp user@host1:/home/user/dir1/file.txt user@host2:/home/user/dir2 |