If the system policies of Cloud Monitor do not meet your requirements, you can create custom policies to implement the principle of least privilege. Custom policies allow you to achieve fine-grained control over permissions and improve resource access security. This topic describes the scenarios where custom policies are used for Cloud Monitor and provides sample custom policies.
What is a custom policy?
Resource Access Management (RAM) policies are classified into system policies and custom policies. You can manage custom policies based on your business requirements.
After you create a custom policy, you must attach the policy to a RAM user, RAM user group, or RAM role. This way, the permissions that are 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, before you can delete the RAM policy you must detach the RAM policy from the principal.
Custom policies support version control. You can manage custom policy versions based on the version management mechanism provided by RAM.
References
Common scenarios and sample custom policies
You can grant a RAM user the permissions to export metric data. Example:
{
"Version": "1",
"Statement": [
{
"Effect": "Allow",
"Action": [
"cms:BatchGet",
"cms:Cursor"
],
"Resource": [
"*"
],
"Condition": {}
}
]
}References
Before you use custom policies, you must understand the permission control requirements of your business and the authorization information about Cloud Monitor.