Tencent Cloud Resource Management & Operations Tool

The Common Pitfalls of Managing Tencent Cloud Resources

Teams operating on Tencent Cloud frequently encounter several concrete problems:

• Outdated Information and Parameter Confusion: Pre-trained knowledge of APIs may be obsolete. For instance, required parameters for tccli, supported region lists, or product-specific limits can change. Relying on outdated information leads to command failures.
• Operational Risk and Lack of Process: Managing cloud resources, such as terminating instances or modifying security groups, is high-risk. Without a clear confirmation mechanism, it can cause irreversible downtime or data loss.
• Fragmented Multi-Product Operations: Managing products like Lighthouse, CVM, CBS, and DNSPod simultaneously often requires switching between multiple consoles or documentation sources, making workflows cumbersome.

How the Skill Works: A Standardized Process Centered on tccli

This skill aims to standardize the resolution of these issues. Its core operation is to establish the tccli command-line tool as the sole, authoritative source for both information and action. Key capabilities and steps include:

1. Unified Retrieval and Verification: All queries regarding Tencent Cloud API parameters or product limits prioritize executing tccli <product> <action> --help to get the latest documentation. The skill integrates reference sources (like the API Documentation), but stipulates a critical rule: if a discrepancy exists between the documentation and the --help output, the --help output takes precedence. This ensures operational commands are immediately accurate.

2. Comprehensive and Secure Product Operations: The skill provides capabilities to query and manage resources across several core Tencent Cloud products, including Lighthouse (full operations), CVM, CBS, VPC, DNSPod, SSL, CAM, Monitor, and TAT. Key actions are executed through standard tccli commands, for example:

   • tccli lighthouse DescribeInstances --region ap-beijing (Query Lighthouse instances)
   • tccli cbs DescribeDisks (List cloud disks)
   • tccli ssl DescribeCertificates (View SSL certificates)

3. Security and Authentication Management: It strongly recommends using OAuth browser-based login authorization (via the tccli-oauth-helper.py script) to obtain temporary credentials valid for 2 hours, which is a high-security practice. The skill strictly prohibits manually constructing OAuth authorization URLs; they must be generated via the provided script. Furthermore, it implements a double-confirmation process for high-risk operations (e.g., deletion), explicitly stating the irreversible consequences.

Scope of Applicability and Key Considerations

This skill focuses on cloud-based resource operations and management, with clearly defined boundaries:

• Core Boundary: It deals with resources already deployed on Tencent Cloud. Local environment development, code writing, and CI/CD pipelines are outside its scope.
• Authoritative Source: tccli is the cornerstone. Whether obtaining the current instance ID (using scripts/whoami.sh), verifying credential status, or executing any operation, one should rely on tccli or its auxiliary scripts.
• Product Isolation: Lighthouse and CVM are distinct products. Using commands interchangeably (e.g., using tccli cvm to manage Lighthouse) is strictly forbidden.
• Credential Security: Avoid using permanent AK/SK keys unless in special, controlled scenarios. When exiting a session, use tccli auth logout to clear local credentials.

By adhering to these tccli-centric standards, one can effectively mitigate the risks of information lag and operational errors in Tencent Cloud resource management, enabling more reliable and secure operations.