Getting started with Databases for PostgreSQL

Step 1: Provision through the console

1. Log in to the IBM Cloud console.

2. Click the Databases for PostgreSQL service in the catalog.

3. In Service details, configure the following:

   • Location - Select a location that supports Gen 2
   • Service name - The name can be any string and is the name that is used on the web and in the CLI to identify the new instance.
   • Resource group - If you are organizing your services into resource groups. For more information, see Managing resource groups.

4. Resource allocation - Select an isolated compute instance with a certain amount of RAM and CPU cores. Changing resource allocation requires selecting a different host size. Once provisioned, disk cannot be scaled down.

5. In Service configuration, configure the following:

   • Database version Set only at deployment - The deployment version of your database. To ensure optimal performance, run the preferred version. The latest minor version is used automatically. For more information, see Database versioning policy.
   • Encryption - If you use Key Protect, an instance and key can be selected to encrypt the instance's disk. If you do not use your own key, the instance automatically creates and manages its own disk encryption key.

6. Click Create. The Cloud Databases Resource list page opens.

7. When your instance has been provisioned, click the instance name to view more information.

As part of provisioning a new instance in IBM Cloud®, you can use the service credential console page to create a user with different roles (Manager and Writer).

Databases for PostgreSQL instances no longer include a default admin user. Instead, customers create a user with the Manager or Writer role using the IBM Cloud® service credential interface — via UI or CLI. These users come with necessary credentials to connect to and manage the instance.

Step 1: Provision through the CLI

You can provision a Databases for PostgreSQL instance through the CLI. If you don't already have it, you need to install the IBM Cloud CLI.

1. Log in to IBM Cloud with the following command:

   ibmcloud login
   

   If you use a federated user ID, it's important that you switch to a one-time passcode (ibmcloud login --sso), or use an API key (ibmcloud --apikey key or @key_file) to authenticate. For more information about how to log in using the CLI, see General CLI (ibmcloud) commands under ibmcloud login.

2. Create a Databases for PostgreSQL instance.

   Select one of the following methods:

   • To create an instance from the CLI on the Enterprise plan, run the following command:

     ibmcloud resource service-instance-create <INSTANCE_NAME> databases-for-postgresql standard-gen2 <LOCATION> -g <RESOURCE_GROUP>
     

     This provisions a PG instance with the default of 2 members and 10 GB disk, as well as the smallest host flavor available in the location you selected.

     Alternatively, you can specify custom values for these parameters by passing in the parameters flag:

     ibmcloud resource service-instance-create <INSTANCE_NAME> databases-for-postgresql standard-gen2 <LOCATION> -g <RESOURCE_GROUP> -p '{"dataservices": {"postgresql": {"storage_gb": 40, "members": 3, "host_flavor": "bx3d.8x40"}}}'
     

     This will provision a PG instance with 3 members, 40GB of storage per member running on hosts of flavor bx3d.8x40.

     If you pass in unsupported values, the create command will fail with a message indicating which values are invalid, for example, when passing in an unsupported number of members:

     Message: The broker for 'Databases for PostgreSQL' service returned error, [400, Bad Request] invalid members '5', allowed values: 2, 3. If this is unexpected, open a support ticket with the service to help troubleshoot the issue.

     Or, an unsupported disk size:

     Message: The broker for 'Databases for PostgreSQL' service returned error, [400, Bad Request] invalid storage size '10000', only integer values between 10 and 9600 are allowed. If this is unexpected, open a support ticket with the service to help troubleshoot the issue.

     Passing in any other key-value pairs that are not supported by the service will result in a corresponding error message as well.

     Supported parameters:

     • storage_gb (valid integer values between 10 and 9600, representing disk storage per member in GB)
     • members(valid integer values '2' and '3', indicating whether to run PG with 2 zone HA or 3 zone HA).
     • host_flavor(values depend on location)

   The fields in the command are described in the table that follows.

   Basic command format fields

   Field	Description	Flag
   NAME Required	The instance name can be any string and is the name that is used on the web and in the CLI to identify the new instance.
   SERVICE_NAME Required	Name or ID of the service. For Databases for PostgreSQL, use databases-for-postgresql.
   SERVICE_PLAN_NAME Required	Standard plan (standard).
   LOCATION Required	The location where you want to deploy. To retrieve a list of regions, use the ibmcloud regions command.
   SERVICE_ENDPOINTS_TYPE	Configure the Service endpoints of your instance, private.
   RESOURCE_GROUP	The Resource group name. The default value is default.	-g
   --parameters	JSON file or JSON string of parameters to create service instance.	-p

