All Products
Search
Document Center

Object Storage Service:Custom policies for OSS

Last Updated:Mar 18, 2024

If system policies do not meet your requirements, you can configure custom policies to implement the principle of least privilege. You can use custom policies to achieve fine-grained control over permissions and increase resource access security. This topic describes application scenarios and examples of custom policies in Object Storage Service (OSS).

What is a custom policy?

Resource Access Management (RAM) policies are classified into system policies and custom policies. You can create, update, and delete custom policies. You need to manage the versions of custom policies.

  • After you create a custom policy, you need to attach the policy to intended RAM users, user groups, or RAM roles to grant them the permissions defined in the policy.

  • You can delete a RAM policy that is not attached to a principal. If the RAM policy is attached to a principal, you must detach the RAM policy from the principal before you can delete the RAM policy.

  • Custom policies can be versioned. You can manage the versions of your custom policies in accordance with the defined RAM version management rules.

References

Common scenarios and examples of custom policies

RAM authorization

To use custom policies for access control, you need to understand your access control requirements in your business scenarios and OSS authorization information. For more information, see RAM policies.