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
DocumentationTDSQL-C for MySQLPractical TutorialHow to Authorize Sub-Users to View Monitoring Data

How to Authorize Sub-Users to View Monitoring Data

PDF
Focus Mode
Font Size
Last updated: 2024-06-07 14:23:46

Operation Scenarios

By default, the root account is the owner of the resources and has access permissions to all its resources. Sub-users do not have access permissions to any resources by default and require the root account to grant them the relevant access permissions. Only then can a sub-user normally access the relevant resources. Therefore, for a sub-user to be able to log in and access the monitoring and alarm features of the TDSQL-C for MySQL cluster, the root account must first authorize the sub-user.
When an unauthorized sub-user account is used to log in to the console, you cannot query instance monitoring information, or access TCOP and set alarms.

Prerequisites

To authorize a sub-user, you need to log in to the CAM console with the root account. Contact the root account holder in advance to assist with the authorization operation.

Directions

1. Log in to the CAM console with the root account.
2. In the left navigation pane, choose Users > User List.
3. In the user list, find the target sub-user, and click Authorize in the Operation column.

4. In the pop-up window, find and select the relevant policies (see table below), and click OK.

Policy Name
Description
QcloudCynosDBFullAccess
For full read-write access to TDSQL-C for CynosDB, the authorized sub-user can view the TDSQL-C for MySQL clusters under the root account and has full read-write access to the clusters.
QcloudCynosDBReadOnlyAccess
For read-only access to TDSQL-C for CynosDB, the authorized sub-user can view the TDSQL-C for MySQL clusters under the root account and has read-only access to the clusters.
QcloudMonitorFullAccess
Full read-write access to TCOP (Monitor), including the permission to view user groups.
QcloudMonitorReadOnlyAccess
Read-only access to TCOP (Monitor).
5. After authorization, the sub-user can log in to the TDSQL-C for MySQL console to view monitoring information and set alarms for the relevant clusters.


Previous Topic: Solution to High CPU UtilizationNext Topic: Overview

Help and Support

Was this page helpful?

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

Feedback