tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Binding and Unbinding Resource Pack

PDF
Focus Mode
Font Size
Last updated: 2026-01-29 17:47:35
If you want to use a resource pack, you need to bind the resource pack after purchasing it. You can also unbind a resource pack that has been bound to clusters. This document describes how to bind or unbind a resource pack.
Note:
A resource package can be bound to multiple clusters.
Each cluster can be bound to up to 10 computing resource packages and 10 storage resource packages.
Storage resource packages can only be bound to Serverless clusters.
Computing resource packages can be bound to Serverless clusters or provisioned resource clusters with Serverless enabled (that is, the cluster contains Serverless read-only instances).

Prerequisites

You have created a serverless cluster. For more information, see Creating Serverless Cluster.
You have purchased a resource pack. For more information, see Purchasing Resource Pack.

Binding a resource pack

Scenario 1: Binding a resource pack when creating a serverless cluster

1. Log in to the purchase page.
2. Set the instance mode to Serverless. In the Instance Selection and Storage sections, select and bind a resource pack. For details about the complete creation steps, see Creating a Serverless Cluster.

Scenario 2: Binding Resource Packages to Existing Clusters

Binding Existing Clusters from the Resource Package List

After purchasing a resource package, you can bind it to an existing cluster from the resource package list.
1. Log in to the TDSQL-C for MySQL console.
2. On the left sidebar, click Resource Pack to enter the resource pack management page.
3. Find the target resource pack directly on the page or quickly filter it out in the search box on the right, and click Bind/Unbind in the Operation column.

4. In the pop-up window, select a region, and then select clusters to bind the resource packages to (multiple selections are supported). Click OK.


Binding Resource Packages to Existing Clusters from the Cluster Management Page

1. Log in to the TDSQL-C for MySQL console.
2. Click the target cluster in the cluster list on the left to enter the cluster management page.
3. On the cluster management page, select Resource Pack and click Bind Now.

4. In the pop-up window, select the required resource packs. Multiple selections are supported. Click OK.


Unbinding a resource pack

When a resource pack expires or is used up, the resource pack will be automatically unbound. You can also unbind it manually.

Unbinding Existing Clusters from the Resource Package List

1. Log in to the TDSQL-C for MySQL console.
2. On the left sidebar, click Resource Pack to enter the resource pack management page.
3. Find the target resource pack directly on the page or quickly filter it out in the search box on the right, and click Bind/Unbind in the Operation column.
4. In the pop-up window, select a region, and then delete the bound clusters on the right. Click OK.

Unbinding Resource Packages from Existing Clusters from the Cluster Management Page

1. Log in to the TDSQL-C for MySQL console.
2. Click the target cluster in the cluster list on the left to enter the cluster management page.
3. On the cluster management page, select Resource Pack.
4. Find the target resource pack, and click Unbind in the Operation column.

5. In the pop-up window, click OK.

Related APIs

API
Description
This API (BindClusterResourcePackages) is used to bind resource pack to cluster.
This API (UnbindClusterResourcePackages) is used to unbind resource pack from cluster.
This API (ModifyResourcePackageClusters) is used to modify the binding relationship between resource pack and cluster.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback