GSP1036

Overview

In this lab, you will learn how to use Chrome Enterprise Premium and Identity-Aware Proxy (IAP) TCP forwarding to enable administrative access to VM instances that do not have external IP addresses or do not permit direct access over the internet.

What you'll learn

• Enable IAP TCP forwarding in your Google Cloud project
• Test connectivity to your Linux and Windows instances
• Configure the required firewall rules for BCE
• Grant permissions to use IAP TCP forwarding
• Demonstrate tunneling using SSH and RDP connections

Setup

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources will be made available to you.

This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

• Access to a standard internet browser (Chrome browser recommended).

Note: Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.

• Time to complete the lab---remember, once you start, you cannot pause a lab.

Note: If you already have your own personal Google Cloud account or project, do not use it for this lab to avoid extra charges to your account.

How to start your lab and sign in to the Google Cloud console

1. Click the Start Lab button. If you need to pay for the lab, a pop-up opens for you to select your payment method. On the left is the Lab Details panel with the following:

   • The Open Google Cloud console button
   • Time remaining
   • The temporary credentials that you must use for this lab
   • Other information, if needed, to step through this lab

2. Click Open Google Cloud console (or right-click and select Open Link in Incognito Window if you are running the Chrome browser).

   The lab spins up resources, and then opens another tab that shows the Sign in page.

   Tip: Arrange the tabs in separate windows, side-by-side.

   Note: If you see the Choose an account dialog, click Use Another Account.

3. If necessary, copy the Username below and paste it into the Sign in dialog.

   {{{user_0.username | "Username"}}}

   You can also find the Username in the Lab Details panel.

4. Click Next.

5. Copy the Password below and paste it into the Welcome dialog.

   {{{user_0.password | "Password"}}}

   You can also find the Password in the Lab Details panel.

6. Click Next.

   Important: You must use the credentials the lab provides you. Do not use your Google Cloud account credentials. Note: Using your own Google Cloud account for this lab may incur extra charges.

7. Click through the subsequent pages:

   • Accept the terms and conditions.
   • Do not add recovery options or two-factor authentication (because this is a temporary account).
   • Do not sign up for free trials.

After a few moments, the Google Cloud console opens in this tab.

Note: To view a menu with a list of Google Cloud products and services, click the Navigation menu at the top-left.

You will need a RDP client pre-installed so that you can connect and test Windows instances.

Task 1. Enable IAP TCP forwarding in your Google Cloud project

1. Open the Navigation Menu and select APIs and Services > Library.

2. Search for IAP and select Cloud Identity-Aware Proxy API.

3. Click Enable.

Task 2. Create Linux and Windows instances

Create three instances for this lab: - Two for demonstration purposes (Linux and Windows) - One for testing connectivity (Windows)

Linux instance

1. From the Navigation Menu and select Compute Engine.

2. Click Create instance.

3. In the Machine configuration:

   Select the following values:

   • Name: linux-iap
   • Zone:

4. Click Networking.

   For Network interfaces, click the default network dropdown to edit. Then change the External IPV4 address to None.

5. Click Done.

   

6. Then click create. This VM will be referred to as linux-iap

Windows instances

1. To create the Windows Demo VM click Create instance.

2. In the Machine configuration:

   Select the following values:

   • Name: windows-iap
   • Zone:

3. Click OS and Storage section.

   Click Change to begin configuring your boot disk and select the following values:

   • Public Images > Operating system > Windows Server
   • Version > Windows Server 2016 Datacenter

   

   Click Select.

4. Click Networking.

   For Network interfaces, click the default network dropdown to edit. Then change the External IPV4 address to None. Click Done.

5. Then click create. This VM will be referred to as windows-iap

6. To create the Windows Connectivity VM, click Create instance.

7. In the Machine configuration:

   Select the following values:

   • Name: windows-connectivity
   • Zone:

8. Click OS and Storage section, click on Change

   For the OS, set the following on the Custom Images tab:

   • Source project for images: Qwiklabs Resources
   • Image: iap-desktop-v001

   Click Select.

9. Click Security.

   In the Access scopes section, select Allow full access to all Cloud APIs.

   Do not disable external IP for this instance

10. Then click create. This VM will be referred to as windows-connectivity

Check if all 3 instances have been created

Task 3. Test connectivity to your Linux and Windows instances

1. After the instances are created, You will test access to linux-iap and windows-iap to ensure that you aren’t able to access the VMs without the external IP.

2. For linux-iap click on the SSH button to get into the machine and ensure you get a message similar to the following.

   

3. For windows-iap: click the RDP button and ensure you get a message similar to the following:

   

The following steps for configuring and using IAP will allow you to connect to the instances that don’t have external IPs.

Task 4. Configure the required firewall rules for BCE

1. Open the Navigation Menu and select VPC Network > Firewall and click Create Firewall Rule

2. Configure the following settings:

Field	Setting
Name	allow-ingress-from-iap
Direction of traffic	Ingress
Target	All instances in the network
Source filter	IPv4 Ranges
Source IPv4 Ranges	35.235.240.0/20
Protocols and ports	Select TCP and enter 22, 3389 to allow both SSH and RDP respectively

3. Click CREATE to create the firewall rule.

Check proper firewall rules have been created.

Task 5. Grant permissions to use IAP TCP forwarding

Use the following steps to configure the iap.tunnelResourceAccessor role by VM.

1. Open Navigation Menu and select Security > Identity-Aware Proxy, switch to the SSH and TCP Resources tab (safely ignore the Oauth Consent screen error in the HTTPS section).
2. Select the linux-iap and windows-iap VM instances.
3. Click Add principal, then enter in the service account associated with your Windows connectivity VM. This should be of the form -compute@developer.gserviceaccount.com.
4. Select Cloud IAP > IAP-Secured Tunnel User for the role.
5. Click SAVE.
6. From the top-right of the page click the "S" icon to open your profile and copy the email of the student account.
7. Click Add principal again to add your student account.
8. Enter in the student account. You can copy this value from the lab details pane.
9. Select Cloud IAP > IAP-Secured Tunnel User for the role.
10. Click SAVE.

The IAP-Secured Tunnel User role will grant the windows-connectivity instance to connect to resources using IAP. Adding the student account will help verify the step was done correctly.

Check that IAM roles have been set for the service account.

Task 6. Use IAP Desktop to connect to the Windows and Linux instances

It is possible to use IAP Desktop to connect to instances using a graphical user interface from an instance with Windows Desktop. You can read more about IAP Desktop on the GitHub repository hosting the download for the tool.

To use IAP Desktop to connect to the instances in this lab:

1. RDP to the windows-connectivity instance by downloading the RDP file. Go to the Compute Engine > VM Instances page. Select the down arrow next to the windows-connectivity instance on the Compute Engine landing page and download the file.

2. Open the RDP file to connect to the instance via Remote Desktop Protocol. You will use the credentials below to connect to the instance once prompted:

   • Username: student
   • Password: Learn123!

3. Once connected to the windows-connectivity instance, locate and open the IAP Desktop application on the desktop of the instance.

4. Once the application opens, click on the sign in with Google button to log in. Use the username and password provided in the lab console to authenticate with IAP Desktop. When you're prompted to continue, click Continue, and click Allow.

5. You will need to add the project to connect to Compute Engine instances within IAP Desktop after authentication. Select the lab project associated with your lab instance:

6. Double click on the windows-iap instance in the IAP Desktop application to log into the instance.

7. You may be prompted to provide credentials for the instance the first time you try to connect to it through IAP Desktop. Select "Generate new credentials" the first time logging into the instance.

8. Click OK for Generate logon credentials popup.

9. After the credentials are created you will be taken to the desktop of the windows-iap instance and can see the end user experience.

Task 7. Demonstrate tunneling using SSH and RDP connections

1. You will test connectivity to the RDP instance using an RDP client. This is because you need to connect to the instance via an IAP tunnel locally.

2. Go to the Compute Engine > VM Instances page.

3. For the windows-connectivity instance click the down arrow and select Set windows password. Copy the password and save it.

4. Then click down arrow next to connect and click download the RDP file. Open the RDP file with your client and enter in your password.

5. Once you have connected to the windows-connectivity instance. Open the Google Cloud Shell SDK:

   

6. Now from the command line enter the following command to see if you can connect to the linux-iap instance:

   gcloud compute ssh linux-iap

   Click Y when prompted to continue and to select the zone.

   Make sure that you select the right zone for the instance when prompted.

7. Then Accept the Putty security alert.

You should receive a message that no external IP address was found and that it will use IAP tunneling.

8. Update Putty Settings to allow Tunnel connections locally. Click the top left corner of the Putty Window > Change Settings.

   

9. Allow local ports to accept connections from other hosts by checking the checkbox "Local ports accept connections from other hosts".

   

10. Close the Putty session and click Apply. Use the following command to create an encrypted tunnel to the RDP port of the VM instance:

    gcloud compute start-iap-tunnel windows-iap 3389 --local-host-port=localhost:0 --zone={{{ project_0.default_zone | Zone }}}

    Once you see the message about “Listening on port [XXX].” Copy the tunnel port number.

11. Return to the Google Cloud Console and go to the Compute Engine > VM Instances page.

12. Set and copy the password for the windows-iap instance.

    Return to the RDP session now.

13. Leave gcloud running and open the Microsoft Windows Remote Desktop Connection app.

14. Enter the tunnel endpoint where the endpoint is the tunnel port number from the earlier step like so:

    • localhost:endpoint
    

15. Click Connect.

    Then enter the previous credentials you copied earlier. You will be successfully RDPed into your instance now!

    If prompted click Yes.

    

You were able to access the instance even without an external IP address using IAP Confirm VM is accessible via IAP enabled SA Congratulations! You were able to successfully connect to both instances using IAP.

Congratulations

You learned how to use BeyondCorp Enterprise (BCE) and Identity-Aware Proxy (IAP) TCP forwarding by deploying 2 VM's, windows-iap and linux-iap, without IP addresses and configuring an IAP tunnel which gave you access to both instances using a third VM, windows-connectivity.

Next steps/ Learn more

• Read more about BeyondCorp Enterprise (BCE) and the zero trust security model at the following cloud documentation site.

Google Cloud training and certification

...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.

Manual Last Updated December 11, 2024

Lab Last Tested November 25, 2024

Copyright 2024 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.