3. Use the following command to check the provisioning status:

   ibmcloud resource service-instance <INSTANCE_NAME>
   

ibmcloud cdb deployment-connections example-postgres --start

ibmcloud resource service-instance-create databases-for-postgresql <SERVICE_NAME> standard us-south \
-p \ '{
  "backup_id": "crn:v1:blue:public:databases-for-postgresql:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6",
  "members_memory_allocation_mb": "3072"
}'

Step 1: Provision through the resource controller API

Follow these steps to provision by using the resource controller API.

1. Obtain an IAM token from your API token.

2. You need to know the ID of the resource group to which you would like to deploy. This information is available through the IBM Cloud CLI.

   Use a command like:

   ibmcloud resource groups
   

3. You need to know the region where you would like to deploy.

   To list all of the regions that instances can be provisioned into from the current region, use the Cloud Databases CLI.

   The command looks like:

   ibmcloud cdb regions --json
   

   Once you have all the information, provision a new resource instance with the IBM Cloud resource controller.

   curl -X POST \
     https://resource-controller.cloud.ibm.com/v2/resource_instances \
     -H 'Authorization: Bearer <>' \
     -H 'Content-Type: application/json' \
       -d '{
       "name": "my-instance",
       "target": "blue-us-south",
       "resource_group": "5g9f447903254bb58972a2f3f5a4c711",
       "resource_plan_id": "databases-for-postgresql-standard"
     }'
   

   The parameters name, target, resource_group, and resource_plan_id are all required.

Supported parameters:

  - `storage_gb` (valid integer values are between 10 and 9600, representing disk storage per member in GB)
  - `members`(valid integer values are '2' and '3', indicating whether to run PG with two-zone HA or three-zone HA)
  - `host_flavor`(values depend on location).

List of additional parameters

• backup_id- A CRN of a backup resource to restore from. The backup must be created by a database instance with the same service ID. The backup is loaded after provisioning and the new instance starts up that uses that data. A backup CRN is in the format crn:v1:<...>:backup:<uuid>. If omitted, the database is provisioned empty.

• version - The version of the database to be provisioned. If omitted, the database is created with the most recent major and minor version.

• disk_encryption_key_crn - The CRN of a KMS key (Key Protect), which is then used for disk encryption. A KMS key CRN is in the format crn:v1:<...>:key:<id>.

