- Updates and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Purchasing Instances
- Creating an Enterprise Edition Instance
- Access Configuration
- Manage Image Repository
- Image Distribution
- Image Security
- Synchronization and Replication
- Configuring Image Tag Retention
- Image Cleanup
- DevOps
- OCI Artifacts Management
- Operation Guide for TCR Individual
- Terminating/Returning Instances
- Best Practices
- TCR Personal migration
- Using the Delivery Assembly Line to Implement Container DevOps
- TKE Clusters Use the TCR Addon to Enable Secret-free Pulling of Container Images via Private Network
- Synchronizing Images to TCR Enterprise Edition from External Harbor
- TKE Serverless Clusters Pull TCR Container Images
- Image Data Synchronization and Replication Between Multiple Platforms in Hybrid Cloud
- Nearby Access Through Image Synchronization Between Multiple Global Regions
- Using Custom Domain Name and CCN to Implement Cross-Region Private Network Access
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- DescribeInstances
- DescribeInstanceStatus
- CreateInstanceToken
- CreateInstance
- ModifyInstanceToken
- DescribeInstanceToken
- DeleteInstanceToken
- DeleteInstance
- RenewInstance
- CheckInstanceName
- CheckInstance
- ModifyInstance
- DescribeRegions
- DescribeInstanceCustomizedDomain
- DescribeImageAccelerateService
- DeleteInstanceCustomizedDomain
- DeleteImageAccelerateService
- CreateInstanceCustomizedDomain
- CreateImageAccelerationService
- Namespace APIs
- Image Repository APIs
- Custom Account APIs
- Trigger APIs
- Instance Synchronization APIs
- Access Control APIs
- Helm Chart APIs
- Tag Retention APIs
- Data Types
- Error Codes
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Updates and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Purchasing Instances
- Creating an Enterprise Edition Instance
- Access Configuration
- Manage Image Repository
- Image Distribution
- Image Security
- Synchronization and Replication
- Configuring Image Tag Retention
- Image Cleanup
- DevOps
- OCI Artifacts Management
- Operation Guide for TCR Individual
- Terminating/Returning Instances
- Best Practices
- TCR Personal migration
- Using the Delivery Assembly Line to Implement Container DevOps
- TKE Clusters Use the TCR Addon to Enable Secret-free Pulling of Container Images via Private Network
- Synchronizing Images to TCR Enterprise Edition from External Harbor
- TKE Serverless Clusters Pull TCR Container Images
- Image Data Synchronization and Replication Between Multiple Platforms in Hybrid Cloud
- Nearby Access Through Image Synchronization Between Multiple Global Regions
- Using Custom Domain Name and CCN to Implement Cross-Region Private Network Access
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- DescribeInstances
- DescribeInstanceStatus
- CreateInstanceToken
- CreateInstance
- ModifyInstanceToken
- DescribeInstanceToken
- DeleteInstanceToken
- DeleteInstance
- RenewInstance
- CheckInstanceName
- CheckInstance
- ModifyInstance
- DescribeRegions
- DescribeInstanceCustomizedDomain
- DescribeImageAccelerateService
- DeleteInstanceCustomizedDomain
- DeleteImageAccelerateService
- CreateInstanceCustomizedDomain
- CreateImageAccelerationService
- Namespace APIs
- Image Repository APIs
- Custom Account APIs
- Trigger APIs
- Instance Synchronization APIs
- Access Control APIs
- Helm Chart APIs
- Tag Retention APIs
- Data Types
- Error Codes
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
Note：
If you are a customer of a Tencent Cloud partner, the rules regarding resources when there are overdue payments are subject to the agreement between you and the partner.
Pay-as-You-Go Enterprise Edition Instance
Precautions
When you no longer need to use pay-as-you-go instances, terminate them as soon as possible to avoid continued fee deductions.
After an instance is terminated or repossessed, its data is cleared and cannot be recovered.
Since your actual resource consumption changes constantly, some slight discrepancies may exist for your stated balance.
When an instance in arrears is automatically repossessed, due to the restrictions of the COS billing policy, the associated backend bucket cannot be automatically deleted. Please go to the COS console console to manage the COS bucket and avoid continued fee deductions.
Alerts
Type | Description |
Arrears reminder | Pay-as-you-go resources are billed on the hour. When your account balance becomes negative, your Tencent Cloud account creator, global resource collaborators, and financial collaborators will be notified via email and SMS. |
Arrears alert | This feature is disabled by default. |
Arrears processing
To ensure that your business app updates are not affected by temporary arrears, you can continue to use TCR for 24 hours after your account balance becomes negative and will be billed for this time. If your account is still in arrears after 24 hours, the instances in your account will all be isolated and billing will stop.
After instances are isolated, the system will process them as follows:
Time Since Isolation | Description |
≤ 7 days | If your account is topped up to a positive balance, billing will resume and the instances will automatically recover to the running status. |
| If your account is not topped up to a positive balance, the instances will remain isolated. |
> 7 days | If your account is not topped up to a positive balance, your pay-as-you-go instances will be repossessed, and all data in the instances will be irrecoverably erased. When instances are repossessed, the Tencent Cloud account creator and all collaborators will be notified via email and SMS. |
When your account is in arrears, you can delete instances you do not need to avoid continued billing. For more information about deleting instances, see Terminating/Returning Instances.
Note
When an instance in arrears is automatically repossessed, due to the restrictions of the COS billing policy, the associated backend bucket cannot be automatically deleted. Please go to the COS console to manually manage the COS bucket.
Data Storage Billing and Arrears
In TCR, when an Enterprise Edition instance is created, a COS bucket will be automatically created in the region of the instance and associated with the instance. During the use of the instance, container images, Helm Charts, and other data are directly stored in the bucket. Users can view and manage relevant data and configure data encryption and backup modes. These resources are directly provided and billed by the COS service. For more information about the billing rules and arrears, see Billing Overview and Notes on Arrears.
Yes
No
Was this page helpful?