SSH access and metadata in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is SSH access in Google Cloud Platform (GCP)?

SSH access allows you to securely connect to your virtual machine (VM) instances in GCP using a command-line interface over the internet or internal network.

beginner

What role does metadata play in managing SSH access on GCP VM instances?

Metadata stores SSH keys and other configuration data that GCP uses to control access and settings for VM instances.

intermediate

How can you add an SSH key to a GCP VM instance using metadata?

You add the SSH public key to the instance or project metadata under the 'ssh-keys' entry, allowing the corresponding private key holder to connect.

intermediate

What is the difference between project-wide and instance-level SSH keys in GCP metadata?

Project-wide SSH keys apply to all VM instances in the project, while instance-level keys apply only to a specific VM instance.

beginner

Why is it important to manage SSH keys carefully in GCP metadata?

Because SSH keys control who can access your VMs, managing them carefully helps keep your cloud resources secure and prevents unauthorized access.

Where do you add SSH keys to allow access to all VM instances in a GCP project?

A In the project-wide metadata under 'ssh-keys'

B In the instance's boot disk

C In the firewall rules

D In the Cloud Storage bucket

Adding SSH keys to the project-wide metadata under 'ssh-keys' allows access to all VM instances in that project.

What does SSH stand for?

A Secure System Handler

B Simple Secure Host

C Server Shell Host

D Secure Shell

SSH stands for Secure Shell, a protocol for secure remote login and other secure network services.

If you want to restrict SSH access to only one VM instance, where should you add the SSH key?

A In the Cloud IAM roles

B In the project-wide metadata

C In the instance-level metadata

D In the VPC network settings

Adding SSH keys to the instance-level metadata restricts access to that specific VM instance only.

What is the purpose of the SSH public key in GCP metadata?

A To identify the user allowed to connect to the VM

B To encrypt the VM's disk

C To configure the VM's firewall

D To start the VM instance

The SSH public key identifies the user who is allowed to connect securely to the VM instance.

Which of the following is NOT a recommended practice for SSH key management in GCP?

A Regularly rotating SSH keys

B Sharing private SSH keys with others

C Removing unused SSH keys from metadata

D Using instance-level keys for sensitive VMs

Sharing private SSH keys is insecure and not recommended; private keys should be kept secret.

Explain how SSH access is controlled using metadata in GCP.

Think about where SSH keys are stored and how they grant access.

Describe best practices for managing SSH keys in GCP metadata to keep your VMs secure.

Consider security steps to prevent unauthorized access.