This topic provides answers to the most frequently asked questions about TOS billing.
Purchasing or cancelling resource packages
When does a resource package take effect after purchase?
The package takes effect immediately after purchase.
Do I need to manually apply the resource package after purchasing it?
No, the package will apply automatically to eligible usage. No manual action is required.
What types of resource packages are supported?
Are resource packages refundable?
Does TOS support auto-renewal for resource packages?
Yes. Once you purchase a resource package and enable auto-renewal, the system will automatically renew it according to the renewal rules you configured. For detailed steps, see Renewing resource packages. Using resource packages
How can I view the details of my resource package usage?
Can resource packages be applied across accounts or regions?
Cross-region usage is supported, but cross-account usage is not.
Can resource packages be stacked?
- Resource packages of the same type are stackable. For example, if you purchase several standard storage capacity packages, TOS will apply them in the order of purchase.
- Resource packages of different types cannot be stacked. For example, standard storage capacity packages and infrequent access storage capacity packages cannot be combined.
Why is my account still in arrears even after I purchased a resource package?
Possible reasons:
- Resource package exhausted: Exceeding the package quota will trigger pay-as-you-go billing. An insufficient account balance will result in arrears.
- Non-coverable fees: TOS resource packages only apply to specific billable items. Any other usage is charged separately at pay-as-you-go rates. An insufficient account balance will result in arrears. To learn more, see Billing overview.
Will data stored in TOS be retained if my account is in arrears?
If you do not pay your arrears within 24 hours, Volcano Engine will suspend your TOS service but will retain your data. Since retained data occupies storage resources, your arrears will increase. For more information on calculating the increase, see Storage. If you do not pay your arrears within 15 days of service suspension, Volcano Engine will consider this to be your decision to discontinue TOS and will terminate your terms and delete all your data. This data cannot be restored.
Why doesn't the remaining balance of my resource package ever change?
Possible reasons:
- Non-coverable fees: Each type of resource package can only offset one type of billable item. For example, a Standard Storage resource package can only offset Standard Storage usage. If you purchased a standard storage capacity package and incurred Infrequent Access Storage charges, the package would not apply to those charges. Thus, the remaining balance would remain unchanged.
- TOS billing delay: TOS calculates the usage of all billable items on an hourly basis and generates bills accordingly, deducting the corresponding resource packages. However, there may be a delay in TOS billing. We recommend checking the remaining balance of the resource package again after receiving the bill.
Why can't I see the details of the deductions for the resource package?
Possible reasons:
- There may be a delay in TOS billing. We recommend checking the remaining balance of the resource package again after receiving the bill.
- The resource package is not applicable to the billed items, so no deduction occurs and no corresponding deduction details are available.
Bills
How can I check my TOS bill?
How can I view TOS bills by project?
Navigate to Billing center > Split bills. On the Split bills page, select the Billing cycle, Project, and Period. Set Product to Torch Object Storage. After configuring these settings, you can view bills by project. TOS service
How can I disable TOS service?
Once activated, the TOS service cannot be disabled. If you no longer need it, you can delete all objects in the buckets and then delete the buckets.
Will deleting TOS service affect existing data and deployments?
Deleting TOS data usually does not affect data and deployments on your Elastic Compute Service (ECS). However, we recommend verifying that there are no discrepancies between the data in TOS and the data in ECS before deletion to avoid missing data.