
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
Create a Cloud Storage Bucket
/ 25
Make a second Cloud Storage bucket
/ 25
Upload Files to Your Cloud Storage Bucket (demo-image1.png and demo-image2.png)
/ 25
Copy files between Cloud Storage buckets (demo-image1-copy.png)
/ 25
The Google APIs Explorer is a tool that helps you explore various Google APIs interactively. With the APIs Explorer, you can:
Cloud Storage allows world-wide storage and retrieval of any amount of data at any time. You can use Cloud Storage for a range of scenarios including serving website content, storing data for archival and disaster recovery, or distributing large data objects to users via direct download.
In this lab, you will use the APIs Explorer to make Cloud Storage API requests that create and delete Cloud Storage buckets. You will also learn how to copy and delete files in Cloud Storage.
In this lab, you will:
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.
To access the Cloud Storage APIs Explorer tool, from the Navigation menu select APIs & Services > Library.
In the search bar, type Cloud Storage.
Click on the Google Cloud Storage JSON API from the results list.
Make sure that API is enabled, if not click Enable.
Open the Buckets: insert reference. This will open a new tab with the APIs Explorer page loaded.
You will now be on the APIs Explorer page.
insert
method from Cloud Storage JSON API. You can view all API versions and its method in the API reference.
Your method should now resemble the following:
Click the Execute button.
Select the student account you started the lab with.
On the next screen, click Allow to give APIs Explorer access.
Your response should resemble the following:
Click Check my progress to verify the objective.
Now make another Cloud Storage bucket so you can get hands-on practice copying files between the two.
Still, in the insert
method, ensure that your Project ID is still in the project field.
In the request body, for the name key-value pair, give your second bucket a unique name.
Make sure that there are no trailing spaces in any of the fields.
Click the Execute button. Your response should resemble the following:
You have successfully created two buckets with the insert
method. Next you'll find them in the Cloud console.
Click Check my progress to verify the objective.
Return to the Cloud console and from the Navigation menu go to Cloud Storage to ensure that your Cloud Storage buckets were created.
From the Navigation menu select Cloud Storage > Buckets. You should see your newly created buckets added.
Remain in the Cloud console for the following step. Keep the APIs Explorer tab open.
Upload some files to your Cloud Storage bucket so you can get hands-on practice with methods housed in the APIs explorer.
In the Cloud Storage browser select the first bucket from the list.
Click Upload files and select demo-image1.png and demo-image2.png from your computer.
Your bucket should now have both image files added to it and should resemble the following:
Click Check my progress to verify the objective.
Next, you will copy one of the image files to your second Cloud Storage bucket.
From the left APIs & Reference section, navigate to JSON API > API reference > Objects > copy to copy
method or, to copy files between storage buckets using API Explorer, use the Objects: copy reference.
Update as follows:
Your method should resemble the following:
Make sure that there are no trailing spaces in any of the fields.
Now scroll down and click Execute.
You should receive a similar output:
You have successfully copied a file from one bucket to another using the objects.copy
method.
Click Check my progress to verify the objective.
Return to the Cloud console for this step. You should have left off on your Cloud Storage bucket details page.
From the left-hand menu, click Buckets and select your second bucket. You should see the copy of demo-image1.png added.
From the left APIs & Reference section navigate to JSON API > API reference > Objects > delete or, to delete files from a Cloud Storage bucket using API Explorer, use the Objects: delete reference.
Now you'll delete an image file from a Cloud Storage bucket.
Make sure that there are no trailing spaces in any of the fields.
Now scroll down and click Execute.
You should receive a similar output as below:
You have successfully deleted files from a bucket using the objects.delete
method. You will now view your removed file in the Cloud console.
Return to the Cloud console for this step. You should have left off on your Cloud Storage bucket details page.
From the left-hand menu, click Buckets and select your first bucket. You should see that both images have been removed.
buckets.delete
method or, to delete a Cloud Storage bucket using API Explorer, use the Buckets: delete reference.You will now delete your first (empty) Cloud Storage bucket.
Make sure that there are no trailing spaces in any of the fields.
Now scroll down and click Execute. You should receive a similar output:
You have successfully deleted a bucket using the buckets.delete
method.
Return to the Cloud console for this step. You should have left off on the Details page.
From the left-hand menu, click Buckets. You should see that your first bucket has been removed.
You have successfully completed all steps of the lab. You can end your lab here, or experiment with some new methods in the remaining time.
Below are multiple-choice questions to reinforce your understanding of this lab's concepts. Answer them to the best of your abilities.
In this lab you created Cloud Storage buckets with the APIs Explorer. You also copied and deleted image files with specific APIs Explorer methods. After deleting image files, you learned how to delete an entire bucket with the delete
method. At this point, you have a solid understanding of Cloud Storage and how you can provision this service's methods through the APIs Explorer.
For more practice with the APIs Explorer, try this lab:
APIs Explorer: Create and Update a Cluster
...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 November 04, 2024
Lab Last Tested November 04, 2024
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.