
Before you begin
- Labs create a Google Cloud project and resources for a fixed time
- Labs have a time limit and no pause feature. If you end the lab, you'll have to restart from the beginning.
- On the top left of your screen, click Start lab to begin
Enable the Cloud Scheduler API
/ 10
Create two static IP addresses
/ 20
Create an instance with static IP address created earlier.
/ 20
Deploy cloud function
/ 20
Create App Engine Application
/ 10
Run a cloud schedular job
/ 10
Confirm the deletion of unused IP address
/ 10
In this lab, you use Cloud Run functions and Cloud Scheduler to identify and clean up wasted cloud resources. On Google Cloud, static IP addresses are a free resource when they’re attached to a load balancer or virtual machine (VM) instance. When a static IP address is reserved, but not used, it accumulates a hourly charge. In apps that heavily depend on static IP addresses and large-scale dynamic provisioning, this waste can become significant over time.
The following diagram describes the architecture used in the first section of this lab, where you schedule a Cloud Run function to identify and clean up unused IP addresses.
In this section, you configure the infrastructure and identities required to complete the lab.
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 are made available to you.
This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials you use to sign in and access Google Cloud for the duration of the lab.
To complete this lab, you need:
Click the Start Lab button. If you need to pay for the lab, a dialog opens for you to select your payment method. On the left is the Lab Details pane with the following:
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.
If necessary, copy the Username below and paste it into the Sign in dialog.
You can also find the Username in the Lab Details pane.
Click Next.
Copy the Password below and paste it into the Welcome dialog.
You can also find the Password in the Lab Details pane.
Click Next.
Click through the subsequent pages:
After a few moments, the Google Cloud console opens in this tab.
Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Cloud Shell provides command-line access to your Google Cloud resources.
Click Activate Cloud Shell at the top of the Google Cloud console.
Click through the following windows:
When you are connected, you are already authenticated, and the project is set to your Project_ID,
gcloud
is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell and supports tab-completion.
Output:
Output:
gcloud
, in Google Cloud, refer to the gcloud CLI overview guide.
In Cloud Shell, enable the Cloud Scheduler API:
Click Check my progress to verify the objective.
Clone the repository:
Set environment variables and make the repository folder your $WORKDIR where you run all commands related to this lab:
In Cloud Shell, navigate to the unused-ip directory:
Export the names of the IP addresses as variables:
Create two static IP addresses:
This lab uses the
Confirm that two addresses were created:
In the output, a status of RESERVED means that the IP addresses aren’t in use:
Click Check my progress to verify the objective.
Set the used IP address as an environment variable:
In Cloud Shell, create an instance:
Click Check my progress to verify the objective.
Confirm that one of the IP addresses is now in use:
The output is similar to the following:
In Cloud Shell, output the main section of the code:
The output is as follows:
In the preceding code sample, the following is important:
compute.getAddresses(function(err, addresses)
uses the getAddresses method to retrieve IP addresses across all regions in the project.
item.getMetadata(function(err, metadata, apiResponse)
gets the metadata for each IP address and checks its STATUS field.
if ((metadata.status=='RESERVED') & (calculateAge(metadata.creationTimestamp) >= ageToDelete)){
checks whether the IP address is in use, calculates its age by using a helper function, and compares its age against a constant (set to 0 for the purposes of the lab).
item.delete(function(err, operation, apiResponse2){
deletes the IP address.
Disable the Cloud Functions API:
Re-enable the Cloud Functions API:
Add the artifactregistry.reader
permission for your appspot service account. Replace [PROJECT_ID] with your qwiklabs Project ID.
In Cloud Shell, deploy the Cloud Run function:
Click Check my progress to verify the objective.
Set the trigger URL as an environment variable:
In Cloud Shell, create an App Engine app to use Cloud Scheduler:
In Cloud Shell, create a Cloud Scheduler task to run the Cloud Run function at 2 AM every night:
Click Check my progress to verify the objective.
Test the job by manually triggering it:
You should receive no output.
Click Check my progress to verify the objective.
Confirm that the unused IP address was deleted:
The output is similar to the following:
Click Check my progress to verify the objective.
In this lab, you completed the following tasks:
...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 January 15, 2025
Lab Last Tested January 15, 2025
Copyright 2025 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.
This content is not currently available
We will notify you via email when it becomes available
Great!
We will contact you via email if it becomes available
One lab at a time
Confirm to end all existing labs and start this one