• backup_encryption_key_crn - The CRN of a KMS key (for example, [Key Protect), which is then used for backup encryption. A KMS key CRN is in the format crn:v1:<...>:key:<id>.

  To use a key for your backups, you must first enable the service-to-service delegation.

• service_endpoints - The Service endpoints supported on your instance,private. This is a required parameter.

Step 1: Provision through Terraform

Initialize your Terraform project:

terraform init

This downloads the IBM Cloud provider plug-in and initializes your workspace.

Review the planned changes:

terraform plan

If the plan looks correct, apply the configuration:

terraform apply

Type yes when prompted to confirm. The provisioning process takes approximately 15-20 minutes.

If you are using short-lived OAuth tokens, the token might expire during the provisioning process, causing terraform apply to fail with an authentication error. If this occurs:

1. Mark the resource as successfully created:

   terraform untaint ibm_resource_instance.pg_demo
   

2. Refresh your authentication by exporting a new IC_API_KEY.

3. Rerun the apply:

   terraform apply
   

   You'll see output similar to:

   database = "postgres"
   host_flavor = "bx3d.8x40"
   hostname = "0b917284-1ab8-4b44-8aa5-dceab4812863.private.uhp.ca-mon.postgresql.dataservices.appdomain.cloud"
   instance_crn = "crn:v1:bluemix:public:databases-for-postgresql:ca-mon:a/23b09aee04da4545b6e32805fa93249d:0b917284-1ab8-4b44-8aa5-dceab4812863::"
   instance_id = "0b917284-1ab8-4b44-8aa5-dceab4812863"
   instance_status = "active"
   members = "3"
   memory_gb = "40"
   pg_manager_password = "lXcjb8q-2)ItFOq7l5)KtLgj%PmhFN,)"
   pg_manager_psql = "postgres://ibmcloud_692fd265b48b4904a5dfdbe1dd218cb3:lXcjb8q-2%29ItFOq7l5%29KtLgj%25PmhFN,%29@0b917284-1ab8-4b44-8aa5-dceab4812863.private.uhp.ca-mon.postgresql.dataservices.appdomain.cloud:5432/postgres?sslmode=verify-full"
   pg_manager_role = "Manager"
   pg_manager_username = "ibmcloud_692fd265b48b4904a5dfdbe1dd218cb3"
   port = "5432"
   postgresql_cpu_count = "8"
   postgresql_version = "18"
   psql_connection_string = "PGUSER=$PGUSER PGPASSWORD=$PGPASSWORD PGSSLMODE=verify-full PGSSLROOTCERT=system psql 'host=0b917284-1ab8-4b44-8aa5-dceab4812863.private.uhp.ca-mon.postgresql.dataservices.appdomain.cloud port=5432 dbname=postgres'"
   storage_gb = "9600"
   

Step 2: Creating the Manager user via console

pg_read_all_data
pg_write_all_data
pg_monitor
pg_read_all_settings
pg_read_all_stats
pg_stat_scan_tables
pg_signal_backend
pg_checkpoint
pg_create_subscription

GRANT pg_signal_backend TO joe;

GRANT pg_monitor TO mary;

Step 2: Creating the Manager user via the CLI

Databases for PostgreSQL instances no longer include a default admin user. Instead, you create a user with the Manager or Writer role using the IBM Cloud® service credential interface — via UI or CLI. These users come with necessary credentials to connect to and manage the instance.

The Manager user functions as a admin-like user and is automatically granted the PostgreSQL default role pg_monitor, which provides access to monitoring views and functions within the database. The created user has the CREATEROLE and CREATEDB privileges, inheriting permissions from both ibm_admin and ibm_writer, enabling broader access and management capabilities within the deployment.

Use one of the following commands from the IBM Cloud CLI Cloud Databases plug-in to create the Manager user.

ibmcloud resource service-key-create <service_key_name> Manager --instance-name <instance_name>

ibmcloud resource service-key-create <service_key_name> Manager --instance-id <guid>

These commands can be used when creating a user with either the Writer or Manager role. In this example, the command creates a PostgreSQL user (ibmcloud_d0388…) with CREATEROLE and CREATEDB privileges. This user inherits permissions from both ibm_admin and ibm_writer, enabling broader access and management capabilities within the instance.

rolname	rolsuper	rolinherit	rolcreaterole	rolcreatedb	rolcanlogin	memberof
ibm_admin						{pg_read_all_data,pg_write_all_data,pg_monitor,pg_read_all_settings,pg_read_all_stats,pg_stat_scan_tables,pg_signal_backend,pg_checkpoint,pg_create_subscription}
ibm_monitoring						{pg_use_reserved_connections}
ibm_rest						{pg_use_reserved_connections,ibm_admin,ibm_writer,ibmcloud_d0388c96d13841b1b45f1039c73ea6c7}
ibm_rewind						{}
ibm_superuser						{}
ibm_writer						{pg_read_all_data,pg_write_all_data}
ibmcloud_d0388c96d13841b1b45f1039c73ea6c7						{ibm_admin,ibm_writer}
{: caption="ibm_admin and ibm_writer permissions" caption-side="top"}

Similarly, for creating a user with the Writer role, use the following command, updating the 'role_crn' to 'Writer' instead of 'Manager:

ibmcloud resource service-key-create <service_key_name> --instance-name <INSTANCE_NAME> -p '{"role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Writer"}'

The user (ibmcloud_b153...) with writer role inherits the ibm_writer permissions:

rolname	rolsuper	rolinherit	rolcreaterole	rolcreatedb	rolcanlogin	memberof
ibm_admin						{pg_read_all_data,pg_write_all_data,pg_monitor,pg_read_all_settings,pg_read_all_stats,pg_stat_scan_tables,pg_signal_backend,pg_checkpoint,pg_create_subscription}
ibm_monitoring						{pg_monitor,pg_use_reserved_connections}
ibm_replication						{pg_use_reserved_connections}
ibm_rest						{pg_use_reserved_connections,ibm_admin,ibm_writer,ibmcloud_b153b496ae5a41a08a27db730e43b835}
ibm_rewind						{}
ibm_superuser						{}
ibm_writer						{pg_read_all_data,pg_write_all_data}
ibmcloud_b153b496ae5a41a08a27db730e43b835						{ibm_writer}
{: caption="ibm_writerpermissions" caption-side="top"}

ibmcloud resource service-key-delete <service_key_name>

ALTER ROLE username WITH PASSWORD 'new_password';

ibmcloud cdb deployment-connections example-postgres --start

ibmcloud resource service-instance-create databases-for-postgresql <SERVICE_NAME> standard us-south \
-p \ '{
  "backup_id": "crn:v1:blue:public:databases-for-postgresql:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6",
  "members_memory_allocation_mb": "3072"
}'

