If system policies cannot meet your business requirements, you can create custom policies to implement the principle of least privilege. You can use custom policies to implement fine-grained permission control and improve the security of your resources. This topic describes how to use custom policies 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
Sample custom policies
Grant permissions to create a workflow.
{ "Version": "1", "Statement": [ { "Effect": "Allow", "Action": [ "composer:CreateFlow", "composer:ListConnectors", "composer:GetFlow", "composer:ListFlowTriggers", "composer:ListConnectorTriggers", "composer:ListFlows", "composer:DescribeConnectorAttribute", "composer:ListInvocationLogs", "composer:DescribeConnectorCapability", "composer:UpdateFlow" ], "Resource": "*" } ] }Grants permission to view a workflow.
{ "Version": "1", "Statement": [ { "Effect": "Allow", "Action": [ "composer:GetFlow", "composer:GetVersion", "composer:ListFlows", "composer:ListInvocationLogs", "composer:ListFlowTriggers", "composer:DescribeConnectorCapability", "composer:ListFlowConnections", "composer:ListVersions" ], "Resource": "*" } ] }