All Products
Search
Document Center

Function Compute:RAM authorization

Last Updated:Nov 22, 2024
Resource Access Management (RAM) is a service provided by Alibaba Cloud to manage user identities and resource access permissions. You can use RAM to prevent RAM users from sharing the AccessKey pairs of your Alibaba Cloud account. You can also use RAM to grant minimum permissions to RAM users. RAM uses policies to define permissions.
This topic describes the elements, such as Action, Resource, and Condition, which are defined by FCV3. You can use the elements to create policies in RAM. The code (RamCode) in RAM that is used to indicate FCV3 is [{"popCode":"FC","ramCodes":["fc"]}]. You can grant permissions on FCV3 at the RESOURCE.

General structure of a policy

Policies can be stored as JSON files. The following code provides an example on the general structure of a policy:
{
  "Version": "1",
  "Statement": [
    {
      "Effect": "<Effect>",
      "Action": "<Action>",
      "Resource": "<Resource>",
      "Condition": {
        "<Condition_operator>": {
          "<Condition_key>": [
            "<Condition_value>"
          ]
        }
      }
    }
  ]
}
The following list describes the fields in the policy:
  • Effect: specifies the authorization effect. Valid values: Allow, Deny.
  • Action: specifies one or more API operations that are allowed or denied. For more information, see the Action section of this topic.
  • Resource: specifies one or more resources to which the policy applies. You can use an Alibaba Cloud Resource Name (ARN) to specify a resource. For more information, see the Resource section of this topic.
  • Condition: specifies one or more conditions that are required for the policy to take effect. This is an optional field. For more information, see the Condition section of this topic.
    • Condition_operator: specifies the conditional operators. Different types of conditions support different conditional operators. For more information, see Policy elements.
    • Condition_key: specifies the condition keys.
    • Condition_value: specifies the condition values.

Action

FCV3 defines the values that you can use in the Action element of a policy statement. The following table describes the values.
  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • API operation: the API operation that you can call to perform the operation.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition key: the condition keys that are defined by the Alibaba Cloud service. The Condition key column does not list the common condition keys that are defined by Alibaba Cloud. For more information about the common condition keys, see Generic Condition Keyword.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
ActionsAPI operationAccess levelResource typeCondition keyAssociated operation
fc:ListLayersListLayerslist
All Resources
*
NoneNone
fc:PutFunctionAsyncInvokeConfigPutAsyncInvokeConfigcreate
All Resources
*
NoneNone
fc:GetConcurrencyConfigGetConcurrencyConfigget
All Resources
*
NoneNone
fc:GetLayerVersionGetLayerVersionget
All Resources
*
NoneNone
fc:DeleteCustomDomainDeleteCustomDomaindelete
CustomDomain
acs:fc:{#regionId}:{#accountId}:custom-domains/{#domainName}
NoneNone
fc:UpdateFunctionUpdateFunctionupdate
All Resources
*
NoneNone
fc:ListTagResourcesListTagResourceslist
All Resources
*
NoneNone
fc:DeleteLayerVersionDeleteLayerVersiondelete
All Resources
*
NoneNone
fc:CreateTriggerCreateTriggercreate
All Resources
*
NoneNone
fc:PutLayerACLPutLayerACLupdate
All Resources
*
NoneNone
fc:CreateAliasCreateAliascreate
All Resources
*
NoneNone
fc:GetFunctionGetFunctionget
All Resources
*
NoneNone
fc:GetAsyncTaskGetAsyncTaskget
All Resources
*
NoneNone
fc:DeleteProvisionConfigDeleteProvisionConfigdelete
All Resources
*
NoneNone
fc:DeleteTriggerDeleteTriggerdelete
All Resources
*
NoneNone
fc:GetFunctionCodeGetFunctionCodeget
All Resources
*
NoneNone
fc:GetTriggerGetTriggerget
All Resources
*
NoneNone
fc:DeleteVpcBindingDeleteVpcBindingdelete
All Resources
*
NoneNone
fc:ListTriggersListTriggerslist
All Resources
*
NoneNone
fc:ListProvisionConfigsListProvisionConfigslist
All Resources
*
NoneNone
fc:StopAsyncTaskStopAsyncTaskupdate
All Resources
*
NoneNone
fc:UpdateTriggerUpdateTriggerupdate
All Resources
*
NoneNone
fc:CreateVpcBindingCreateVpcBindingcreate
All Resources
*
NoneNone
fc:ListAliasesListAliaseslist
All Resources
*
NoneNone
fc:DeleteAliasDeleteAliasdelete
All Resources
*
NoneNone
fc:GetLayerVersionByArnGetLayerVersionByArnget
All Resources
*
NoneNone
fc:CreateFunctionCreateFunctioncreate
All Resources
*
NoneNone
fc:DeleteConcurrencyConfigDeleteConcurrencyConfigdelete
All Resources
*
NoneNone
fc:GetAliasGetAliasget
All Resources
*
NoneNone
fc:ListInstancesListInstanceslist
All Resources
*
NoneNone
fc:DeleteFunctionAsyncInvokeConfigDeleteAsyncInvokeConfigdelete
All Resources
*
NoneNone
fc:DeleteFunctionDeleteFunctiondelete
All Resources
*
NoneNone
fc:ListVpcBindingsListVpcBindingslist
All Resources
*
NoneNone
fc:GetFunctionAsyncInvokeConfigGetAsyncInvokeConfigget
All Resources
*
NoneNone
fc:UpdateAliasUpdateAliasupdate
All Resources
*
NoneNone
fc:PublishFunctionVersionPublishFunctionVersioncreate
All Resources
*
NoneNone
fc:ListFunctionAsyncInvokeConfigsListAsyncInvokeConfigslist
All Resources
*
NoneNone
fc:DeleteFunctionVersionDeleteFunctionVersiondelete
All Resources
*
NoneNone
fc:UpdateCustomDomainUpdateCustomDomainupdate
All Resources
*
NoneNone
fc:PutConcurrencyConfigPutConcurrencyConfigcreate
All Resources
*
NoneNone
fc:TagResourcesTagResourcescreate
All Resources
*
NoneNone
fc:GetCustomDomainGetCustomDomainget
All Resources
*
NoneNone
fc:ListConcurrencyConfigsListConcurrencyConfigslist
All Resources
*
NoneNone
fc:ListAsyncTasksListAsyncTaskslist
All Resources
*
NoneNone
fc:ListLayerVersionsListLayerVersionslist
All Resources
*
NoneNone
fc:PutProvisionConfigPutProvisionConfigcreate
All Resources
*
NoneNone
fc:InvokeFunctionInvokeFunctioncreate
All Resources
*
NoneNone
fc:ListCustomDomainsListCustomDomainslist
All Resources
*
NoneNone
fc:CreateLayerVersionCreateLayerVersioncreate
All Resources
*
NoneNone
fc:GetProvisionConfigGetProvisionConfigget
All Resources
*
NoneNone
fc:UntagResourcesUntagResourcesdelete
All Resources
*
NoneNone
fc:ListFunctionVersionsListFunctionVersionslist
All Resources
*
NoneNone
fc:ListFunctionsListFunctionslist
All Resources
*
NoneNone
fc:CreateCustomDomainCreateCustomDomaincreate
All Resources
*
NoneNone

Resource

FCV3 defines the values that you can use in the Resource. You can attach the policy to a RAM user or a RAM role so that the RAM user or the RAM role can perform a specific operation on a specific resource. The ARN is the unique identifier of the resource on Alibaba Cloud. Take note of the following items:
  • {#}indicates a variable. {#} must be replaced with an actual value. For example, {#ramcode} must be replaced with the actual code of an Alibaba Cloud service in RAM.
  • An asterisk (*) is used as a wildcard. Examples:
    • {#resourceType} is set to *, all resources are specified.
    • {#regionId} is set to *, all regions are specified.
    • {#accountId} is set to *, all Alibaba Cloud accounts are specified.
Resource typeARN
CustomDomainacs:fc:{#regionId}:{#accountId}:custom-domains/{#domainName}

Condition

FCV3 does not define service-specific condition keys. For more information about common condition keys that are defined by Alibaba Cloud, see Generic Condition Keyword.

What to do next

You can create a custom policy and attach the policy to a RAM user, RAM user group, or RAM role. For more information, see the following topics: