
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 cluster and instance
/ 30
Create and load a table
/ 40
Create a cluster and instance with CLI
/ 30
AlloyDB for PostgreSQL is a fully managed PostgreSQL-compatible database service for your most demanding enterprise database workloads. AlloyDB combines the best of Google with one of the most popular open-source database engines, PostgreSQL, for superior performance, scale, and availability.
In this lab, you perform several key fundamental tasks for creating and managing AlloyDB for PostgreSQL instances and databases.
In this lab, you learn how to perform the following tasks:
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.
First create an AlloyDB cluster. On the Cloud Console Navigation menu (), click on View all products, scroll down to the Databases section and then select AlloyDB.
Click Create cluster at the top of the page.
In the Configure your cluster section, fill in the following fields. Please be certain to select the Region value listed below. Leave the others at their default value.
Item | Value |
---|---|
Cluster ID | lab-cluster |
Password | Change3Me |
Region | |
Network | peering-network |
The private services access connection option was configured for this project when you started the lab. This step is required to allow access to the AlloyDB cluster.
Under Configure your primary instance, set the instance ID as lab-instance.
Select Multiple zones (Highly Available) in the Zonal availability section.
Select 2 vCPU, 16 GB as your machine type.
Scroll to the bottom of the page and click Create Cluster.
You're now on the Overview page for the new cluster you created. The bottom section contains details on your instance. Expand the Connectivity section. Please make note of the Private IP address in the instances section. Copy the Private IP address to a text file so that you can paste the value in a later step. Do not include the port number.
Click Check my progress to verify the objective.
A VM named, alloydb-client, containing the PostgreSQL client was provisioned for you at the start of the lab.
On the Navigation menu (), under Compute Engine click VM instances.
For the instance named alloydb-client, in the Connect column, click SSH to open a terminal window.
Set the following environment variable, replacing ALLOYDB_ADDRESS with the Private IP address of the AlloyDB instance.
Type \q to exit the psql client.
Another option to create tables and/or load data is by using a SQL file (.sql). A SQL file can contain DDL, DML or any supported SQL syntax. You will download and run a file containing DDL and DML, run that file, and then verify the load.
Run the following command to download a file containing DDL and DML for three tables: countries, departments, and jobs.
Type \q to exit the psql client.
Type exit to close the terminal window.
Click Check my progress to verify the objective.
The Cloud Console is very useful, but in some use cases you want to manage AlloyDB databases using other methods. Google Cloud services can also be managed through the command line tool named gcloud. The easiest way to use the gcloud CLI is via the Cloud Shell but it can also be installed on a wide variety of operating systems.
Creating an AlloyDB cluster instance via gcloud is very simple. Click Activate Cloud Shell at the top of the Google Cloud console.
In the Cloud Shell, create a new AlloyDB cluster using the command below.
If prompted Do you want to continue (Y/n)?
press Y
to continue.
You now have a solid understanding of several key tasks when using an AlloyDB for PostgreSQL database.
Manual Last Updated October 15, 2024
Lab Last Tested October 15, 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.
현재 이 콘텐츠를 이용할 수 없습니다
이용할 수 있게 되면 이메일로 알려드리겠습니다.
감사합니다
이용할 수 있게 되면 이메일로 알려드리겠습니다.
One lab at a time
Confirm to end all existing labs and start this one