Step 2: Creating the Manager user via API

As part of provisioning a new instance in IBM Cloud®, you can use the service credential console page to create a user with different roles (Manager and Writer).

Databases for PostgreSQL instances no longer include a default admin user. Instead, you create a user with the Manager or Writer role using the IBM Cloud® service credential interface — via UI or CLI. These users come with necessary credentials to connect to and manage the instance.

The Manager user functions as a admin-like user and is automatically granted the PostgreSQL default role pg_monitor, which provides access to monitoring views and functions within the database. The created user has the CREATEROLE and CREATEDB privileges, inheriting permissions from both ibm_admin and ibm_writer, enabling broader access and management capabilities within the deployment.

The manageruser (admin-like) comes with the following roles:

pg_read_all_data
pg_write_all_data
pg_monitor
pg_read_all_settings
pg_read_all_stats
pg_stat_scan_tables
pg_signal_backend
pg_checkpoint
pg_create_subscription

When the Manager user (admin-like) creates a resource in a database, like a table, the user owns that object. Resources that are created by the Manager user are not accessible by other users, unless you explicitly grant permissions to them.

The biggest difference between the Manager user and any other users you add to your instance is the pg_monitor and pg_signal_backend roles. The pg_monitor role provides a set of permissions that makes the Manager user appropriate for monitoring the database server. The pg_signal_backend role provides the Manager user the ability to send signals to cancel queries and connections that are initiated by other users. It is not able to send signals to processes owned by superusers.

You can also use the Manager user to grant roles to other users on your instance.

To expose the ability to cancel queries to other database users, grant the pg_signal_backend role from the Manager user. Use a command like:

GRANT pg_signal_backend TO joe;

To set up a specific monitoring user, mary, use a command like:

GRANT pg_monitor TO mary;

Step 2: Creating the Manager user via Terraform

As part of provisioning a new instance in IBM Cloud®, you can use the service credential console page to create a user with different roles (Manager and Writer).

Databases for PostgreSQL instances no longer include a default admin user. Instead, you create a user with the Manager or Writer role using the IBM Cloud® service credential interface — via UI or CLI. These users come with necessary credentials to connect to and manage the instance.

