Resource-level Permissions Supported

Overview

Strengths

Use Cases

Sharding

Read/Write Separation

Elastic Expansion

Strong Sync

Basic Principles

Instance Architecture

Regions and AZs

Product Introduction

Billing Overview (InnoDB)

Product Pricing (InnoDB)

Purchase and Upgrade

Refund

Payment Overdue

Backup Space Billing

Purchase Guide

Creating Instance

Connecting to Instance

Managing Sharded Table

InnoDB Engine

Getting Started

Renaming Database Instance

Specifying Project for Instance

Isolating/Restoring/Terminating Instances

Adjusting Deployed Node

Changing Instance Specification

Restarting Instance

Instance Management

Disaster Recovery Read-Only Instance

Changing Networks

Creating Account

Modifying Account Permissions

Cloning Account

Configuring Read/Write Separation

Resetting Account Password

Deleting Account

Account Management

Access Management

Security Group Configuration

Transparent Data Encryption (TDE)

Security Management

Slow Query Analysis

Backup Mode

Downloading Backup File

Backup Encryption

Rolling Back Database

Backup and Rollback

Data Migration

Enabling Database Audit

Viewing Audit Logs

Modifying Log Retention Period

Database Audit

Operation Guide（InnoDB）

Import from Standalone Instance to TDSQL Instance

Import Between TDSQL Instances

Selection of TDSQL Instance and Shard Configuration

Practical Tutorial

Platform Security Design

Tenant Security Features

Security White Paper

Use Limits

Compatibility

Connecting Database

Join and Subquery

Sequence

Frequently Used DML Statements

Distributed Transaction

Creating Table

Connection Protection

Globally Unique Field

Exporting/Importing Data

Database Management Statements

Passthrough SQL

Preprocessing

Subpartitioning

Error Codes and Messages

InnoDB

Development Guide

History

Introduction

API Category

AssociateSecurityGroups

DescribeDBSecurityGroups

DescribeProjectSecurityGroups

DisassociateSecurityGroups

ModifyDBInstanceSecurityGroups

Security Group APIs

DescribeBackupFiles

DescribeDBEncryptAttributes

KillSession

ModifyAccountPrivileges

ModifyInstanceNetwork

ModifyDBEncryptAttributes

CreateOnlineDDLJob

Other APIs

Request Structure

Common Params

Signature v3

Signature

Responses

Making API Requests

ActiveHourDCDBInstance

CancelDcnJob

CloneAccount

CloseDBExtranetAccess

CopyAccountPrivileges

CreateAccount

CreateDedicatedClusterDCDBInstance

DeleteAccount

DescribeAccountPrivileges

DescribeAccounts

DescribeDBLogFiles

DescribeDBParameters

DescribeDBSlowLogs

DescribeDBSyncMode

DescribeDBTmpInstances

DescribeDCDBInstanceNodeInfo

DescribeDCDBInstances

DescribeDCDBPrice

DescribeDCDBShards

DescribeDatabaseObjects

DescribeDatabaseTable

DescribeDatabases

DescribeDcnDetail

DescribeFileDownloadUrl

DescribeFlow

DescribeLogFileRetentionPeriod

DescribeOrders

DestroyDCDBInstance

DestroyHourDCDBInstance

GrantAccountPrivileges

InitDCDBInstances

IsolateDedicatedDBInstance

IsolateHourDCDBInstance

ModifyAccountDescription

ModifyDBInstanceName

ModifyDBInstancesProject

ModifyDBParameters

ModifyDBSyncMode

ModifyInstanceVip

ModifyInstanceVport

ResetAccountPassword

SwitchDBInstanceHA

TerminateDedicatedDBInstance

UpgradeDedicatedDCDBInstance

UpgradeHourDCDBInstance

CreateDCDBInstance

CreateHourDCDBInstance

DescribeDCDBInstanceDetail

ModifyAccountConfig

OpenDBExtranetAccess

IsolateDCDBInstance

TDSQL APIs

Data Types

Error Codes

API Documentation

General

Disk Overuse

IO Metric Exception

FAQs

Performance Comparison Data for Strong Sync

General References

Glossary

Alarm Upgrade

Announcements

Contact Us

TDSQL for MySQL

Resource-level permission can be used to specify which resources a user can manipulate. TencentDB supports certain resource-level permission. This means that for some TencentDB operations, you can control the time when a user is allowed to perform operations (based on mandatory conditions) or to use specified resources. The following table describes the types of resources that can be authorized in TencentDB.

Types of resources that can be authorized in CAM:

The table below lists the TencentDB API operations which currently support resource-level permission control as well as the resources and condition keys supported by each operation. When specifying a resource path, you can use the "*" wildcard in the path.

Any TencentDB API operation not listed here does not support resource-level permission. If a TencentDB API operation does not support resource-level permission, you can still authorize a user to perform this operation, but you must specify * for the resource element of the policy statement.

The following operations support resource-level permission control

tencent cloud