Manage Resource Tags and Labels

Tags (for AWS and Azure) and labels (for GCP) are Key = Value metadata attached to cloud resources (such as compute instances, storage volumes, and load balancers) PhoenixAI provisioned for you. Once applied, they are synchronized to the underlying cloud provider, enabling you to identify, categorize, filter, search, and allocate costs for resources within the cloud provider console.

Terminology Across Cloud Providers

AWS and Azure refer to this feature as Tags, while Google Cloud uses the term Labels. This document uses the unified term Tags, while the product UI reflects the terminology of the respective cloud provider.

Add resource tags

You can add resource tags on the cluster and the warehouse level.

Add tags to a cluster

You can add tags to an existing cluster or a new cluster while creating it.

Follow these steps to add tags to an existing cluster:

1. Sign in to the PhoenixAI Cloud console.

2. On the Clusters page, click the cluster that you want to add tags to.

3. On the Cluster parameters tab of the cluster details page, click Edit in the AWS Tags, Azure Tags, or GCP Labels section.

   • To add a new tag/label to the cluster, click Add tag/label, and enter the Tag/Label Key and Value.
   • To modify a tag/label of the cluster, click the edit button, enter the new Tag/Label Key or Value, and click the save button.
   • To delete a tag/label of the cluster, click the delete button.
   note

   The automatically added tags Vendor, Creator, and ClusterName cannot be modified or deleted.

4. Click Apply to submit the changes.

Add tags to a warehouse

You can add tags to an existing warehouse or a new warehouse while creating it.

Follow these steps to add tags to an existing warehouse:

1. Sign in to the PhoenixAI Cloud console.

2. On the Clusters page, click the cluster to which the warehouse belong.

3. On the Warehouses tab of the cluster details page, click the warehouse that you want to add tags to.

4. On the Warehouse parameters tab of the warehouse details page, click Edit in the AWS Tags, Azure Tags, or GCP Labels section.

   • To add a new tag/label to the cluster, click Add tag/label, and enter the Tag/Label Key and Value.
   • To modify a tag/label of the cluster, click the edit button, enter the new Tag/Label Key or Value, and click the save button.
   • To delete a tag/label of the cluster, click the delete button.
   note

   The automatically added tags Vendor, Creator, ClusterName, and WarehouseName cannot be modified or deleted.

5. Click Apply to submit the changes.

Mechanism

Tag hierarchy

Tags are defined at two hierarchical levels, along with a set of system-managed tags.

Cluster tags

Cluster tags apply to FE nodes and all shared infrastructure within a cluster, including compute instances, storage volumes, load balancers, placement groups, and target groups.

Warehouse tags

Warehouse tags apply to BE nodes and dedicated resources associated with a specific Warehouse.

If a Warehouse tag uses the same key as a cluster tag, the Warehouse tag overrides the cluster tag. See Tag Merging Behavior for details.

Automatically added tags

The system automatically assigns a fixed set of tags to each resource for identification and management purposes. These tags are read-only and cannot be modified or deleted.

These tags include:

Tag	Description
Vendor	Always set to PhoenixAI
Creator	The PhoenixAI Cloud account that created the resource
ClusterName / ClusterID	Identifies the associated cluster
WarehouseName	Identifies the associated Warehouse (Warehouse resources only)
CelerdataManaged	Indicates that the resource is managed by PhoenixAI

Additional internal tags (such as workflow and account identifiers) may also be applied.

On Google Cloud, tag keys are automatically normalized to lowercase hyphenated format (for example, ClusterID becomes cluster-id) to comply with labeling requirements.

Tag merging behavior

The tag view displays effective tags, which represent the final set of tags applied to resources after merging cluster-level and Warehouse-level tags:

Effective Tags = Cluster Tags + Warehouse Tags
                 (Warehouse values override on key conflict)

• Keys defined at only one level are applied as-is.
• When both levels define the same key, the Warehouse value overrides the cluster value for resources in that Warehouse.

In the PhoenixAI Cloud Console, overridden tags are marked with an override icon (↻). Hovering over the icon reveals the original cluster value.

When adding a Warehouse tag with a key that already exists at the cluster level, the Warehouse value takes precedence for that Warehouse’s resources.

If a Warehouse tag that overrides a cluster tag is deleted, the key does not disappear. Instead, it reverts to the inherited cluster value.

When cluster tags are modified, the system reconciles all Warehouses automatically:

• If a cluster tag is added or updated with a key that also exists in a Warehouse, the cluster value takes precedence, and the Warehouse no longer overrides that key.
• If a cluster tag is removed while a Warehouse still defines the same key, the Warehouse retains its own value.

Rules and limits

Tag constraints vary by cloud provider.

Tag Count limits

System-managed tags count toward the limits below.

Scope	Maximum Number of Tags
Cluster	30
Warehouse	10

Key constraints

Cloud Provider	Length	Constraints
AWS	1–128 characters	Must not start with aws:; allows letters, digits, and _ . : / = + - @
Azure	1–128 characters	Must not contain < > % & \ ? /; must not start with azure, microsoft, or windows
Google Cloud	2–63 characters	Must start with a lowercase letter; only lowercase letters, digits, _, and - are allowed

Value constraints

Cloud Provider	Length	Constraints
AWS	0–256 characters	Allows letters, digits, spaces, and _ . : / = + - @
Azure	0–256 characters	Must not contain < > % & \ ?
Google Cloud	0–63 characters	Only lowercase letters, digits, _, and - are allowed

Additional rules

• Keys must be unique within the same scope.
• Tag keys must not conflict with system-reserved keys such as Vendor, Creator, ClusterName, or WarehouseName.