Billing-related issues

Why Does My Bucket Generate Storage Fees Even Though There Are No Objects in It?

If your bucket has no objects but still generates fees, check whether the following conditions exist:

• Objects not permanently deleted: If you enabled replica management, objects in the bucket will not be deleted permanently upon one deletion action and will be stored as historical replicas. This can cause deleted objects to generate fees.

• Parts: Parts can exist in the bucket. These are due to historical actions or requests. You can clear up the parts.

What Causes Traffic in My Bucket Even When It Contains No Objects?

Possible cause 1: Inbound traffic is accounted for in real-time during file uploads. It is possible that users have uploaded files to the bucket and subsequently deleted them. As a result, while no objects are currently visible in the bucket, inbound traffic would have been recorded.

Possible cause 2: Interruptions during file uploads, due to unknown factors, may result in only partial file segments being uploaded without forming a complete object. Nevertheless, traffic is recorded during the upload of these segments.

How is the number of API requests calculated?

Any operation in ZOS performed using the console, tools, API, SDK, or other methods calls the ZOS API, and each such call is considered as a request.

Requests are categorized into read operations, write operations, and object deletions. For example, downloading, uploading, and listing objects contribute to the total number of requests.

Why Am I Still Being Billed After I Buy a Resource Package?

The possible causes are as follows:

Your resource package is not applicable to the resources you use.
Your resource package quota has been used up.
Your resource package cannot be used for the billed bucket.
Your resource package does not cover all of the ZOS billing items.

If the problem persists, please contact our agents for assistance.

Storage Bucket and Object (File) FAQs

What Can I Do When I Failed to Create a Bucket?

Common reasons for encountering issues while creating a bucket include:

Network connectivity: Check the status of the network connection between your local device and ZOS. Make sure that the network connectivity is normal.

Overdue payments or insufficient balance: Check whether your account has any overdue payments or insufficient balance. If there are overdue payments, top up your account to restore its availability.

Lack of permissions: Check whether your account has the necessary permissions for creating buckets. If not, reach out to the administrator or an eligible user to grant you the required permissions.

Cap on the bucket quantity: If you have already created 100 buckets, you are not able to create additional ones. Consider deleting unnecessary buckets to free up the quota.

If this issue persists, contact the technical support of eSurfing Cloud and provide a detailed description of the problem to receive assistance.

Can Files Be Restored After Being Deleted or Overwritten?

If the versioning feature is not enabled for a bucket, files within the bucket cannot be restored after they are deleted or overwritten. In this case, exercise caution when you delete or overwrite files, and back up important data to prevent accidental data loss.

The versioning feature helps you manage accidental data deletion and other data-related issues. When you enable the versioning feature for a bucket, data within the bucket can be easily restored. This feature allows you to maintain multiple versions of an object and retrieve or restore data as needed. In this case, when a file is deleted or overwritten, it becomes a historical version rather than being permanently deleted. You can restore the file as needed. For more information, see Recovering Files.

Can I Upload Individual Files Exceeding 5 GB? What are the procedures?

Using the console, you can upload up to 100 files, each with a capacity limit of 5 GB, all at once.

If you need to upload a file exceeding 5 GB, consider using the SDK or ZOSBrowser. For more information, see Segmented Uploading of Large Files.

Is Encrypted Uploading of Objects Supported by ZOS?

Yes, ZOS supports encrypted uploading of objects. When server-side encryption is enabled for a bucket, objects uploaded to that bucket are encrypted for storage. Specifically, the uploaded data is encrypted at the server end, and the encrypted data is stored in ZOS as ciphertext.

When you download encrypted objects, they are decrypted at the server end and displayed as plaintext. This process ensures data security during transmission and protects the data from being accessed by unauthorized users.

Exercise caution when handling encryption keys for ZOS objects to ensure data security and reliability.

Does ZOS support static website hosting? Where can I configure this feature? What are the procedures?

Yes. However, this feature is not publicly available due to regulatory compliance requirements from the Ministry of Industry and Information Technology (MIIT) of China. To use this feature, submit a ticket to apply for permissions.

The procedures of using static website hosting are as follows:

Store static website files: Upload static website files to ZOS. You can complete this task using the web management page, API, or CLI tools. File types include HTML pages, CSS style sheets, JavaScript code, and other resource files.
Create buckets: Create buckets in ZOS.

The buckets serve as containers organizing and managing files. In general, each website is hosted in a unique bucket.
Set access policies and permissions: You must configure access policies and permissions to allow users to access the files over the Internet. In general, ZOS offers the Public Read option, allowing users to download files through a web browser.
Allocate custom domain names: To facilitate user access to websites, you can associate a custom domain name with a ZOS bucket. This is achieved by mapping domain names to ZOS addresses. For example, you can configure a CNAME record to point to the bucket URL.
Configure static website hosting: ZOS provides an option for static website hosting. You can specify a default file (such as index.html), and define error page and redirection rules.
Website access: After completing the preceding procedures, you can use one of the custom domain names to access the corresponding static website. When the access request is sent to the bucket, ZOS resolves it and returns the corresponding file as the website content for the browser to display.

Zettabyte Object Storage

Hot FAQs