Actions Supported by Policy-based Authorization
This section describes fine-grained permissions management for your IEF resources. If your cloud account does not need individual Identity and Access Management (IAM) users, you can skip this section.
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and 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.
You can grant users permissions by using roles and policies. Roles are provided by IAM to define service-based permissions that match users' job 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.
- IEF does not support enterprise projects or project-based authorization.
Your account has all the permissions required to call all APIs. If you use IAM users in your account to call an API, the IAM users must be granted the required permissions. The required permissions are determined by the actions supported by the API. Only users with the policies allowing for those actions can call the API successfully. For example, if an IAM user wants to call an API to query ECSs, the user must be granted the permissions allowing for action ecs:servers:list.
Supported Actions
IEF 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 lists common concepts related to policies:
- Permissions: statements 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.
- Related actions: actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the related actions.
- IAM projects: the authorization scope of a custom policy. The authorization scope supports only IAM project authorization and does not support enterprise project authorization. This means a custom policy takes effect only when a user group is authorized within IAM. If authorization is performed through Enterprise Management, the custom policy will not take effect.
The check mark (√) and cross symbol (×) respectively indicate that an action takes effect or does not take effect for the corresponding type of projects.
|
Permission |
API |
Action |
Related Action |
IAM Project |
Enterprise Project |
|---|---|---|---|---|---|
|
Creating an application template version |
POST /v2/{project_id}/edgemgr/apps/{app_id}/versions |
ief:appVersion:create |
- |
√ |
× |
|
Deleting an application template version |
DELETE /v2/{project_id}/edgemgr/apps/{app_id}/versions/{version_id} |
ief:appVersion:delete |
- |
√ |
× |
|
Querying application template version information |
GET /v2/{project_id}/edgemgr/apps/{app_id}/versions/{version_id} |
ief:appVersion:get |
- |
√ |
× |
|
Querying a list of application template versions |
GET /v2/{project_id}/edgemgr/apps/{app_id}/versions |
ief:appVersion:list |
- |
√ |
× |
|
Updating an application template version |
PUT /v2/{project_id}/edgemgr/apps/{app_id}/versions/{version_id} |
ief:appVersion:update |
- |
√ |
× |
|
Creating an application template |
POST /v2/{project_id}/edgemgr/apps |
ief:application:create |
- |
√ |
× |
|
Deleting an application template |
DELETE /v2/{project_id}/edgemgr/apps/{app_id} |
ief:application:delete |
- |
√ |
× |
|
Querying application template information |
GET /v2/{project_id}/edgemgr/apps/{app_id} |
ief:application:get |
- |
√ |
× |
|
Querying a list of application templates |
GET /v2/{project_id}/edgemgr/apps |
ief:application:list |
- |
√ |
× |
|
Updating an application template |
PUT /v2/{project_id}/edgemgr/apps/{app_id} |
ief:application:update |
- |
√ |
× |
|
Creating a deployment |
POST /v3/{project_id}/edgemgr/deployments |
ief:deployment:create |
- |
√ |
× |
|
Deleting a deployment |
DELETE /v3/{project_id}/edgemgr/deployments/{deployment_id} |
ief:deployment:delete |
- |
√ |
× |
|
Querying deployment information |
GET /v3/{project_id}/edgemgr/deployments/{deployment_id} |
ief:deployment:get |
- |
√ |
× |
|
Querying a list of deployments |
GET /v3/{project_id}/edgemgr/deployments |
ief:deployment:list |
- |
√ |
× |
|
Updating a deployment |
PUT /v3/{project_id}/edgemgr/deployments/{deployment_id} |
ief:deployment:update |
- |
√ |
× |
|
Starting or stopping an edge node |
POST /v2/{project_id}/edgemgr/nodes/{node_id}/action |
ief:node:action |
- |
√ |
× |
|
Creating an edge node |
POST /v2/{project_id}/edgemgr/nodes |
ief:node:create |
- |
√ |
× |
|
Creating an edge node certificate |
POST /v2/{project_id}/edgemgr/nodes/{node_id}/certs |
ief:node:createNodeCert |
- |
√ |
× |
|
Deleting an edge node |
DELETE /v2/{project_id}/edgemgr/nodes/{node_id} |
ief:node:delete |
- |
√ |
× |
|
Deleting an edge node certificate |
DELETE /v2/{project_id}/edgemgr/nodes/{node_id}/certs/{cert_id} |
ief:node:deleteNodeCert |
- |
√ |
× |
|
Querying edge node information |
GET /v2/{project_id}/edgemgr/nodes/{node_id} |
ief:node:get |
- |
√ |
× |
|
Querying a list of edge nodes |
GET /v2/{project_id}/edgemgr/nodes |
ief:node:list |
- |
√ |
× |
|
Querying edge node certificates |
GET /v2/{project_id}/edgemgr/nodes/{node_id}/certs |
ief:node:listNodeCert |
- |
√ |
× |
|
Updating an edge node |
PUT /v2/{project_id}/edgemgr/groups/{group_id}/nodes |
ief:node:update |
- |
√ |
× |
|
Upgrading an edge node |
POST /v2/{project_id}/edgemgr/nodes/{node_id}/upgrade |
ief:node:upgrade |
- |
√ |
× |
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