Setting Object Access Permission
Last updated: 2020-02-19 17:05:31PDF
COS allows you to set access permissions for objects, and this setting has a higher priority than that for buckets.
The object access permission is valid only when an access attempt is made to the default domain name. For any access attempt made to a CDN-accelerated or custom domain name, the bucket access permission will prevail.
By setting object access permission, you can, for example, set the specific objects which allow public access in a "private read/write" bucket or set the specific objects which only allow access after authentication in a "public read/write" bucket. Object permissions include the following types:
- Inherited bucket permission: The object has the same access permission as the bucket. When you access an object with the "inherited bucket permission", COS will match the bucket permission to respond to the access. A new object inherits the permission from its bucket by default.
- Public read/private write: When you access an object with the public read permission, the object can be directly downloaded, regardless of the bucket permission.
- Private read/write: When you access an object with the private read/write permission, the object can only be accessed after signature authentication regardless of the bucket permission.
- Log in to the COS Console and select Bucket List on the left sidebar to enter the bucket list page. Click the bucket of the object for which you want to modify access permission (such as example) to enter the bucket.
- Locate the object for which you want to set permission (such as example.exe), click More > Set Permission on its right, and the Set Permission dialog box will pop up.
- Modify the access permission and click OK to save the changes.