Help Center> NAT Gateway> User Guide> Permissions Management> NAT Gateway Custom Policies
Updated on 2024-03-15 GMT+08:00
View PDF

NAT Gateway Custom Policies

You can create custom policies to supplement system-defined policies of NAT Gateway. For the actions that can be added to custom policies, see Permissions Policies and Supported Actions.

To create a custom policy, choose either visual editor or JSON.

  • Visual editor: Select cloud services, actions, resources, and request conditions. You do not need to have knowledge of the policy syntax.
  • JSON: Create a JSON policy or edit an existing one.

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

Example Policies

  • Example 1: Grant permissions to create and delete a NAT gateway.
    {
      "Version": "1.1",
      "Statement": [
            {
                  "Effect": "Allow",
                  "Action": [
                        "nat:natGateways:create",
                        "nat:natGateways:delete"
                  ]
            }
      ]
}
  • Example 2: Grant permission to deny NAT gateway deletion.

    A policy with only "Deny" permissions must be used together with other policies. 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 NAT Gateway FullAccess policy to a user but also forbid the user from deleting NAT gateways. Create a custom policy for denying NAT gateway deletion, and attach both policies to the group to which the user belongs. Then the user can perform all operations on NAT gateways except deleting NAT gateways. The following is an example of a deny policy:

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

    A custom policy can contain 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": [
        {
            "Action": [
                "nat:natGateways:update",
                "nat:natGateways:create"
            ],
            "Effect": "Allow"
        },
        {
            "Action": [
                "vpc:vpcs:update"
            ],
            "Effect": "Allow"
        }
    ]
}

Parent topic: Permissions Management