Last updated：2021-07-06 15:04:36
You can separately set read/write permissions for the existing buckets or objects. Bucket permissions include public read/write, public read, and private. Object permissions include public read and private.
|Public read/write||All users have read and write permissions on the bucket. They are allowed to list all objects in the bucket and upload, create, overwrite, or delete objects in the bucket. We recommend that you do not grant this permission on buckets.||Not applicable.|
|Public read||The bucket owner has read and write permissions on the bucket and can upload, delete, and list objects. Other users, including anonymous users, have read permissions on the bucket. They are allowed to list all objects in the bucket.||All users have read permissions on the object. They are allowed to download the object and read the object data and its metadata.|
|Private||The bucket owner has read and write permissions on the bucket and can upload, delete, and list objects. Other users, including anonymous users, do not have read or write permissions on the bucket.||The object owner has read permissions on the object and can download the object. Other users, including anonymous users, do not have access permissions on the object.|
Object permissions are not inherited from bucket permissions. They apply to different scopes. When the permission of a bucket is set to public, it does not mean that objects in the bucket are public. To allow all users to access an object, you need to set the permission of the object to public.
When the permission of an object is set to private, you can generate a temporary external link for the object in the console so that all users can access the object within the validity period of the external link.
Log in to the KS3 console and click Bucket in the left navigation pane. On the Bucket list page, click the name of the target bucket. On the page that appears, click Bucket Settings. On the Basic settings tab, click Edit next to Bucket Permissions.
Source image protection
After you enable source image protection, source images in your bucket can only be accessed by using styles. For more information, see Create Picture Styles. Currently, styles are only applicable to image processing. Before you enable source image protection for a bucket, make sure that the bucket stores only images.
Some objects in a bucket are cached on Content Delivery Network (CDN) nodes during access, and the cache is retained for a maximum of 24 hours. Therefore, you need to manually use the cache refresh feature of CDN to clear the cache, which affects the access speed of your users.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.