This topic describes how to grant an IAM user the permissions required to perform specific operations on an OBS bucket. Below describes how to grant the bucket deletion permission.
If you need to configure other permissions, select the corresponding actions from the Action Name drop-down list in the bucket policy. For details about the actions supported by OBS, see Action/NotAction.
You are advised to use bucket policies to grant resource-level permissions to an IAM user.
After the configuration is complete, you can delete buckets using APIs. However, if you log in to OBS Console or OBS Browser+ to delete buckets, an error is reported indicating that you do not have required permissions.
This is because when you log in to OBS Console or OBS Browser+, more APIs (such as ListAllMyBuckets and ListBucketVersions) are called to load the list of buckets and versioned objects, but your permissions do not cover those APIs. In such case, your access is denied or your operation is not allowed.
If you want an IAM user to delete buckets on OBS Console or OBS Browser+, allow the ListBucketVersions permission in the bucket policy and configure a custom IAM policy to grant the ListAllMyBuckets permission by referring to Follow-up Procedure.
Parameter |
Description |
---|---|
Policy Mode |
Select Customized. |
Effect |
Select Allow. |
Principal |
|
Resources |
Select Include > Entire bucket. |
Actions |
To configure other permissions, select the corresponding actions. For details about the actions supported by OBS, see Action/NotAction. |
To successfully delete buckets on OBS Console or OBS Browser+, you need to allow the obs:bucket:ListAllMyBuckets (for listing buckets) permission in the IAM policy.
Parameter |
Description |
---|---|
Policy Name |
Name of the custom policy |
Policy View |
Set this parameter based on your own habits. Visual editor is used here. |
Policy Content |
|
Scope |
The default value is Global services. |
Add the created custom policy to the user group by following the instructions in the IAM document.
Due to data caching, it takes about 10 to 15 minutes for a custom policy to take effect after the authorization.