The Manager user functions as a admin-like user and is automatically granted the PostgreSQL default role pg_monitor, which provides access to monitoring views and functions within the database. The created user has the CREATEROLE and CREATEDB privileges, inheriting permissions from both ibm_admin and ibm_writer, enabling broader access and management capabilities within the deployment.

The manageruser (admin-like) comes with the following roles:

pg_read_all_data
pg_write_all_data
pg_monitor
pg_read_all_settings
pg_read_all_stats
pg_stat_scan_tables
pg_signal_backend
pg_checkpoint
pg_create_subscription

When the Manager user (admin-like) creates a resource in a database, like a table, the user owns that object. Resources that are created by the Manager user are not accessible by other users, unless you explicitly grant permissions to them.

The biggest difference between the Manager user and any other users you add to your instance is the pg_monitor and pg_signal_backend roles. The pg_monitor role provides a set of permissions that makes the Manager user appropriate for monitoring the database server. The pg_signal_backend role provides the Manager user the ability to send signals to cancel queries and connections that are initiated by other users. It is not able to send signals to processes owned by superusers.

You can also use the Manager user to grant roles to other users on your instance.

To expose the ability to cancel queries to other database users, grant the pg_signal_backend role from the Manager user. Use a command like:

GRANT pg_signal_backend TO joe;

To set up a specific monitoring user, mary, use a command like:

GRANT pg_monitor TO mary;

Step 3: Create a connection

The Connect tab in Gen 2 provides guided instructions for creating a secure connection to your Databases for PostgreSQL deployment.

Because Gen 2 supports private endpoints only, all connections are established through the IBM Cloud® private network. The Create a connection view walks you through the required setup to connect securely from your infrastructure, such as a Virtual Server Instance (VSI), by using Virtual Private Endpoint (VPE) gateway.

This guided experience is designed to help you configure a production-ready, secure connection without exposing your database to the public internet.

Also, the sections below provide a clear overview of how a connection is established within the VPC environment.

• Create a VPC (Virtual Private Cloud): A VPC is your own isolated network within IBM Cloud® where you can securely run resources.
• Generate an SSH key: SSH keys allow you to securely connect to your virtual servers.
• Provision a Virtual Server Instance (VSI): A VSI is your cloud-based server where applications and workloads will run.
• Reserve a floating IP for your VSI: A floating IP is a public IP address that lets you access your VSI from the internet.
• Create a Virtual Private Endpoint (VPE): A VPE provides secure, private connectivity to IBM Cloud services.

Step 3: Create a connection

The Connect tab in Gen 2 provides guided instructions for creating a secure connection to your Databases for PostgreSQL deployment.

Because Gen 2 supports private endpoints only, all connections are established through the IBM Cloud® private network. The Create a connection view walks you through the required setup to connect securely from your infrastructure, such as a Virtual Server Instance (VSI), by using Virtual Private Endpoint (VPE) gateway.

This guided experience is designed to help you configure a production-ready, secure connection without exposing your database to the public internet.

Also, the sections below provide a clear overview of how a connection is established within the VPC environment.

• Create a VPC (Virtual Private Cloud): A VPC is your own isolated network within IBM Cloud® where you can securely run resources.
• Generate an SSH key: SSH keys allow you to securely connect to your virtual servers.
• Provision a Virtual Server Instance (VSI): A VSI is your cloud-based server where applications and workloads will run.
• Reserve a floating IP for your VSI: A floating IP is a public IP address that lets you access your VSI from the internet.
• Create a Virtual Private Endpoint (VPE): A VPE provides secure, private connectivity to IBM Cloud services.

Step 3: Create a connection

The Connect tab in Gen 2 provides guided instructions for creating a secure connection to your Databases for PostgreSQL deployment.

Because Gen 2 supports private endpoints only, all connections are established through the IBM Cloud® private network. The Create a connection view walks you through the required setup to connect securely from your infrastructure, such as a Virtual Server Instance (VSI), by using Virtual Private Endpoint (VPE) gateway.

This guided experience is designed to help you configure a production-ready, secure connection without exposing your database to the public internet.

