AS Custom Policies

Scenarios

Custom policies can be created to supplement the system-defined policies of AS. For the actions that can be added to custom policies, see Permissions Policies and Supported Actions.

You can create custom policies in either of the following ways:

• Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
• JSON: Edit JSON policies from scratch or based on an existing policy.

For operation details, see Creating a Custom Policy. The following section contains examples of common AS custom policies.

Example Custom Policies

• Example 1: Allowing users to remove instances from an AS group and create AS configurations

  {
        "Version": "1.1",
        "Statement": [
              {
                    "Effect": "Allow",
                    "Action": [
                          "as:instances:delete",
                          "as:configs:create"
                    ]
              }
        ]
  }

• Example 2: Denying AS group deletion

  A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

  The following method can be used if you need to assign permissions of the AutoScaling FullAccess policy to a user but you want to prevent the user from deleting AS groups. Create a custom policy for denying AS group deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on AS except deleting AS groups. The following is an example of a deny policy:

  { 
          "Version": "1.1", 
          "Statement": [ 
                  { 
                          "Action": [ 
                                  "as:groups:delete" 
                          ], 
                          "Effect": "Deny" 
                  } 
          ] 
  }