- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
-
FAQs
- Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?
- What Information Is on the Trace List?
- How Will CTS Be Affected If My Account Balance Is Insufficient?
- What Are the Recommended Users of CTS?
- What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?
- Does CTS Support Integrity Verification of Trace Files?
- Why Are There Some Null Fields on the View Trace Page?
- Why Is an Operation Recorded Twice in the Trace List?
- What Services Are Supported by Key Event Notifications?
- How Can I Store Trace Files for a Long Time?
- Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?
- How Do I Find Out Who Created a Specific ECS?
- How Do I Find Out the Login IP Address of an IAM User?
- Why Are Two deleteMetadata Traces Generated When I Buy an ECS in Pay-per-Use or Yearly/Monthly?
- What If I Cannot Query Traces?
- Can I Disable CTS?
- How Do I Make the Log Retention Period 180 Days?
- What Can I Do If a Tracker Cannot Be Created on the CTS Console?
- What Should I Do If I Cannot Enable CTS as an IAM User?
- How Do I Enable Alarm Notifications for EVS?
- Can I Receive Duplicate Traces?
- What Should I Do If I Fail to Transfer Data to an OBS Bucket Authorized by a Key of Another Tenant?
- Does the cts_admin_trust Agency Include OBS Authorization?
- Does CTS Record ECS Creation Failures?
- Glossary
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Querying Traces
- Management Trackers
- Data Trackers
- Application Examples
- Trace References
- Cross-Tenant Transfer Authorization
- Verifying Trace File Integrity
- Auditing
- Permissions Management
- Supported Services and Operations
-
FAQs
- Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?
- What Information Is on the Trace List?
- How Will CTS Be Affected If My Account Balance Is Insufficient?
- What Are the Recommended Users of CTS?
- What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?
- Does CTS Support Integrity Verification of Trace Files?
- Why Are There Some Null Fields on the View Trace Page?
- Why Is an Operation Recorded Twice in the Trace List?
- What Services Are Supported by Key Event Notifications?
- How Can I Store Trace Files for a Long Time?
- Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?
- How Do I Find Out Who Created a Specific ECS?
- How Do I Find Out the Login IP Address of an IAM User?
- Why Are Two deleteMetadata Traces Generated When I Buy an ECS?
- What If I Cannot Query Traces?
- Can I Disable CTS?
- How Do I Enable Alarm Notifications for EVS?
- Can I Receive Duplicate Traces?
- Does CTS Record ECS Creation Failures?
- API Reference (ME-Abu Dhabi Region)
-
User Guide (Paris)
- Service Overview
- Getting Started
- Querying Traces
- Management Trackers
- Application Examples
- Trace References
- Cross-Tenant Transfer Authorization
- Verifying Trace File Integrity
- Auditing
- Permissions Management
- Supported Services and Operations
-
FAQs
- Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?
- How Will CTS Be Affected If My Account Balance Is Insufficient?
- What Are the Recommended Users of CTS?
- What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?
- Does CTS Support Integrity Verification of Trace Files?
- Why Are There Some Null Fields on the View Trace Page?
- Why Is an Operation Recorded Twice in the Trace List?
- What Services Are Supported by Key Event Notifications?
- How Can I Store Trace Files for a Long Time?
- Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?
- How Do I Find Out Who Created a Specific ECS?
- How Do I Find Out the Login IP Address of an IAM User?
- Why Are Two deleteMetadata Traces Generated When I Buy an ECS?
- What If I Cannot Query Traces?
- Can I Disable CTS?
- How Do I Enable Alarm Notifications for EVS?
- Can I Receive Duplicate Traces?
- Does CTS Record ECS Creation Failures?
- API Reference (Paris)
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Getting Started
- Querying Traces
- Management Trackers
- Trackers
- Organization Trackers
- Application Examples
- Trace References
- Cross-Tenant Transfer Authorization
- Verifying Trace File Integrity
- Auditing
- Permissions Management
- Supported Services and Operations
-
FAQs
- Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?
- What Information Is on the Trace List?
- How Will CTS Be Affected If My Account Balance Is Insufficient?
- What Are the Recommended Users of CTS?
- What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?
- Does CTS Support Integrity Verification of Trace Files?
- Why Are There Some Null Fields on the View Trace Page?
- Why Is an Operation Recorded Twice in the Trace List?
- What Services Are Supported by Key Event Notifications?
- How Can I Store Trace Files for a Long Time?
- Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?
- How Do I Find Out Who Created a Specific ECS?
- How Do I Find Out the Login IP Address of an IAM User?
- Why Are Two deleteMetadata Traces Generated When I Buy an ECS?
- What If I Cannot Query Traces?
- Can I Disable CTS?
- How Do I Enable Alarm Notifications for EVS?
- Can I Receive Duplicate Traces?
- Does CTS Record ECS Creation Failures?
- API Reference (Kuala Lumpur Region)
- User Guide (Ankara Region)
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- Videos
- General Reference
Show all
Copied.
Error Codes
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
CTS.0001 |
The IAM or OBS service is abnormal. |
The IAM or OBS service is abnormal. |
Contact technical support. |
400 |
CTS.0003 |
The message body is empty or invalid. |
The message body is empty or invalid. |
Verify the body content and format. |
400 |
CTS.0200 |
The number of trackers has reached the upper limit. |
The number of trackers has reached the upper limit. |
Delete or modify unnecessary trackers. |
400 |
CTS.0201 |
A management tracker has been created. |
A management tracker has been created. |
Check whether a management tracker is already available. |
400 |
CTS.0202 |
The value of the tracker_type parameter is incorrect. |
The value of tracker_type is invalid. |
Change its value to system or data. |
400 |
CTS.0203 |
The value of tracker_name parameter is in an incorrect format. |
The value of tracker_name is invalid. |
Modify its value by referring to the parameter descriptions. |
400 |
CTS.0204 |
The tracker_name parameter of a management tracker can only be set to system. |
The tracker_name parameter of a management tracker can only be set to system. |
Modify its value by referring to the parameter descriptions. |
400 |
CTS.0205 |
The status parameter can only be set to enabled or disabled. |
The status parameter can only be set to enabled or disabled. |
Change its value to enabled or disabled. |
400 |
CTS.0206 |
The data_bucket parameter cannot be included in the message body for a management tracker. |
The data_bucket parameter cannot be included in the message body for a management tracker. |
Delete the data_bucket parameter. |
400 |
CTS.0207 |
The tracker_name parameter in the message body cannot be set to system for a data tracker. |
The tracker_name parameter in the message body cannot be set to system for a data tracker. |
Change the value of tracker_name to a value other than system. |
400 |
CTS.0208 |
The tracker already exists. |
The tracker already exists. |
Check whether the tracker already exists. |
400 |
CTS.0209 |
A type of operations on an OBS bucket can be tracked by only one tracker. |
A type of operations on an OBS bucket can be tracked by only one tracker. |
Change the tracker configurations. |
400 |
CTS.0210 |
The OBS bucket to track cannot be empty. |
The OBS bucket to be tracked cannot be empty. |
Select another bucket or ensure that the bucket is not empty. |
400 |
CTS.0211 |
The tracked OBS bucket does not exist. |
The OBS bucket to be tracked does not exist. |
Check whether bucket_name is correctly set. |
400 |
CTS.0212 |
The tracked OBS bucket cannot be modified. |
The tracked OBS bucket cannot be modified. |
Withdraw the changes on the OBS bucket. |
400 |
CTS.0213 |
The OBS bucket used for trace transfer cannot be a tracked OBS bucket. |
The OBS bucket used for trace transfer cannot be a tracked OBS bucket. |
Select another OBS bucket for trace transfer. |
400 |
CTS.0215 |
The OBS bucket already exists. |
The OBS bucket already exists. |
Change the value of bucket_name. |
400 |
CTS.0216 |
Failed to create a bucket. |
Failed to create a bucket. |
Contact technical support. |
400 |
CTS.0217 |
Failed to set a lifecycle rule for the OBS bucket. |
Failed to set a lifecycle rule for the OBS bucket. |
Contact technical support. |
400 |
CTS.0218 |
The value of file_prefix_name is in an incorrect format. |
The value of file_prefix_name is invalid. |
Modify its value by referring to the parameter descriptions. |
400 |
CTS.0219 |
The operation type cannot be empty. |
The operation type cannot be empty. |
Select at least one operation type to track. |
400 |
CTS.0220 |
KMS is not supported. |
KMS is not supported. |
Contact technical support. |
400 |
CTS.0221 |
The KMS ID is empty. |
The KMS ID is empty. |
Check whether the KMS ID is correct. |
400 |
CTS.0222 |
KMS verification failed. |
KMS verification failed. |
Check whether the KMS ID is correct. |
400 |
CTS.0225 |
Only WRITE and/or READ operations on the OBS bucket can be tracked. |
The bucket operation must be write, read, or read/write. |
Check whether the input parameters are correctly set. |
400 |
CTS.0228 |
The CTS service is not trusted. |
CTS is not trusted. |
Enable CTS as a trusted service on the Organizations console. |
400 |
CTS.0229 |
The organization tracker already exists. |
The organization tracker already exists. |
Disable the enabled organization tracker first. |
400 |
CTS.0231 |
Invalid bucket name. A bucket name must be a string of 3 to 63 characters, including only lowercase letters, digits, hyphens (-), or periods (.). It must start with a digit or a lowercase letter. |
Invalid bucket name. A bucket name must contain 3 to 63 characters and start with a digit or a lowercase letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed. |
Check whether the bucket name is correct. |
400 |
CTS.0300 |
Query failed. |
Query failed. |
Try again later or contact technical support. |
403 |
CTS.0002 |
Authentication failed or you do not have the permissions required. |
Authentication failed or you do not have the permissions required. |
Check your permissions. |
403 |
CTS.0013 |
No permission, Please check roles. |
You do not have the corresponding operation permission. |
Configure the permission. |
404 |
CTS.0100 |
API version query is not supported in CTS. |
API version query is not supported in CTS. |
Contact technical support. |
404 |
CTS.0214 |
The tracker does not exist. |
The tracker does not exist. |
Check whether the tracker has been deleted. |
500 |
CTS.0004 |
Failed to write data. |
Failed to write data. |
Contact technical support. |
500 |
CTS.0005 |
Failed to read data. |
Failed to read data. |
Contact technical support. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot