RAM authorization

更新时间:
复制 MD 格式

Resource Access Management (RAM) is a service provided by Alibaba Cloud to manage user identities and resource access permissions. Using RAM helps you avoid sharing your Alibaba Cloud account keys with other users and allows you to grant users the least privilege access. RAM uses permission policies to define authorizations. This topic describes the general structure of a RAM policy, and the policy statement elements (Action, Resource, and Condition) defined by Hologres for RAM permission policies. The RAM code (RamCode) for Hologres is hologram , and the supported authorization granularity is RESOURCE .

General structure of a policy

Permission policies support JSON format with the following general structure:

{
  "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:

  • Version: Specifies the policy version number. It is fixed at 1.

  • Statement:

    • Effect: Specifies the authorization result. Valid values: Allow and Deny.

    • Action: Specifies one or more operations that are allowed or denied.

    • Resource: Specifies the specific objects affected by the operations. You can use Alibaba Cloud Resource Names (ARNs) to describe specific resources.

    • Condition: Specifies the conditions for the authorization to take effect. This field is optional.

      • Condition operator: Specifies the conditional operators. Different types of conditions support different conditional operators.

      • Condition_key: Specifies the condition keys.

      • Condition_value: Specifies the condition values.

Action

The following table lists the actions defined by Hologres. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that support authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding ARN in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys that are applicable across all RAM-integrated services. For more information, see Common condition keys.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

API

Access level

Resource type

Condition key

Dependent action

hologram:ListDatabases ListDatabases list

*All Resource

*

None None
hologram:UpdateInstanceName UpdateInstanceName update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ListInstances ListInstances list

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/*

None None
hologram:RebalanceHoloWarehouse RebalanceHoloWarehouse update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:GrantDatabasePermission GrantDatabasePermission update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:EnableSSL EnableSSL none

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:StopInstance StopInstance update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:CreateHoloWarehouse CreateHoloWarehouse create

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:CreateUser CreateUser create

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:RestartHoloWarehouse RestartHoloWarehouse update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:GrantTablePermission GrantTablePermission update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:UpdateInstanceNetworkType UpdateInstanceNetworkType update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:GetCertificateAttribute GetCertificateAttribute get

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:SuspendHoloWarehouse SuspendHoloWarehouse update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:DisableHiveAccess DisableHiveAccess update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ResumeInstance ResumeInstance update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ListWarehouses ListWarehouses list

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ChangeResourceGroup ChangeResourceGroup update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:DeleteInstance DeleteInstance delete

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:GetWarehouseDetail GetWarehouseDetail get

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:CreateInstance CreateInstance create

*All Resource

*

None None
hologram:RenewSSLCertificate RenewSSLCertificate none

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ScaleInstance ScaleInstance update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:EnableHiveAccess EnableHiveAccess update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ListBackupData ListBackupData list

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:DeleteHoloWarehouse DeleteHoloWarehouse delete

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:RenameHoloWarehouse RenameHoloWarehouse update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:RestartInstance RestartInstance update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:GetInstance GetInstance get

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:DropUser DropUser delete

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#instanceId}

None None
hologram:ScaleHoloWarehouse ScaleHoloWarehouse update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:DisableSSL DisableSSL none

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:RenewInstance RenewInstance update

*All Resource

*

None None
hologram:GrantSchemaPermission GrantSchemaPermission list

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:ResumeHoloWarehouse ResumeHoloWarehouse update

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None
hologram:GetRootCertificate GetRootCertificate none

*Instance

acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}

None None

Resource

The following table lists the resources defined by Hologres. Specify them in the Resource element of RAM policy statements to grant permissions for specific operations. They are uniquely identified by ARNs. Format: acs:{#ramcode}:{#regionId}:{#accountId}:{#resourceType}:

  • acs: The initialism of Alibaba Cloud service, which indicates the public cloud of Alibaba Cloud.

  • {#ramcode}: The code used in RAM to indicate an Alibaba Cloud service.

  • {#regionId}: The region ID. If the resource covers all regions, set it to an asterisk (*).

  • {#accountId}: The ID of the Alibaba Cloud account. If the resource covers all Alibaba Cloud accounts, set it to an asterisk (*).

  • {#resourceType}: The service-defined resource identifier. It supports a hierarchical structure, which is similar to a file path. If the statement covers global resources, set it to an asterisk (*).

Resource type

ARN

Instance
  • acs:hologram:*:{#accountId}:instance/*
  • acs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}
  • acs:hologram:{#regionId}:{#accountId}:instance/*
  • acs:hologram:*:{#accountId}:instance/{#InstanceId}

Condition

Hologres does not define product-level condition keys. However, you can use Alibaba Cloud common condition keys for access control. For more information, see Common condition keys.

How to create custom RAM policies?

You can create custom policies and grant them to RAM users, RAM user groups, or RAM roles. For instructions, see: