Permissions Management

New IAM users do not have any permissions assigned by default. You need to first add them to one or more user groups and then attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.

NAT Gateway is a project-level service deployed for specific regions. To assign NAT Gateway permissions to a user group, specify the scope as region-specific projects and select projects for which you want the permissions to take effect. If you select All projects, the permissions will take effect for the user group in all region-specific projects. When accessing NAT gateways, the users need to switch to the authorized region.

You can grant users permissions by using roles and policies.

• Roles: A coarse-grained authorization strategy that defines permissions by job responsibility. Only a limited number of service-level roles are available for authorization. Cloud services often depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.

• Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permissions to manage a certain type of NAT gateways and SNAT rules. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by NAT Gateway, see section "Permissions Policies and Supported Actions" in the NAT Gateway API Reference.

Table 1 lists all the system-defined permissions for NAT Gateway.

Table 2 lists the common operations supported by each NAT Gateway system policy or role. Select the policies or roles as required.