Vultr Customer Portal

1. Navigate to Products and select Databases.
2. Click the target database instance.
3. Navigate to Settings and click Change Plan.
4. Review the active plan, select a new plan, set replica nodes, and click Save.

Vultr API

1. List all the database instances by sending a GET request to the List Managed Databases endpoint and note the database ID. For example, 43b4c774-5dff-4ac0-a01f-78a23c2205b5.
   console

   $ curl "https://api.vultr.com/v2/databases" \
       -X GET \
       -H "Authorization: Bearer ${VULTR_API_KEY}"
   

2. Send a PUT request to the Update Managed Database endpoint to change the database plan and specify the database ID and the new plan (For instance, vultr-dbaas-business-cc-1-55-2).
   console

   $ curl "https://api.vultr.com/v2/databases/database_id" \
       -X PUT \
       -H "Authorization: Bearer ${VULTR_API_KEY}" \
       -H "Content-Type: application/json" \
       --data '{
           "plan" : "vultr-dbaas-startup-cc-1-55-2"     
       }'
   

   Visit the Update Managed Database endpoint to view additional attributes to add to your request.

Vultr CLI

1. List all database instances and note the database ID. For instance, d6ac2a3c-92ea-43ef-8185-71a23e58ad8c.
   console

   $ vultr-cli database list --summarize
   

2. Update the database plan by specifying a database ID and a new plan (For instance, vultr-dbaas-business-cc-1-55-2).
   console

   $ vultr-cli database update database_id \
   --plan vultr-dbaas-business-cc-1-55-2
   

   Run vultr-cli database update --help to view all options.

Terraform

1. Open your Terraform configuration and locate the Managed Database for MySQL resource.
2. Update the plan argument with the new database plan ID.
   terraform

   resource "vultr_database" "mysql" {
       label                   = "mysql-cluster-1"
       database_engine         = "mysql"
       database_engine_version = "8"
       region                  = "ewr"
       plan                    = "vultr-dbaas-business-cc-1-55-2" # Updated plan
   }
   

3. Apply the configuration and observe the following output:

   Apply complete! Resources: 0 added, 1 changed, 0 destroyed.