Contents x
    AlloyDB
    • 3 Minutes to read
    • Dark
      Light
    Contents

    AlloyDB

    • 3 Minutes to read
    • Dark
      Light
    Article summary

    AlloyDB is a fully managed, PostgreSQL-compatible database service that's designed for your most demanding workloads, including hybrid transactional and analytical processing. AlloyDB pairs a Google-built database engine with a cloud-based, multi-node architecture to deliver enterprise-grade performance, reliability, and availability.

    Prerequisites

    Authorize Connection to AlloyDB

    In AlloyDB

    Create an AlloyDB Instance

    1. In your Google Cloud Console, look for AlloyDB and click on Create Cluster.
    2. Configure the Availability of the of the cluster, Location and Password for the default user.
    3. Under the Networking section, select the default network, and click on Set up connection. Use Automatically alocated IP range and finish setting up the connection.
    4. Click on Create Cluster to obtain a Private IP address.

    Create an Instance for AlloyDB Auth Proxy

    AlloyDB requires an auth proxy to make authorized, encrypted connections to an instance. You can follow GCP's instructions, to create your auth proxy and generate a connection string to use with Dataddo. However, we'll also continue below with a Dataddo-specific implementation.

    1. In your Google Cloud Console, go to the VM instances page and click on Create instance.
    2. Provide the name of the instance and set full access to all Cloud APIs. In the Network interfaces section, configure the VPC network configured for private services access to your AlloyDB instance.

    Install AlloyDB Auth Proxy on the Instance

    Connect to the instance you created in the previous step and download the auth proxy as per GCP instructions.

    Start the instance by running the command below.

    ./alloydb-auth-proxy "projects/<project-id>/locations/<region>/clusters/<alloydb-cluster-id>/instances/<alloydb-instance-id>" --address "0.0.0.0"

    Configure Network

    1. In the Google Cloud Console, go to the VPC Network and click on Create Firewall Rule.
    2. Add all Dataddo IPs using CIDR notation (e.g. 52.17.68.150/32) and set the port to default of 5432.
    3. Click on Create to finalize the process.

    In Dataddo

    1. In the Authorizers tab, click on Authorize New Service and select AlloyDB.
    2. You will be asked to fill the following fields:
      1. Server IP or Hostname: Public IP or hostname of your AlloyDB auth proxy instance.
      2. Database: Name of the database you will use for writing or reading the data. The default value is postgres.
      3. Username: AlloyDB username for accessing the database. The default value is postgres.
      4. Password: AlloyDB password to creating AlloyDB instance.
      5. Port: Port to connect to AlloyDB. The default value is 5432.
      6. TLS/SSL Settings: Keep the PREFER value, this will ensure the SSL connection when available. If you want to enforce SSL without a fallback to unencrypted connection, use REQUIRED.
    3. [Optional] Configure the connection via SSH tunnel. To do so, please follow these steps
    4. Click on Save.

    Create a New AlloyDB Destination

    1. On the Destinations page, click on the Create Destination button and select the destination from the list.
    2. Select your authorizer from the drop-down menu.
    3. Name your destination and click on Save.
    Need to authorize another connection?

    Click on Add new Account in drop-down menu during authorizer selection and follow the on-screen prompts. You can also go to the Authorizers tab and click on Add New Service.

    Create a Flow to AlloyDB

    1. Navigate to Flows and click on Create Flow.
    2. Click on Connect Your Data to add your source(s).
    3. Click on Connect Your Data Destination to add the destination.
    4. Choose the write mode and fill in the other required information.
    5. Check the Data Preview to see if your configuration is correct.
    6. Name your flow and click on Create Flow to finish the setup.

    Was this article helpful?
    What's Next