Permissions Management

If you need to grant your enterprise personnel permission to access your NAT Gateway resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your Huawei Cloud resources.

With IAM, you can create IAM users and grant them permissions to access only specific resources. For example, if you want some software developers in your enterprise to be able to use NAT Gateway resources but do not want them to be able to delete NAT gateways or perform any other high-risk operations, you can create IAM users and grant permission to use NAT gateways but not permission to delete them.

If your Huawei Cloudcloud account does not require individual IAM users for permissions management, you can skip this section.

IAM is a free service. You only pay for the resources in your account. For more information about IAM, see What Is IAM?

NAT Gateway Permissions

New IAM users do not have any permissions assigned by default. You need to first add them to one or more 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. Huawei 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 permission to manage a certain type of NAT gateways. 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 Permissions Policies and Supported Actions.

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

**Table 1** System-defined permissions for NAT Gateway
Policy Name	Description	Type
NAT FullAccess	All operations on NAT Gateway resources.	System-defined policy
NAT ReadOnlyAccess	Read-only permissions for all NAT Gateway resources.	System-defined policy
NAT Administrator	All operations on NAT Gateway resources. To be granted this permission, users must also have the Tenant Guest permissions.	System-defined role

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

**Table 2** Common operations supported by each system-defined policy or role of NAT Gateway
Operation	NAT FullAccess	NAT ReadOnlyAccess	NAT Gateway Administrator
Creating a NAT gateway	√	x	√
Querying NAT gateways	√	√	√
Querying NAT gateway details	√	√	√
Updating a NAT gateway	√	x	√
Deleting a NAT gateway	√	x	√
Adding an SNAT rule	√	x	√
Viewing an SNAT rule	√	√	√
Modifying an SNAT rule	√	x	√
Deleting an SNAT rule	√	x	√
Adding a DNAT rule	√	x	√
Viewing a DNAT rule	√	√	√
Modifying a DNAT rule	√	x	√
Deleting a DNAT rule	√	x	√
Deleting DNAT rules in one batch	√	x	√
Importing DNAT rules using templates	√	x	√
Exporting DNAT rules using templates	√	√	√
Creating a transit subnet	√	x	√
Querying transit subnets	√	√	√
Querying details of a transit subnet	√	√	√
Modifying a transit subnet	√	x	√
Deleting a transit subnet	√	x	√
Assigning a transit IP address	√	x	√
Querying a transit IP address	√	√	√
Releasing a transit IP address	√	x	√

To create a yearly/monthly public NAT gateway, you also need to obtain the BSS Administrator permissions of the Billing Center. For details, see the Billing Center User Guide.

Note the following when creating a DNAT rule:
- DNAT rule permissions cannot be managed by enterprise project.
- If you set Instance Type to Server and select an ECS, you also need to obtain the ECS ReadOnlyAccess permissions or the fine-grained permissions for actions ecs:cloudServers:get and ecs:cloudServers:list. For details, see the Elastic Cloud Server API Reference.
- If you set Instance Type to Server and select a BMS, you also need to obtain the BMS ReadOnlyAccess permissions or the fine-grained permissions for actions bms:servers:get and bms:servers:list. For details, see the Bare Metal Server API Reference.
- If you create a DNAT rule on a private NAT gateway and select Load balancer for Instance Type, you need to obtain the ELB ReadOnlyAccess permissions or the fine-grained permissions for actions elb:loadbalancers:get and elb:loadbalancers:list. For details, see the Elastic Load Balance API Reference.
- After a DNAT rule is created, add a security group rule to allow the Internet to access servers for which the DNAT rule is configured. Otherwise, the DNAT rule does not take effect. Obtain the VPC FullAccess permissions or the fine-grained permissions for action vpc:securityGroups:create by referring to the Virtual Private Cloud API Reference.
To view metrics, obtain the CES ReadOnlyAccess permissions. For details, see the Cloud Eye API Reference.
To view access logs, obtain the LTS ReadOnlyAccess permissions. For details, see the Log Tank Service API Reference.
To query predefined tags, obtain the TMS Administrator permissions. For details, see the Tag Management Service API Reference.