Cloud Object Storage (COS) supports limiting object sizes upon the upload, which allows you to manage storage space flexibly by avoiding uploading objects that are too large or too small to make full use of the bandwidth and storage space. This document gives two samples to describe how to control the objects sizes in a refined way.
Prerequisites
The samples use the information below:
APPID of the root account: 1250000000
Bucket name: examplebucket-1250000000
In practice, please replace with your own bucket and use an account with the appropriate permissions and secret key to operate the bucket.
Sample 1. Specifying a Size Range During POST Object Uploads
When uploading objects using POST Object, you can add content-length-range in the HTML form to control the object size in this request as follows:
[ "content-length-range", minNum, maxNum ]
Sample:
[ "content-length-range", 1, 10]
The JSON-formatted field above is added to policy > conditions in the POST request form. A complete policy with this field carried is as follows:
Sample 2. Specifying a Size Range when Applying for a Temporary Credential
The method used in sample 1 is easy, which requires only one parameter in the HTML form. However, it only supports POST Object but not PUT Object. Moreover, since the requester can still modify the parameter in requests, uploading objects beyond the specified size range is still possible, making it hard for central management.
To solve the problem above, bucket managers can use the following fields to limit the object size when applying for a temporary key. For COS objects, use the fixed cos:content-length.
Condition Field
Description
Example
numeric_greater_than
A number greater than
{"numeric_greater_than": {"cos:content-length": 1}}, The object size must be greater than 1 byte.
numeric_greater_than_equal
A number greater than or equal to
{"numeric_greater_than_equal": {"cos:content-length": 1}}, The object size must be greater than or equal to 1 byte.
numeric_less_than
A number smaller than
{"numeric_less_than": {"cos:content-length": 1}}, The object must be smaller than 1 bytes.
numeric_less_than_equal
A number smaller than or equal to
{"numeric_less_than_equal": {"cos:content-length": 1}}, The object must be smaller than 10 bytes.
For the complete request sample, please see the Obtaining a Temporary Access Credential API Documentation of STS. A complete policy is as follows:
With the temporary credential obtained using the following policy, you can call the PUT Object or POST Object API to upload objects to the examplebucket-1250000000 bucket, with the object sizes limited to [1, 10), in bytes.
Note:
This policy is only applicable to the cos:PutObject and cos:PostObject actions. Using other actions such as cos:GetObject will fail.
This method allows bucket managers or the authentication center to centrally apply for temporary credentials and limit the size during the application, after which the credentials can be distributed to operators or business modules. In this way, object sizes can be controlled, avoiding uploading objects beyond the size range due to parameter modification.
Response
If the size of the uploaded object is within the specified range, the upload request will succeed with 200 or 204 returned. Otherwise, 403 will be returned, as shown below:
2. Click Bucket List on the left sidebar, select the bucket to which you want to add a bucket policy, and enter the bucket.
3. Click Permission Management > Policy Settings.
4. Based on your requirements, choose either Graphical Settings or Policy Syntax to add a bucket policy. For information on configuration items, please refer to Access Policy Language Overview.
5. When configuring bucket permission settings, set content-type to specify the file type, as shown in the image below:
Note
Supported file types: JPG, JPEG, PNG.
6. Click Confirm to save the policy. The policy is as follows:
