Vultr DocsLatest Content

How to Manage Tags on a Vultr Cloud GPU Instance

Updated on 28 August, 2025

Tagging enables the assignment of specific labels called tags on an instance for identification in your Vultr account. Tags consist of multiple characters that help identify, organize, and manage instances in your Vultr account.

Follow this guide to manage tags on a Vultr Cloud GPU instance using the Vultr Customer Portal, API, CLI, or Terraform.

  • Vultr Customer Portal
  • Vultr API
  • Vultr CLI
  • Terraform
  1. Navigate to Products and click Compute.
  2. Click your target Cloud GPU instance to open its management page.
  3. Navigate to the Tags tab.
  4. Enter a new tag in the Add Tag field and click Add to apply the new tag.
  5. Find and click Delete within the Existing Tags section to remove a specific tag on your instance.

  1. Send a GET request to the List Instances endpoint and note the target instance's ID.

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

  2. Send a PATCH request to the Update Instance endpoint to add new tags to the instance.

    console 
    $ curl "https://api.vultr.com/v2/instances/{instance-id}" \
  -X PATCH \
  -H "Authorization: Bearer ${VULTR_API_KEY}" \
  -H "Content-Type: application/json" \
  --data '{
    "tags" : ["tag1", "tag2"]
  }'

  1. List all instances in your Vultr account and note the target instance's ID.

    console 
    $ vultr-cli instance list

  2. Add new tags to the instance.

    console 
    $ vultr-cli instance tags <instance_id> --tags <tag1,tag2>

  1. Open your Terraform configuration for the existing Cloud GPU instance.

  2. Update the tags value in the instance resource to include the desired tags.

    terraform 
    resource "vultr_instance" "gpu" {
    # ...existing fields (region, plan, label, etc.)

    tags = ["tag1", "tag2"]
}

  3. Apply the configuration and observe the following output:

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

Comments

No comments yet.