Also, the sections below provide a clear overview of how a connection is established within the VPC environment.

• Create a VPC (Virtual Private Cloud): A VPC is your own isolated network within IBM Cloud® where you can securely run resources.
• Generate an SSH key: SSH keys allow you to securely connect to your virtual servers.
• Provision a Virtual Server Instance (VSI): A VSI is your cloud-based server where applications and workloads will run.
• Reserve a floating IP for your VSI: A floating IP is a public IP address that lets you access your VSI from the internet.
• Create a Virtual Private Endpoint (VPE): A VPE provides secure, private connectivity to IBM Cloud services.

Step 3: Create a connection

The Connect tab in Gen 2 provides guided instructions for creating a secure connection to your Databases for PostgreSQL deployment.

Because Gen 2 supports private endpoints only, all connections are established through the IBM Cloud® private network. The Create a connection view walks you through the required setup to connect securely from your infrastructure, such as a Virtual Server Instance (VSI), by using Virtual Private Endpoint (VPE) gateway.

This guided experience is designed to help you configure a production-ready, secure connection without exposing your database to the public internet.

Also, the sections below provide a clear overview of how a connection is established within the VPC environment.

• Create a VPC (Virtual Private Cloud): A VPC is your own isolated network within IBM Cloud® where you can securely run resources.
• Generate an SSH key: SSH keys allow you to securely connect to your virtual servers.
• Provision a Virtual Server Instance (VSI): A VSI is your cloud-based server where applications and workloads will run.
• Reserve a floating IP for your VSI: A floating IP is a public IP address that lets you access your VSI from the internet.
• Create a Virtual Private Endpoint (VPE): A VPE provides secure, private connectivity to IBM Cloud services.

psql --version

psql (PostgreSQL) 17.x

terraform output -raw pg_manager_psql

psql 'postgresql://ibmcloud_user:lXcjb8q-2)ItFOq7l5)KtLgj%PmhFN,)@host:5432/postgres?sslmode=verify-full'

postgres=>

terraform output -raw pg_manager_username
terraform output -raw pg_manager_password
terraform output -raw hostname
terraform output -raw port

terraform destroy

Step 4: Connect IBM Cloud Monitoring through the console

You can use IBM Cloud Monitoring to get operational visibility into the performance and health of your applications, services, and platforms. IBM Cloud Monitoring provides administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

For more information about how to use Monitoring with Databases for PostgreSQL, see Monitoring integration.

You cannot connect IBM Cloud Monitoring by using the CLI. Use the console to complete this task. For more information, see Monitoring integration.

Step 4: Connect IBM Cloud Monitoring through the CLI

You can use IBM Cloud Monitoring to get operational visibility into the performance and health of your applications, services, and platforms. IBM Cloud Monitoring provides administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

For more information about how to use Monitoring with Databases for PostgreSQL, see Monitoring integration.

You cannot connect IBM Cloud Monitoring by using the CLI. Use the console to complete this task. For more information, see Monitoring integration.

Step 4: Connect IBM Cloud Monitoring through the API

You can use IBM Cloud Monitoring to get operational visibility into the performance and health of your applications, services, and platforms. IBM Cloud Monitoring provides administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

For more information about how to use Monitoring with Databases for PostgreSQL, see Monitoring integration.

You cannot connect IBM Cloud Monitoring by using the CLI. Use the console to complete this task. For more information, see Monitoring integration.

Step 4: Connect IBM Cloud Monitoring through Terraform

You can use IBM Cloud Monitoring to get operational visibility into the performance and health of your applications, services, and platforms. IBM Cloud Monitoring provides administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

For more information about how to use Monitoring with Databases for PostgreSQL, see Monitoring integration.

You cannot connect IBM Cloud Monitoring by using the CLI. Use the console to complete this task. For more information, see Monitoring integration.

Step 5: Connect IBM Cloud Activity Tracker Event Routing

IBM Cloud® Activity Tracker Event Routing allows you to view, and audit service activity to comply with corporate policies and industry regulations. Activity Tracker Event Routing records user-initiated activities that change the state of a service in IBM Cloud. Use Activity Tracker Event Routing to track how users and applications interact with the Databases for PostgreSQL service.

To get up and running with IBM Cloud Activity Tracker Event Routing, see Getting started with IBM Cloud Activity Tracker Event Routing.

Activity Tracker Event Routing can have only one instance per location. To view events, you must access the web UI of the Activity Tracker Event Routing service in the same location where your service instance is available. For more information, see Launch the web UI.

For more information about events specific to Databases for PostgreSQL, see Activity Tracker Event Routing events.

Events are formatted according to the Cloud Auditing Data Federation (CADF) standard. For further details of the information they include, see CADF standard.

You cannot connect Activity Tracker Event Routing by using the CLI. Use the console to complete this task. For more information, see Activity tracking events.

Step 5: Connect IBM Cloud Activity Tracker Event Routing through the CLI

IBM Cloud® Activity Tracker Event Routing allows you to view, and audit service activity to comply with corporate policies and industry regulations. Activity Tracker Event Routing records user-initiated activities that change the state of a service in IBM Cloud. Use Activity Tracker Event Routing to track how users and applications interact with the Databases for PostgreSQL service.

To get up and running with IBM Cloud Activity Tracker Event Routing, see Getting started with IBM Cloud Activity Tracker Event Routing.

Activity Tracker Event Routing can have only one instance per location. To view events, you must access the web UI of the Activity Tracker Event Routing service in the same location where your service instance is available. For more information, see Launch the web UI.

For more information about events specific to Databases for PostgreSQL, see Activity Tracker Event Routing events.

Events are formatted according to the Cloud Auditing Data Federation (CADF) standard. For further details of the information they include, see CADF standard.

You cannot connect Activity Tracker Event Routing by using the CLI. Use the console to complete this task. For more information, see Activity tracking events.

Step 5: Connect IBM Cloud® Activity Tracker Event Routing through the API

IBM Cloud® Activity Tracker Event Routing allows you to view, and audit service activity to comply with corporate policies and industry regulations. Activity Tracker Event Routing records user-initiated activities that change the state of a service in IBM Cloud. Use Activity Tracker Event Routing to track how users and applications interact with the Databases for PostgreSQL service.

To get up and running with IBM Cloud Activity Tracker Event Routing, see Getting started with IBM Cloud Activity Tracker Event Routing.

Activity Tracker Event Routing can have only one instance per location. To view events, you must access the web UI of the Activity Tracker Event Routing service in the same location where your service instance is available. For more information, see Launch the web UI.

For more information about events specific to Databases for PostgreSQL, see Activity Tracker Event Routing events.

Events are formatted according to the Cloud Auditing Data Federation (CADF) standard. For further details of the information they include, see CADF standard.

You cannot connect Activity Tracker Event Routing by using the CLI. Use the console to complete this task. For more information, see Activity tracking events.

Step 5: Connect IBM Cloud Activity Tracker Event Routing through Terraform

IBM Cloud® Activity Tracker Event Routing allows you to view, and audit service activity to comply with corporate policies and industry regulations. Activity Tracker Event Routing records user-initiated activities that change the state of a service in IBM Cloud. Use Activity Tracker Event Routing to track how users and applications interact with the Databases for PostgreSQL service.

To get up and running with IBM Cloud Activity Tracker Event Routing, see Getting started with IBM Cloud Activity Tracker Event Routing.

Activity Tracker Event Routing can have only one instance per location. To view events, you must access the web UI of the Activity Tracker Event Routing service in the same location where your service instance is available. For more information, see Launch the web UI.

For more information about events specific to Databases for PostgreSQL, see Activity Tracker Event Routing events.

Events are formatted according to the Cloud Auditing Data Federation (CADF) standard. For further details of the information they include, see CADF standard.

You cannot connect Activity Tracker Event Routing by using the CLI. Use the console to complete this task. For more information, see Activity tracking events.