- Release Notes and Announcements
- Release Notes
- Announcements
- Commercial Billing for Database Proxy
- TencentDB for MySQL Audit Upgrade
- Added Authentication APIs
- API Authentication Upgrade
- TencentDB for MySQL API 2.0 Discontinuation
- Monitoring Module Upgrade in Shanghai Region
- Monitoring Metric Optimization
- Network Architecture Upgrade
- Change of APIs for Querying the Specifications of Purchasable Database Instances
- Replacement of Certain Old Database Proxy APIs
- Added Advanced Monitoring Metrics
- Change of Calculation Formula for Memory Utilization
- Monitoring Module Upgrade and Optimization in Guangzhou and Shanghai Regions
- Monitoring Module Upgrade
- Parameter Template and Instance Purchase Process Optimization
- Binlog Will Take up Disk Space
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Stability Features
- TXRocks Engine
- Purchase Guide
- Getting Started
- Database Audit
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data Migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Best Practices
- Usage Specifications of TencentDB for MySQL
- Configuring Automatic Application Reconnection
- Impact of Modifying MySQL Source Instance Parameters
- Limits on Automatic Conversion from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Setting up 2-Region-3-DC Disaster Recovery Architecture
- Improving TencentDB for MySQL Performance with Read/Write Separation
- Migrating Data from InnoDB to RocksDB with DTS
- Building LAMP Stack for Web Application
- Building Drupal Website
- Building All-Scenario High-Availability Architecture
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- StopCpuExpand
- StartCpuExpand
- DescribeCpuExpandStrategy
- AddTimeWindow
- BalanceRoGroupLoad
- CloseWanService
- CreateDBInstance
- CreateDBInstanceHour
- CreateRoInstanceIp
- DeleteTimeWindow
- DescribeCdbZoneConfig
- DescribeDBFeatures
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDBInstanceGTID
- DescribeDBInstanceInfo
- DescribeDBInstanceRebootTime
- DescribeDBSwitchRecords
- DescribeRoGroups
- DescribeRoMinScale
- DescribeTagsOfInstanceIds
- DescribeTimeWindow
- InitDBInstances
- IsolateDBInstance
- ModifyAutoRenewFlag
- ModifyDBInstanceName
- ModifyDBInstanceProject
- ModifyDBInstanceVipVport
- ModifyInstanceTag
- ModifyRoGroupInfo
- ModifyTimeWindow
- OfflineIsolatedInstances
- OpenDBInstanceEncryption
- OpenDBInstanceGTID
- OpenWanService
- ReleaseIsolatedDBInstances
- RenewDBInstance
- RestartDBInstances
- StartReplication
- StopReplication
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- SwitchForUpgrade
- UpgradeDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- DescribeDBZoneConfig
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Data Import APIs
- Database Proxy APIs
- AdjustCdbProxy
- AdjustCdbProxyAddress
- CloseCdbProxyAddress
- CreateCdbProxy
- CreateCdbProxyAddress
- DescribeCdbProxyInfo
- DescribeProxySupportParam
- ModifyCdbProxyAddressDesc
- ModifyCdbProxyAddressVipAndVPort
- ModifyCdbProxyParam
- CloseCDBProxy
- DescribeProxyCustomConf
- ReloadBalanceProxyNode
- SwitchCDBProxy
- UpgradeCDBProxyVersion
- Database Audit APIs
- Security APIs
- Task APIs
- Account APIs
- Backup APIs
- DescribeBackupDecryptionKey
- CreateBackup
- DeleteBackup
- DescribeBackupDownloadRestriction
- DescribeBackupEncryptionStatus
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBinlogBackupOverview
- DescribeDataBackupOverview
- DescribeLocalBinlogConfig
- DescribeRemoteBackupConfig
- DescribeSlowLogs
- ModifyBackupDownloadRestriction
- ModifyBackupEncryptionStatus
- ModifyLocalBinlogConfig
- ModifyRemoteBackupConfig
- DescribeBackups
- DescribeBackupConfig
- ModifyBackupConfig
- DescribeBinlogs
- Rollback APIs
- Parameter APIs
- Database APIs
- Monitoring APIs
- Log-related API
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Preset Plugin List
- Release Notes and Announcements
- Release Notes
- Announcements
- Commercial Billing for Database Proxy
- TencentDB for MySQL Audit Upgrade
- Added Authentication APIs
- API Authentication Upgrade
- TencentDB for MySQL API 2.0 Discontinuation
- Monitoring Module Upgrade in Shanghai Region
- Monitoring Metric Optimization
- Network Architecture Upgrade
- Change of APIs for Querying the Specifications of Purchasable Database Instances
- Replacement of Certain Old Database Proxy APIs
- Added Advanced Monitoring Metrics
- Change of Calculation Formula for Memory Utilization
- Monitoring Module Upgrade and Optimization in Guangzhou and Shanghai Regions
- Monitoring Module Upgrade
- Parameter Template and Instance Purchase Process Optimization
- Binlog Will Take up Disk Space
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Stability Features
- TXRocks Engine
- Purchase Guide
- Getting Started
- Database Audit
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data Migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Best Practices
- Usage Specifications of TencentDB for MySQL
- Configuring Automatic Application Reconnection
- Impact of Modifying MySQL Source Instance Parameters
- Limits on Automatic Conversion from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Setting up 2-Region-3-DC Disaster Recovery Architecture
- Improving TencentDB for MySQL Performance with Read/Write Separation
- Migrating Data from InnoDB to RocksDB with DTS
- Building LAMP Stack for Web Application
- Building Drupal Website
- Building All-Scenario High-Availability Architecture
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- StopCpuExpand
- StartCpuExpand
- DescribeCpuExpandStrategy
- AddTimeWindow
- BalanceRoGroupLoad
- CloseWanService
- CreateDBInstance
- CreateDBInstanceHour
- CreateRoInstanceIp
- DeleteTimeWindow
- DescribeCdbZoneConfig
- DescribeDBFeatures
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDBInstanceGTID
- DescribeDBInstanceInfo
- DescribeDBInstanceRebootTime
- DescribeDBSwitchRecords
- DescribeRoGroups
- DescribeRoMinScale
- DescribeTagsOfInstanceIds
- DescribeTimeWindow
- InitDBInstances
- IsolateDBInstance
- ModifyAutoRenewFlag
- ModifyDBInstanceName
- ModifyDBInstanceProject
- ModifyDBInstanceVipVport
- ModifyInstanceTag
- ModifyRoGroupInfo
- ModifyTimeWindow
- OfflineIsolatedInstances
- OpenDBInstanceEncryption
- OpenDBInstanceGTID
- OpenWanService
- ReleaseIsolatedDBInstances
- RenewDBInstance
- RestartDBInstances
- StartReplication
- StopReplication
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- SwitchForUpgrade
- UpgradeDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- DescribeDBZoneConfig
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Data Import APIs
- Database Proxy APIs
- AdjustCdbProxy
- AdjustCdbProxyAddress
- CloseCdbProxyAddress
- CreateCdbProxy
- CreateCdbProxyAddress
- DescribeCdbProxyInfo
- DescribeProxySupportParam
- ModifyCdbProxyAddressDesc
- ModifyCdbProxyAddressVipAndVPort
- ModifyCdbProxyParam
- CloseCDBProxy
- DescribeProxyCustomConf
- ReloadBalanceProxyNode
- SwitchCDBProxy
- UpgradeCDBProxyVersion
- Database Audit APIs
- Security APIs
- Task APIs
- Account APIs
- Backup APIs
- DescribeBackupDecryptionKey
- CreateBackup
- DeleteBackup
- DescribeBackupDownloadRestriction
- DescribeBackupEncryptionStatus
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBinlogBackupOverview
- DescribeDataBackupOverview
- DescribeLocalBinlogConfig
- DescribeRemoteBackupConfig
- DescribeSlowLogs
- ModifyBackupDownloadRestriction
- ModifyBackupEncryptionStatus
- ModifyLocalBinlogConfig
- ModifyRemoteBackupConfig
- DescribeBackups
- DescribeBackupConfig
- ModifyBackupConfig
- DescribeBinlogs
- Rollback APIs
- Parameter APIs
- Database APIs
- Monitoring APIs
- Log-related API
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Preset Plugin List
As required by the security requirements of Tencent Cloud, APIs that are directly accessed now require CAM authentication for access starting from March 31, 2023. To ensure that you can continue to use these APIs normally after the upgrade, go to the CAM console to grant the access permissions for them.
Note
- If you have already authorized, the authentication upgrade will have no impact on your business; otherwise, you should authorize first before calling APIs.
Effective Time
Friday, March 31, 2023.
APIs That Require CAM Authentication (46 in Total)
| API | Description | Authorization Granularity |
|---|---|---|
| DescribeSSLStatus | Queries whether SSL is enabled. If it is enabled, the download link for the certificate will be returned synchronously. | Operation-level |
| DescribeAuditPolicies | Queries the instance audit policy | Resource-level |
| DescribeDBPrice | Queries the price of a database instance | Resource-level |
| OpenAuditService | Enables the audit service | Operation-level |
| OpenSSL | Enables SSL connection | Resource-level |
| DescribeDBInstanceGTID | Queries whether GTID is enabled for the instance | Resource-level |
| DeleteAuditRule | Deletes the audit policy | Operation-level |
| CreateAuditRule | Creates an audit rule | Operation-level |
| CloseSSL | Disables SSL connection | Resource-level |
| ModifyAuditRule | Modifies the audit rule | Operation-level |
| DescribeDBFeatures | Queries database version attributes, including supported features such as database encryption and audit. | Resource-level |
| DescribeDBDiskInfo | Queries the disk information of the TencenDB physical machine | Resource-level |
| ModifyDBInstanceReadOnlyStatus | Sets TencenDB for MySQL instance to be read-only | Resource-level |
| OpenTransparentSlaveAccess | Enables the read-only access to the replica server | Resource-level |
| SwitchDrMasterRole | Performs a disaster recovery failback | Resource-level |
| DescribeDBInstanceProcess | Queries the instance active threads | Resource-level |
| DescribeDataBackupSavePlan | Queries the database backup retention plan for the next year | Resource-level |
| EndReservedRollbackInstance | Disables version rollback after version upgrade, which indicates that you can’t roll back the instance version from v5.7 to v5.6. | Resource-level |
| BatchUpgradeDBInstance | Upgrades or downgrades TencentDB instance configurations in batches, which can be applied for a source instance, disaster recovery instance, or read-only instance | Resource-level |
| DescribeSupportDeviceClass | Obtains the supported placement group model | Operation-level |
| CheckDrInstanceRecovery | Verifies whether a disaster recovery failback can be performed. Before promoting the disaster recovery instance to the source instance, you can use this API to verify the delay between these two instances and their GTIDs. If the verification is successful, the disaster recovery instance can be promoted to the source instance and a disaster recovery failback can be performed. | Resource-level |
| StartReplay | Enables point-in-time replay to a specific time or position. | Resource-level |
| DescribeSwitchableInstanceList | Obtains the list of all instances to be switched | Resource-level |
| DescribeInstanceGTIDInfo | Queries GTID information | Resource-level |
| CloseTransparentSlaveAccess | Disables the read-only access to the replica server | Resource-level |
| CheckIpInSubnet | Verifies whether an IP is within a subnet | Operation-level |
| RollbackDBInstanceEngineVersion | Rolls back the instance that initiated the version upgrade. Currently, this is only supported for upgrading from v5.6 to v5.7, that is, only v5.7 can be rolled back to v5.6 | Resource-level |
| UnAssociateSecurityGroups | Unassociates security groups from instances in batches | Resource-level |
| TransferPreToPost | Switches from monthly subscription to pay-as-you-go billing | Resource-level |
| TerminateInstanceAutoTune | Cancels parameter tunning task, which is only supported for incomplete task with instances that have not been terminated. | Resource-level |
| SubmitBatchOperation | Submits batch import tasks | Resource-level |
| StartInstanceAutoTune | Initiates parameter tunning task | Resource-level |
| ModifyRollbackInstanceSyncStatus | Ignores errors in data sync during the rollback version process after version upgrade | Resource-level |
| ModifyProtectMode | Modifies the sync mode of the instance | Resource-level |
| ModifyManualBackupName | Modifies the alias of a manual backup | Resource-level |
| ModifyBackupInfo | Modifies the backup information | Resource-level |
| DescribeTimeWindowSwitchForZone | Gets the list of regions where the maintenance window is disabled. This means that the switch tasks initiated within the maintenance window are all invalid, and no switch is performed.. | Operation-level |
| DescribeMonitorData | Gets the instance monitoring data | Resource-level |
| DescribeBatchJobFileContent | Gets batch import SQL files | Operation-level |
| DescribeBackupDownloadDbTableCode | Queries the download position of sharded databases and tables | Resource-level |
| DeleteTimeWindowSwitchForZone | Deletes a region where any switch tasks initiated by users during the maintenance window will still be valid within the maintenance window. | Operation-level |
| DeleteReadOnlyInstanceIp | Deletes the exclusive VIP for a read-only instance | Resource-level |
| DeleteBatchJobFiles | Deletes the list of batch import SQL files submitted by users | Operation-level |
| CreateBatchJobFiles | Imports and exports SQL files in batches | Operation-level |
| CancelBatchOperation | Stops batch import task | Operation-level |
| AddPartSqlFile | Saves parts information when a large SQL file is divided into multiple parts for uploading | Operation-level |
- Log in to the CAM console.
- Click Policies on the left sidebar.
Resource-level APIs
Select Create Custom Policy > Create by Policy Generator to configure policy parameters.
- Service: TencentDB for MySQL
- Resource: Select Specific resources or All resources.
Operation-level APIs
Select Create Custom Policy > Create by Policy Generator to configure policy parameters.
-Service: TencentDB for MySQL
- Resource: Select All resources.
Yes
No
Was this page helpful?