If the 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 implement fine-grained access control and improve your resource security. This topic describes the common scenarios in which Database Autonomy Service (DAS) custom policies are used and provides examples of DAS custom policies.
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 maintain custom policies.
After you create a custom policy, you need to attach it to a RAM user, a user group, or a RAM role so that the permissions specified in the policy can be granted to the principal.
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 support version control. You can manage custom policy versions based on the version management mechanism provided by RAM.
References
Common scenarios and examples of custom policies
For information about an example of custom policies, see the Sample custom policy section of the "How do I use DAS as a RAM user?" topic.
RAM authorization
We recommend that you understand the permission control requirements and detailed permissions on DAS before you create a custom policy. For more information, see RAM authorization.