Help Center/ NAT Gateway/ API Reference/ Permissions Policies and Supported Actions/ Introduction
Updated on 2022-09-24 GMT+08:00
View PDF

Introduction

This section describes fine-grained permissions management for your NAT gateways. If your account does not need individual IAM users, then you may skip this section.

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

Policy-based authorization is useful if you want to allow or deny the access to an API.

An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users that have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user wants to query NAT gateways using an API, the user must have been granted permissions that allow the nat:natGateways:list action.

Supported Actions

NAT Gateway provides system-defined policies, which can be directly used in IAM. The account administrator can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

  • Permissions: Statements in a policy that allow or deny certain operations.
  • APIs: REST APIs that can be called by a user who has been granted specific permissions.
  • Actions: Specific operations that are allowed or denied.
  • IAM or enterprise projects: Type of projects for which an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. The account administrator can check whether an action supports IAM projects or enterprise projects in the action list. The check mark (√) indicates that the action supports the project and the cross symbol (×) indicates that the action does not support the project.

NAT Gateway supports the following actions that can be defined in custom policies:

  • NAT Gateway v2, including actions supported by all v2 APIs of the NAT gateway, such as creating, updating, and deleting NAT gateways.
  • SNAT Rule v2, including actions supported by all v2 APIs of the SNAT rule, such as creating and querying SNAT rules.
  • DNAT Rule v2, including actions supported by all v2 APIs of the DNAT rule, such as creating and querying DNAT rules.