LogoLogo
Metadata for Integration Config
Metadata for Integration Config
  • INTEGRATION METADATA
    • Amazon Account
    • AWS EC2 SSH
    • Elastic Kubernetes Service (EKS)
    • AWS Lambda Custom Integration
    • Amazon Organization
    • AWS RDS MySQL
    • AWS RDS PostgreSQL
    • Amazon RDS
    • Entra ID (Azure AD) Groups
    • Azure Kubernetes Service (AKS)
    • Azure Management Group
    • Azure MySQL
    • Azure PostgreSQL
    • Azure Subscription
    • Azure VM SSH
    • Cloud Function Custom Integration
    • F5 Network
    • Google AlloyDB
    • Google BigQuery
    • Google Cloud SQL - MySQL
    • Google Cloud SQL - PostgreSQL
    • Google Kubernetes Engine (GKE)
    • Google Organization
    • Google Project
    • Github
    • JumpCloud
    • Kubernetes Proxy
    • Kubernetes
    • LDAP Group
    • MariaDB
    • Mongo Atlas Portal
    • MongoDB Atlas
    • MongoDB
    • Microsoft SQL Server
    • MySQL
    • Okta Group
    • OneLogin Group
    • 1Password
    • OpenVPN
    • Oracle Database
    • PostgreSQL
    • RabbitMQ
    • Rancher
    • RDP
    • Redis Cloud (Redislabs)
    • Amazon Redshift
    • Snowflake
    • SSH
    • Vertica Database
    • Web App
    • Windows Domain Controller
Powered by GitBook
On this page
  • Example Usage
  • Schema
  • Integration Config

Was this helpful?

Export as PDF
  1. INTEGRATION METADATA

Google AlloyDB

Google Cloud AlloyDB is a fully managed, high-performance PostgreSQL-compatible database service. It offers low-latency, automatic scaling, and integrates with Google Cloud’s AI/ML tools, making

Example Usage


gcp-alloydb-integration.tf
resource "apono_integration" "gcp-alloydb-integration" {
  name                     = "Google AlloyDB"
  type                     = "gcp-alloydb"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["gcp-alloydb-database"]
  metadata = {
    auth_type = "<Auth Type>"
    gcp_project_id = "<Project ID>"
    gcp_region = "<Location>"
    gcp_alloydb_cluster = "<Cluster ID>"
    gcp_instance_id = "<Primary Instance ID>"
    port = "<Port>"
    dbname = "<Database Name>"
    sslmode = "<SSL Mode>"
    credentials_rotation_period_in_days = "<Credentials rotation period (in days)>"
    credentials_cleanup_period_in_days = "<User cleanup after access is revoked (in days)>"
  }
  gcp_secret = {
    project    = "project_template_value"
    secret_id  = "gcp_secret_id_template_value"
  }
}
gcp-alloydb-integration.tf
resource "apono_resource_integration" "gcp-alloydb-integration" {
  name                     = "Google AlloyDB"
  type                     = "gcp-alloydb"
  connector_id             = "apono-connector-id"
  connected_resource_types = ["gcp-alloydb-database"]
  integration_config = {
    auth_type = "<Auth Type>"
    gcp_project_id = "<Project ID>"
    gcp_region = "<Location>"
    gcp_alloydb_cluster = "<Cluster ID>"
    gcp_instance_id = "<Primary Instance ID>"
    port = "<Port>"
    dbname = "<Database Name>"
    sslmode = "<SSL Mode>"
    credentials_rotation_period_in_days = "<Credentials rotation period (in days)>"
    credentials_cleanup_period_in_days = "<User cleanup after access is revoked (in days)>"
  }
  secret_store_config = {
    gcp = {
      project    = "project_template_value"
      secret_id  = "gcp_secret_id_template_value"
    }
}

Schema


  • type gcp-alloydb

  • connected_resource_types List of resource types to sync.

Available resource types you can use
  • gcp-alloydb-database

  • gcp-alloydb-table

  • gcp-alloydb-role

Integration Config


  • auth_type (Required | String) Auth Type

    • Possible values: gcp-alloydb-iam-auth, user-password

  • gcp_project_id (Required | String) Project ID

  • gcp_region (Required | String) Location

  • gcp_alloydb_cluster (Required | String) Cluster ID

  • gcp_instance_id (Required | String) Primary Instance ID

  • port (Required | String) Port

    • Default value: 5432

  • dbname (Required | String) Database Name

    • Default value: postgres

  • sslmode (Optional | String) SSL Mode

    • Possible values: disable, allow, prefer, require, verify-ca, verify-full

  • credentials_rotation_period_in_days (Optional | String) Credentials rotation period (in days)

  • credentials_cleanup_period_in_days (Optional | String) User cleanup after access is revoked (in days)

PreviousF5 NetworkNextGoogle BigQuery

Last updated 2 hours ago

Was this helpful?