Before you can begin using AlloyDB as a Supermetrics destination, ensure that you’ve met the prerequisites below.
Prerequisites
AlloyDB Cluster and PostgreSQL database
You need an existing cluster for AlloyDB, and a PostgreSQL database set up inside that cluster.
Permissions
If you’d prefer to create the destination with a user account, make sure it has permission to:
- Access and ability to create, query, update, rename, drop, insert and delete from objects in a given schema within a Postgres database. Learn more about access privileges in PostgreSQL.
- Query table and column metadata information in “information_schema.tables” and “information_schema.columns”. Learn more about PostgreSQL information schema.
- For example, your database admin could run the following SQL statements to create a user that should be able to create successful transfers:
- CREATE user [set user name] WITH CREATEDB PASSWORD [set password]
- GRANT ALL ON DATABASE [database name] TO [user name]
- GRANT ALL ON SCHEMA [schema name/s] TO [user name]
- GRANT ALL ON ALL TABLES IN SCHEMA [schema name/s] TO [user name]
- Note that it’s also possible to take a more granular approach in terms of granting privileges on database objects.
Alternatively, you can use your database admin login credentials to create the destination on the Supermetrics Hub.
IP allowlisting
If your organization only allows access from “selected networks”, you need to add the Supermetrics IP addresses to the allowlist in your firewall settings. Don't forget to add your own IP address. Learn about the permissions you need to modify firewall settings.
Please note that you need to do the IP allowlisting for the server or server groups where AlloyDB Auth proxy is running in.