Overview

Google Cloud Virtual Private Cloud (VPC) provides networking functionality to Compute Engine virtual machine (VM) instances, Kubernetes Engine containers, and App Engine flexible environment. In other words, without a VPC network you cannot create VM instances, containers, or App Engine applications. Therefore, each Google Cloud project has a default network to get you started.

You can think of a VPC network as similar to a physical network, except that it is virtualized within Google Cloud. A VPC network is a global resource that consists of a list of regional virtual subnetworks (subnets) in data centers, all connected by a global wide area network (WAN). VPC networks are logically isolated from each other in Google Cloud.

In this lab, you create an auto mode VPC network with firewall rules and two VM instances. Then, you explore the connectivity for the VM instances.

Objectives

In this lab, you learn how to perform the following tasks:

• Explore the default VPC network
• Create an auto mode network with firewall rules
• Create VM instances using Compute Engine
• Explore the connectivity for VM instances

Setup and requirements

For each lab, you get a new Google Cloud project and set of resources for a fixed time at no cost.

1. Sign in to Qwiklabs using an incognito window.

2. Note the lab's access time (for example, 1:15:00), and make sure you can finish within that time.
   There is no pause feature. You can restart if needed, but you have to start at the beginning.

3. When ready, click Start lab.

4. Note your lab credentials (Username and Password). You will use them to sign in to the Google Cloud Console.

5. Click Open Google Console.

6. Click Use another account and copy/paste credentials for this lab into the prompts.
   If you use other credentials, you'll receive errors or incur charges.

7. Accept the terms and skip the recovery resource page.

Task 1. Explore the default network

Each Google Cloud project has a default network with subnets, routes, and firewall rules.

View the subnets

The default network has a subnet in each Google Cloud region.

• In the Cloud Console, on the Navigation menu (), click VPC network > VPC networks.

Notice the default network with its subnets. Each subnet is associated with a Google Cloud region and a private RFC 1918 CIDR block for its internal IP addresses range and a gateway.

View the routes

Routes tell VM instances and the VPC network how to send traffic from an instance to a destination, either inside the network or outside Google Cloud. Each VPC network comes with some default routes to route traffic among its subnets and send traffic from eligible instances to the internet.

1. In the left pane, click Routes.

2. In the Effective Routes tab, select the default network and the .

Notice that there is a route for each subnet and one for the Default internet gateway (0.0.0.0/0).
These routes are managed for you, but you can create custom static routes to direct some packets to specific destinations. For example, you can create a route that sends all outbound traffic to an instance configured as a NAT gateway.

View the firewall rules

Each VPC network implements a distributed virtual firewall that you can configure. Firewall rules allow you to control which packets are allowed to travel to which destinations. Every VPC network has two implied firewall rules that block all incoming connections and allow all outgoing connections.

• In the left pane, click Firewall.

Notice that there are 4 Ingress firewall rules for the default network: * default-allow-icmp * default-allow-rdp * default-allow-ssh * default-allow-internal

Note: These firewall rules allow ICMP, RDP, and SSH ingress traffic from anywhere (0.0.0.0/0) and all TCP, UDP, and ICMP traffic within the network (10.128.0.0/9). The Targets, Filters, Protocols/ports, and Action columns explain these rules.

Delete the Firewall rules

1. In the left pane, click Firewall.
2. Select all default network firewall rules.
3. Click Delete.
4. Click Delete to confirm the deletion of the firewall rules.

Delete the default network

1. In the Cloud console, navigate to Navigation menu () > VPC network > VPC networks.
2. Select the default network.
3. Click Delete VPC network.
4. Click Delete to confirm the deletion of the default network.
   Wait for the network to be deleted before continuing.
5. In the left pane, click Routes.
   Notice that there are no routes. You may need to click Refresh in order to see this.
6. In the left pane, click Firewall.
   Notice that there are no firewall rules.

Note: Without a VPC network, there are no routes and no firewall rules!

Try to create a VM instance

Verify that you cannot create a VM instance without a VPC network.

1. On the Navigation menu (), click Compute Engine > VM instances.
2. Click Create Instance.
3. Accept the default values and click Create. Notice the error.
4. In the warning box, click Go to Issues(S). You may need to scroll down to see more information. There are no networks for this project and no subnetworks.
5. Click Cancel.

Note: As expected, you cannot create a VM instance without a VPC network!

Task 2. Create a VPC network and VM instances

Create a VPC network so that you can create VM instances.

Create an auto mode VPC network with Firewall rules

Replicate the default network by creating an auto mode network.

1. On the Navigation menu (), click VPC network > VPC networks.
2. Click Create VPC network.
3. For Name, type mynetwork.
4. For Subnet creation mode, click Automatic.
   Auto mode networks create subnets in each region automatically.
5. For Firewall, select all available rules.

These are the same standard firewall rules that the default network had.
The deny-all-ingress and allow-all-egress rules are also displayed, but you cannot check or uncheck them because they are implied. These two rules have a lower Priority (higher integers indicate lower priorities) so that the allow ICMP, Custom, RDP and SSH rules are considered first.

6. Click Create.

When the new network is ready, notice that a subnet was created for each region.

7. Record the IP address range for the subnets in and .
   These will be referred to in the next steps.

Note: If you ever delete the default network, you can quickly re-create it by creating an auto mode network as you just did.

Create a VM instance in

Create a VM instance in the region. Selecting a region and zone determines the subnet and assigns the internal IP address from the subnet's IP address range.

1. On the Navigation menu (), click Compute Engine > VM instances.

2. Click Create Instance.

3. Specify the following, and leave the remaining settings as their defaults:

   Property	Value (type value or select option as specified)
   Name	mynet-us-vm
   Region
   Zone
   Series	E2
   Machine type	e2-micro

4. Click Create.

5. Verify that the Internal IP for the new instance was assigned from the IP address range for the subnet in ..

   The Internal IP should be 10.128.0.2 because 10.128.0.1 is reserved for the gateway and you have not configured any other instances in that subnet.

Create a VM instance in

Create a VM instance in the region.

1. Click Create Instance.

2. Specify the following, and leave the remaining settings as their defaults:

   Property	Value (type value or select option as specified)
   Name	mynet-eu-vm
   Region
   Zone
   Series	E2
   Machine type	e2-micro

3. Click Create.

4. Verify that the Internal IP for the new instance was assigned from the IP address range for the subnet in .

   The Internal IP should be because 10.164.0.1 is reserved for the gateway and you have not configured any other instances in that subnet.

Note: The External IP addresses for both VM instances are ephemeral. If an instance is stopped, any ephemeral external IP addresses assigned to the instance are released back into the general Compute Engine pool and become available for use by other projects. When a stopped instance is started again, a new ephemeral external IP address is assigned to the instance.

Alternatively, you can reserve a static external IP address, which assigns the address to your project indefinitely until you explicitly release it.

Click Check my progress to verify the objective. Create a VPC network and VM instance

Task 3. Explore the connectivity for VM instances

Explore the connectivity for the VM instances. Specifically, try to SSH to your VM instances using tcp:22, and ping both the internal and external IP addresses of your VM instances using ICMP. Then explore the effects of the firewall rules on connectivity by removing the firewall rules individually.

Verify connectivity for the VM instances

The firewall rules that you created with mynetwork allow ingress SSH and ICMP traffic from within mynetwork (internal IP) and outside that network (external IP).

1. On the Navigation menu (), click Compute Engine > VM instances.
   Note the external and internal IP addresses for mynet-eu-vm.
2. For mynet-us-vm, click SSH to launch a terminal and connect.

Note: You can SSH because of the allow-ssh firewall rule, which allows incoming traffic from anywhere (0.0.0.0/0) for tcp:22. The SSH connection works seamlessly because Compute Engine generates an SSH key for you and stores it in one of the following locations:

• By default, Compute Engine adds the generated key to project or instance metadata.
• If your account is configured to use OS Login, Compute Engine stores the generated key with your user account.

Alternatively, you can control access to Linux instances by creating SSH keys and editing public SSH key metadata.

3. To test connectivity to mynet-eu-vm's internal IP, run the following command, replacing mynet-eu-vm's internal IP:

ping -c 3 <Enter mynet-eu-vm's internal IP here>

You can ping mynet-eu-vm's internal IP because of the allow-custom firewall rule.

4. To test connectivity to mynet-eu-vm's external IP, run the following command, replacing mynet-eu-vm's external IP:

ping -c 3 <Enter mynet-eu-vm's external IP here>

Note: You can SSH to mynet-us-vm and ping mynet-eu-vm's internal and external IP address as expected. Alternatively, you can SSH to mynet-eu-vm and ping mynet-us-vm's internal and external IP address, which also works.

Remove the allow-icmp firewall rules

Remove the allow-icmp firewall rule and try to ping the internal and external IP address of mynet-eu-vm.

1. On the Navigation menu (), click VPC network > Firewall.

2. Select the mynetwork-allow-icmp rule.

3. Click Delete.

4. Click Delete to confirm the deletion.
   Wait for the firewall rule to be deleted.

5. Return to the mynet-us-vm SSH terminal.

6. To test connectivity to mynet-eu-vm's internal IP, run the following command, replacing mynet-eu-vm's internal IP:

ping -c 3 <Enter mynet-eu-vm's internal IP here>

You can ping mynet-eu-vm's internal IP because of the allow-custom firewall rule.

7. To test connectivity to mynet-eu-vm's external IP, run the following command, replacing mynet-eu-vm's external IP:

ping -c 3 <Enter mynet-eu-vm's external IP here> Note: The 100% packet loss indicates that you cannot ping mynet-eu-vm's external IP. This is expected because you deleted the allow-icmp firewall rule!

Remove the allow-custom firewall rules

Remove the allow-custom firewall rule and try to ping the internal IP address of mynet-eu-vm.

1. On the Navigation menu (), click VPC network > Firewall.
2. Select the mynetwork-allow-custom rule.
3. Click Delete.
4. Click Delete to confirm the deletion.
   Wait for the firewall rule to be deleted.
5. Return to the mynet-us-vm SSH terminal.
6. To test connectivity to mynet-eu-vm's internal IP, run the following command, replacing mynet-eu-vm's internal IP:

ping -c 3 <Enter mynet-eu-vm's internal IP here> Note: The 100% packet loss indicates that you cannot ping mynet-eu-vm's internal IP. This is expected because you deleted the allow-custom firewall rule!

7. Close the SSH terminal:

exit

Remove the allow-ssh firewall rules

Remove the allow-ssh firewall rule and try to SSH to mynet-us-vm.

1. On the Navigation menu (), click VPC network > Firewall.
2. Select the mynetwork-allow-ssh rule.
3. Click Delete.
4. Click Delete to confirm the deletion.
5. Wait for the firewall rule to be deleted.
6. On the Navigation menu, click Compute Engine > VM instances.
7. For mynet-us-vm, click SSH to launch a terminal and connect.

Note: The Connection failed message indicates that you cannot SSH to mynet-us-vm because you deleted the allow-ssh firewall rule!

Task 4. Review

In this lab, you explored the default network along with its subnets, routes, and firewall rules. You deleted the default network and determined that you cannot create any VM instances without a VPC network. Thus, you created a new auto mode VPC network with subnets, routes, firewall rules, and two VM instances. Then you tested the connectivity for the VM instances and explored the effects of the firewall rules on connectivity.

End your lab

When you have completed your lab, click End Lab. Google Cloud Skills Boost removes the resources you’ve used and cleans the account for you.

You will be given an opportunity to rate the lab experience. Select the applicable number of stars, type a comment, and then click Submit.

The number of stars indicates the following:

• 1 star = Very dissatisfied
• 2 stars = Dissatisfied
• 3 stars = Neutral
• 4 stars = Satisfied
• 5 stars = Very satisfied

You can close the dialog box if you don't want to provide feedback.

For feedback, suggestions, or corrections, please use the Support tab.

Copyright 2022 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.