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.
A Huawei Cloud account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries NAT gateways using an API, the user must have been granted permissions that allow the nat:natGateways:list action.
Supported Actions
GaussDB(for openGauss) provides system-defined policies that can be directly used in IAM. You can also create custom policies and use them to supplement system-defined policies, implementing 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: added to a custom policy to control permissions for specific operations.
- IAM projects or enterprise projects: Type of projects in which policies can be used to grant permissions. A policy can be applied to IAM projects, enterprise projects, or both. 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 check mark (√) indicates that an action takes effect. The cross mark (x) indicates that an action does not take effect.
NAT Gateway supports the following actions that can be defined in custom policies:
- Public NAT Gateways, including actions supported by all v2 APIs of the NAT gateway, such as creating, updating, and deleting NAT gateways.
- SNAT Rules of Public NAT Gateways, including actions supported by all v2 APIs of the SNAT rule, such as creating and querying SNAT rules.
- DNAT Rules of Public NAT Gateways, including actions supported by all v2 APIs of the DNAT rule, such as creating and querying DNAT rules.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot