Help Center> Elastic IP> User Guide> Permissions Management> EIP Custom Policies
View PDF

EIP Custom Policies

Custom policies can be created as a supplement to the system policies of EIP. For the actions supported for custom policies, see Permissions Policies and Supported Actions.

You can create custom policies in either of the following two 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 EIP custom policies.

Example Policies

  • Example 1: Allowing users to create and view EIPs 
    { 
    "Version": "1.1", 
    "Statement": [ 
        { 
            "Effect": "Allow", 
            "Action": [ 
                " 
                     vpc:publicIps:create 
                     vpc:publicIps:list 
                 " 
            ] 
        } 
    ] 
}
  • Example 2: Denying EIP deletion

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

    The following method can be used if you need to assign permissions of the VPC FullAccess policy to a user but also forbid the user from deleting EIPs. Create a custom policy for denying EIP deletion, and assign both policies to the group the user belongs to. Then the user can perform all operations on EIP except deleting EIPs. The following is an example deny policy:

    { 
      "Version": "1.1", 
      "Statement": [ 
            { 
		  "Effect": "Deny", 
                  "Action": [ 
                        "vpc:publicIps:delete" 
                  ] 
            } 
      ] 
}
  • Example 3: Defining permissions for multiple services in a policy

    A custom policy can contain the actions of multiple services that are of the global or project-level type. The following is an example policy containing actions of multiple services:

    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ecs:servers:delete"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "vpc:publicIps:update",
                "vpc:publicIps:create"
            ]
        }
    ]
}
Parent topic: Permissions Management