- Product Introduction
- Supported Resource Types
- Purchase Guide
- Getting Started
- Operation Guide
- Resources
- Rule
- Managed Rules
- List of Managed Rule
- MFA on Sensitive Operations Required for CAM Users
- MFA on Login Required for CAM Users
- No Idle User Groups on CAM
- Association with User Group Required for CAM User
- No Authorization Policies Directly Added to CAM Sub-account
- No Administrator Access Permissions Granted to CAM Users, User Groups, or Roles
- Granting of Specific High-Risk Permissions by CAM Not Allowed
- No Idle Permission Policies on CAM
- CAM Login Permission Check
- Key of CAM User Rotated at Specified Interval
- Login by CAM User within Specified Time Range
- CVM Instance Associated with Specified Security Group
- CVM Instance Not Moved to Recycle Bin
- Association of CVM Instance with Specified Role
- CVM Instance Enabled Automatic Renewal
- Notification About Expiration for CVM Instance in Monthly Subscription or Pay-As-You-Go Mode
- No Idle Security Groups
- CVM Instance in VPC
- No CVM Instances Not Assigned to Project
- Inactive Duration of CVM Instance After Shutdown Not Exceeding Specified Number of Days
- Lease Duration of CVM Instance Meeting Requirement of Specified Number of Days
- CVM Instance Bound to IPv4 Public Address
- Specified Tag Existed for Resource
- Access to Remote Risky Ports by Security Group Not Allowed
- Access to All Ports by Security Group Not Allowed
- CBS Disk Enabled Arrear Protection
- CBS Disk Enabled Encryption
- Detachable CBS Disk Not Moved to Recycle Bin
- Number of Available IP Addresses in VPC Subnet Greater than Specified Value
- Expiration Protection for CVM Instance in Pay-As-You-Go Mode
- No Idle CBS Disks
- Using Rules
- Managing Rules
- Conformance Pack
- Settings
- API Documentation
- FAQs
- Contact Us
- Glossary
- Product Introduction
- Supported Resource Types
- Purchase Guide
- Getting Started
- Operation Guide
- Resources
- Rule
- Managed Rules
- List of Managed Rule
- MFA on Sensitive Operations Required for CAM Users
- MFA on Login Required for CAM Users
- No Idle User Groups on CAM
- Association with User Group Required for CAM User
- No Authorization Policies Directly Added to CAM Sub-account
- No Administrator Access Permissions Granted to CAM Users, User Groups, or Roles
- Granting of Specific High-Risk Permissions by CAM Not Allowed
- No Idle Permission Policies on CAM
- CAM Login Permission Check
- Key of CAM User Rotated at Specified Interval
- Login by CAM User within Specified Time Range
- CVM Instance Associated with Specified Security Group
- CVM Instance Not Moved to Recycle Bin
- Association of CVM Instance with Specified Role
- CVM Instance Enabled Automatic Renewal
- Notification About Expiration for CVM Instance in Monthly Subscription or Pay-As-You-Go Mode
- No Idle Security Groups
- CVM Instance in VPC
- No CVM Instances Not Assigned to Project
- Inactive Duration of CVM Instance After Shutdown Not Exceeding Specified Number of Days
- Lease Duration of CVM Instance Meeting Requirement of Specified Number of Days
- CVM Instance Bound to IPv4 Public Address
- Specified Tag Existed for Resource
- Access to Remote Risky Ports by Security Group Not Allowed
- Access to All Ports by Security Group Not Allowed
- CBS Disk Enabled Arrear Protection
- CBS Disk Enabled Encryption
- Detachable CBS Disk Not Moved to Recycle Bin
- Number of Available IP Addresses in VPC Subnet Greater than Specified Value
- Expiration Protection for CVM Instance in Pay-As-You-Go Mode
- No Idle CBS Disks
- Using Rules
- Managing Rules
- Conformance Pack
- Settings
- API Documentation
- FAQs
- Contact Us
- Glossary
1. Service Address
The API supports access from either a nearby region (at config.intl.tencentcloudapi.com) or a specified region (at config.ap-guangzhou.tencentcloudapi.com for Guangzhou, for example).
We recommend using the domain name to access the nearest server. When you call an API, the request is automatically resolved to a server in the region nearest to the location where the API is initiated. For example, when you initiate an API request in Guangzhou, this domain name is automatically resolved to a Guangzhou server, the result is the same as that of specifying the region in the domain like "config.ap-guangzhou.tencentcloudapi.com".
Note: For latency-sensitive businesses, we recommend that you specify the region in the domain name.
Tencent Cloud currently supports the following regions:
| Hosted region | Domain name |
|---|---|
| Local access region (recommended, only for non-financial availability zones) | config.intl.tencentcloudapi.com |
| South China (Guangzhou) | config.ap-guangzhou.tencentcloudapi.com |
| East China (Shanghai) | config.ap-shanghai.tencentcloudapi.com |
| North China (Beijing) | config.ap-beijing.tencentcloudapi.com |
| Southwest China (Chengdu) | config.ap-chengdu.tencentcloudapi.com |
| Southwest China (Chongqing) | config.ap-chongqing.tencentcloudapi.com |
| Hong Kong, Macao, Taiwan (Hong Kong, China) | config.ap-hongkong.tencentcloudapi.com |
| Southeast Asia (Singapore) | config.ap-singapore.tencentcloudapi.com |
| Southeast Asia (Bangkok) | config.ap-bangkok.tencentcloudapi.com |
| South Asia (Mumbai) | config.ap-mumbai.tencentcloudapi.com |
| Northeast Asia (Seoul) | config.ap-seoul.tencentcloudapi.com |
| Northeast Asia (Tokyo) | config.ap-tokyo.tencentcloudapi.com |
| U.S. East Coast (Virginia) | config.na-ashburn.tencentcloudapi.com |
| U.S. West Coast (Silicon Valley) | config.na-siliconvalley.tencentcloudapi.com |
| Europe (Frankfurt) | config.eu-frankfurt.tencentcloudapi.com |
2. Communications Protocol
All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communication tunnels.
3. Request Methods
Supported HTTP request methods:
- POST (recommended)
- GET
The Content-Type types supported by POST requests:
- application/json (recommended). The TC3-HMAC-SHA256 signature algorithm must be used.
- application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature algorithm must be used.
- multipart/form-data (only supported by certain APIs). You must use TC3-HMAC-SHA256 to calculate the signature.
The size of a GET request packet is up to 32 KB. The size of a POST request is up to 1 MB when the HmacSHA1 or HmacSHA256 signature algorithm is used, and up to 10 MB when TC3-HMAC-SHA256 is used.
4. Character Encoding
Only UTF-8 encoding is used.
Yes
No
Was this page helpful?