Release Notes
Announcements
Category | Specifications and Limits | Description |
QPS | Limits | Read/Write requests: 30,000 QPS for each bucket in a public cloud region in the Chinese mainland, or 3,000 QPS for each bucket in other regions. Requests to list objects/historical versions/in-progress multipart upload tasks in a bucket: 1,000 QPS for each bucket in all regions by default. Bucket creating/deleting/listing requests: 50 QPS for each `APPID` in all regions. Data retrieval requests: 100 QPS for each bucket in all regions. One-time inventory job creating requests: 1 QPS for each bucket in all regions. Single-file upload/deletion/listing requests for traffic throttling: 50 QPS. Single-file download requests for traffic throttling: 1,000 QPS.To raise your QPS threshold, see Request Rate and Performance Optimization. |
Bandwidth | Limits | 15 Gbps of upstream and downstream bandwidth for each bucket in a public cloud region in the Chinese mainland, 10 Gbps for each bucket in other regions. If this threshold is reached, traffic throttling will be requested. To raise the threshold, submit a ticket. |
Storage class | MAZ_STANDARD/STANDARD limits | Billing limits: There is no limit on storage duration or object size. |
| MAZ_STANDARD_IA/STANDARD_IA limits | Billing limits: An object stored less than 30 days is billed as 30 days. An object smaller than 64 KB is billed as 64 KB. If the object size is greater than or equal to 64 KB, it is billed based on its actual size.For more information about the billing of STANDARD_IA, see Product Billing. |
| MAZ_INTELLIGENT TIERING/INTELLIGENT TIERING limits | Billing limits: An object smaller than 64 KB is always stored in the frequent access tier. Objects are billed based on their actual sizes. For INTELLIGENT TIERING pricing, see Pricing | Cloud Object Storage. |
| ARCHIVE limits | Billing limits: An object stored less than 90 days is billed as 90 days. An object smaller than 64 KB is billed as 64 KB. If the object size is greater than or equal to 64 KB, it will be billed based on its actual size.For more information about the billing of ARCHIVE, see Product Pricing. |
| DEEP ARCHIVE limits | Billing limits: An object stored less than 180 days is billed as 180 days. An object smaller than 64 KB is billed as 64 KB. If the object size is greater than or equal to 64 KB, it will be billed based on its actual size.For more information about the billing of DEEP ARCHIVE, see Product Pricing. |
Bucket | Limits | Once a bucket is created, you cannot modify its name or region. Buckets must have unique names under the same account and cannot be renamed. A bucket name cannot start with a hyphen and can contain only lowercase letters, digits, and hyphens. The length of a bucket name is limited by the number of characters in the region abbreviation as described in Regions and Access Endpoints and `APPID`. A complete request domain name can contain up to 60 characters. |
| Number of buckets | Each root account can have up to 200 buckets by default. |
| Number of objects | There is no limit on the number of objects stored in each bucket. |
| Number of bucket tags | Each bucket can have up to 50 different tags. |
Object | Limits | |
| Upload | A single object to be uploaded in the console can be up to 512 GB. A single object to be uploaded through an API/SDK can be up to 48.82 TB (50,000 GB). Upload API specifications: Simple upload: A single object can be up to 5 GB. For more information, see Simple Upload. Multipart upload: A single object can be up to 48.82 TB. The part size can be 1 MB–5 GB, but the last part can be smaller than 1 MB. There can be 1–10,000 parts. For more information, see Multipart Upload. Currently, for a bucket with MAZ configuration enabled, objects can be uploaded to MAZ storage classes (MAZ_STANDARD or MAZ_STANDARD_IA). If intelligent tiering configuration is also enabled for the bucket, objects can also be uploaded to the MAZ_INTELLIGENT TIERING storage class. You can only upload objects to the INTELLIGENT TIERING storage class if you have enabled INTELLIGENT TIERING for the bucket. How objects are transitioned between tiers depends on the INTELLIGENT TIERING configuration. |
| Replication | Objects can be replicated within and across regions under the same account. Intra-region replication is free of charge, while cross-region replication incurs traffic fees. For more information, see Pricing | Cloud Object Storage. Copy APIs specifications: Simple copy: A single object to be copied can be up to 5 GB. For more information, see Simple Copy. If an object is larger than 5 GB, you must use multipart copy. A single object to be copied can be up to 48.82 TB. For more information, see Multipart Copy. Objects in MAZ buckets cannot be replicated to an OAZ bucket. Currently, you cannot copy STANDARD, STANDARD_IA, or INTELLIGENT TIERING objects to the INTELLIGENT TIERING storage class. |
| Batch deletion | Up to 1,000 objects can be deleted in a single request through APIs/SDKs. |
| Number of object tags | Each object can have up to 10 different tags. |
Access policy | Number of ACLs | Each root account (APPID) can have up to 1,000 bucket ACLs. |
Lifecycle | Number of rules | Each bucket can have up to 1,000 lifecycle rules. |
| Storage class transition | STANDARD to STANDARD_IA: At least 1 day. STANDARD/STANDARD_IA to ARCHIVE/DEEP ARCHIVE: At least 1 day. Note: Objects in the MAZ_STANDARD or MAZ_STANDARD_IA storage class cannot be transitioned to the STANDARD, STANDARD_IA, or ARCHIVE storage class. Objects smaller than 64 KB will not be transitioned. |
| Expired object deletion | STANDARD/STANDARD_IA/ARCHIVE: At least 1 day. |
SDKs | | 14 SDKs: Android, C, C++, .NET, Flutter, Go, iOS, Java, JavaScript, Node.js, PHP, Python, React Native, WeChat Mini Program. |
API reserved fields | | All API fields involved in the API documentation are COS reserved fields, including: acl, uploads, policy, cors, delete, versions, location, referer, lifecycle, versioning, notification, replication, website, logging, tagging, accelerate, domain, inventory, origin, object-lock, live, encryption, intelligenttiering, symlink. |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan