Adding disk, memory, and CPU

Review current resources and hosting model

In the Resources tab, you find both Hosting model and Resource allocations tiles. These tiles reflect your current resources and hosting model. Select Configure to adjust the settings in each tile.

Scaling in the UI

In the Resources tab of the UI, select Configure on the Resource allocations tile. This opens up a panel where you can adjust your resources.

Look for a "Host sizes" table, where you can select the vCPU and RAM configuration per member for your database.

The "Disk (GB/member)" slider is your disk selection per member. Drag the slider or adjust the number in the input box to change the number of GB disk. Note that disk is tied to IOPS at 1 GB = 5 IOPS.

Members is the number of members of your database. For PostgreSQL, members are set to 2.

Review your total estimated cost in the calculator on the bottom. Note that if you have grandfathered costs, also known as legacy pricing structure, scaling your database instance removes some or all of your legacy pricing. For more information on grandfathering and when it ends, see Gradfathering transition timeline.

After you are done, click Apply changes to trigger the scaling operation.

Review current resources and hosting model

To interact with Cloud Databases on Gen 2 via the CLI you must utilize the IBM Cloud Resource Controller's CLI. For more information, see the General IBM Cloud CLI (ibmcloud) commands. To get information about a particular instance, use the following command:

ibmcloud resource service-instance <INSTANCE_NAME> -o JSON

Resources and scaling in the CLI

To update your instance (this includes operations, such as scaling and modifying other parts of your service), use the ibmcloud resource service-instance-update command.

ibmcloud resource service-instance-update <INSTANCE_NAME> -p '<{FIELDS_TO_UPDATE}>'

For example, to update the host_flavor of a Databases for PostgreSQL instance, use a command like:

ibmcloud resource service-instance-update test-database databases-for-postgresql standard us-south -p '{"host_flavor": "mx3d.8x80.encrypted", "storage_gb": 10 }'

Review current resources and hosting model

The Foundation endpoint that is shown on the Overview panel of your service provides the base URL to access this deployment through the API. Use it with the /groups endpoint if you need to manage or automate scaling programmatically.

To view the current and scalable resources on a deployment, use the /deployments/{id}/groups endpoint.

curl -X GET https://api.{region}.databases.cloud.ibm.com/v5/ibm/deployments/{id}/groups -H 'Authorization: Bearer <>' \

To view the current and scalable resources on a deployment, use the /deployments/{id}/groups endpoint. Note that this command will also reveal if your database is a Shared Compute or Isolated Compute instance through the host_flavor attribute. If the host_flavor is null, it is on an old style hosting model.

curl -X GET -H "Authorization: Bearer $APIKEY" 'https://api.{region}.databases.cloud.ibm.com/v5/ibm/deployments/{id}/groups'

Scaling with the API

To scale the host_flavor of a deployment to mx3d.8x80.encrypted for each memory member, use the following command:

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": "ca-mon",
    "resource_group": "5c49eabc-f5e8-5881-a37e-2d100a33b3df",
    "resource_plan_id": "databases-for-postgresql-standard",
    "dataservices": {
      "resources": {
        "database": {
          "host_flavor": "mx3d.8x80.encrypted"
        }
      }
     }
   }'

For more information, see the API reference.

Review current resources and hosting model

Review resource allocations to your database by checking your Terraform scripts for cpu { allocation_count = }, memory {allocation_mb = }, and disk { allocation_mb = }.

Scaling with Terraform

Before executing a Terraform script on an existing instance, use the terraform plan command to compare the current infrastructure state with the desired state defined in your Terraform files. Any alteration to the resource_group_id, service plan, version, key_protect_instance, key_protect_key, backup_encryption_key_crn attributes recreates your instance. For a list of current argument references with the Forces new resource specification, see the ibm_database Terraform Registry.

Scale your instance by adjusting your Terraform script for the resource you're interested in. In the following example, host_flavor and disk allocations are specified.

To implement your change, run terraform apply.

data "ibm_resource_group" "default" {
  name = "Default"
}
resource "ibm_resource_instance" "pg_demo" {
  name              = "pg-demo"
  service           = "databases-for-postgresql"
  plan              = "standard-gen2"
  location          = "ca-mon"
  resource_group_id = data.ibm_resource_group.default.id
  parameters_json = jsonencode(
    {
      "dataservices": {
        "postgresql": {
          "storage_gb": 9600,
          "members": 3,
          "host_flavor":  "bx3d.8x40"
        }
      }
    }
  )

Switching to and Scaling Hosting Models in Terraform

Select the hosting model you want your database to be scaled to. You can change this later.

Update the host_flavor value in the parameters_json section from the example above with the intended value, then run terraform apply.