Connect from Cloud Run

Create a cluster and its primary instance

1. In the Google Cloud console, go to the Clusterspage.

   Go to Clusters

2. Click Create cluster.

   The Google Cloud console presents you with a choice of cluster types. Select Highly available.

3. Click Continue.

   The Configure your clustersection expands.

4. Under Basic info, in the Cluster IDfield, enter my-cluster .

5. In the Passwordfield, enter any password you'd like. Take note of this password. You use it again later in this quickstart.

6. In the Regionfield, select us-central1 (Iowa) .

7. In Connectivity, in the Networkdrop-down, select default .

   If you have not set up private services access yet, a dialog labeled Private services access connection requiredappears.

   In the Private services access connection requireddialog, to create private services access connection, complete the following:

   1. Click Set up connection.

      A new pane labeled Enable Service Networking APIappears.

   2. In the pane, select Use an automatically allocated IP range.

   3. Click Continue.

   4. Click Create connection, and wait for the connection configuration to finish.

      The pane is removed.

8. Click Continue.

   The Configure your primary instancesection expands.

9. Under Basic info, in the Instance IDfield, enter my-primary .

10. For a Machinevalue, select 2 vCPU, 16 GB .

11. Click Create cluster.

    Wait for the cluster to get created.

Connect to your instance and create a database

1. If you are not in your newly created cluster Overviewpage, then in the Google Cloud console, go to the Clusterspage.

   Go to Clusters

2. To display the cluster Overviewpage, click the my-cluster cluster name.

3. In the navigation menu, click AlloyDB Studio.

4. In the Databaselist on the Sign in to AlloyDB Studiopage, select postgres .

5. In the Userdrop-down list, select postgres .

6. In the Passwordfield, enter the password you created in Create a cluster and its primary instance .

7. Click Authenticate. The Explorerpane displays a list of the objects in your database.

8. In the Editor 1tab, create a database:

     CREATE 
     
    DATABASE 
     
    quickstart_db 
    ; 
    
   

9. Click Run. Wait for the Statement executed successfully message to display in the Resultspane.

Find your project ID

1. Go to the Dashboardpage in the Google Cloud console.

   Go to Dashboard

2. Find the project ID on the Project infocard.

3. Take note of your project ID. You need it for the following step of this quickstart.

Populate Artifact Registry with an image of the sample application

1. In the Google Cloud console, open Cloud Shell.

   Open Cloud Shell

2. In Cloud Shell Editor, use the following command to clone the repository with the sample application code from GitHub:

    cloudshell_open  
   --repo_url  
    \ 
    "https://github.com/GoogleCloudPlatform/alloydb-auth-proxy" 
     
    \ 
   --dir  
    \ 
    "examples/go" 
     
    \ 
   --force_new_clone 
   

3. Create a repository in Artifact Registry for docker images:

    gcloud  
   artifacts  
   repositories  
   create  
   cloud-run-source-deploy  
   --location  
   us-central1  
   --repository-format = 
   docker  
   --project  
    PROJECT_ID 
    
   

   Replace PROJECT_ID with the ID of your project.

4. In the Authorize Cloud Shelldialog, click Authorize. This prompt does not appear if you have done this step previously.

5. To build a Docker container and publish it to Artifact Registry, use the following command:

      
   gcloud  
   builds  
   submit  
   --tag  
   us-central1-docker.pkg.dev/ PROJECT_ID 
   /cloud-run-source-deploy/run-sql  
   --project  
    PROJECT_ID 
    
   

   Replace PROJECT_ID with the ID of your project.

Understand the sample code

The sample application code for this quickstart is located in the examples/go directory of the GoogleCloudPlatform/alloydb-auth-proxy GitHub repository. The cloudshell_open command in the previous step automatically clones this repository and opens the correct directory for you.

How the code works

The application is written in the Go programming language and serves as a tool for collecting votes. The main logic is contained in the main.go file, which starts a web server and handles user requests.

The database connection is configured using environment variables, which you set up when you create the Cloud Run service. These variables tell the application how to connect to your AlloyDB instance, including the database name, user, password, and the instance's IP address. The code uses these variables to establish a secure connection to your AlloyDB database.

Why is the code in this repository?

The alloydb-auth-proxy repository contains the AlloyDB Auth Proxy, a tool that helps you securely connect to your AlloyDB instances. The repository also includes related libraries and examples, such as the Go application used in this quickstart.

You don't need the entire alloydb-auth-proxy project to connect to AlloyDB from Cloud Run. The cloudshell_open command clones the entire repository for your convenience, but the only files used to build the container for this quickstart are located in the examples/go directory.

Find the IP address for your new instance

1. In the Google Cloud console, go to the Clusterspage.

   Go to Clusters

2. Find the row in the table whose Resource nameis my-primary .

3. Take note of that row's Private IP address. You need it for the following step of this quickstart.

   The example format of the IP address is 172.19.209.2:5432 .

Create a service for Cloud Run

1. In the Google Cloud console, go to the Cloud Runpage.

   Go to Cloud Run

2. In the Servicestab, click Deploy Container.

3. In the Create servicepage, select the Deploy one revision from an existing container imageoption.

4. In the Container image URLfield, click Select.

5. In the Select container imagepane, complete the following steps:

   1. Select the Artifact registrytab.
   2. Expand us-central1-docker.pkg.dev/ PROJECT_ID /cloud-run-source-deploy .
   3. Expand run-sql .
   4. Select the latest image.
   5. Click Select.

6. In the Service namefield, enter quickstart-service .

7. Make sure us-central1 (Iowa) is selected in the Regionlist by default.

8. In the Authenticationsection, select Allow public access.

9. Ensure that CPU is only allocated during request processingis selected in the CPU allocation and pricingsection.

10. Expand the Container(s), Volumes, Networking, Securitysection.

11. In the Container(s)tab, select the Variables & secretstab and complete the following steps:

    1. In the Environment variablessection, click Add variable.

    2. Enter the following in the Name and Value fields:

       • DB_NAME : quickstart_db
       • DB_USER : postgres
       • DB_PASS : The password that you entered when you created the cluster in Create a cluster and its primary instance .
       • DB_PORT : 5432
       • INSTANCE_HOST : The IP address of your cluster's primary instance, which you found in Find the IP address for your new instance . Don't include the port number—for example, set to 172.19.209.2 , and not 172.19.209.2:5432 .

12. Switch from the Container(s)tab to the Networkingtab and complete the following steps:

    1. Select the Connect to a VPC for outbound trafficcheckbox.

    2. Select the Send traffic directly to a VPCoption.

    3. In the Networkdrop-down list, choose the default value.

    4. In the Subnetdrop-down list, ensure that the default value is selected.

13. Click Createto create the Cloud Run service.

    After the Cloud Run service is deployed, the quickstart-servicepage displays the URL of the sample application in the URLfield.

    The application uses AlloyDB as its datastore.

View the sample application

1. In the Google Cloud console, go to the Cloud Runpage.

   Go to Cloud Run

2. On the quickstart-servicepage, click content_copy Copy to clipboardto copy the application URL.

3. In a new browser tab, paste the copied application URL and click Enter.

   The sample vote-collecting web application that appears looks similar to the following: