Updated on 2025-11-06 GMT+08:00

Image Management Service (IMS)

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see What Are the Differences in Access Control Between IAM and Organizations?.

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

  • The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
  • The Resource Type column indicates whether the action supports resource-level permissions.
    • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
    • If this column includes a resource type, you must specify a URN for the Resource element in your identity policy statements.
    • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

    For details about the resource types defined by IMS, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
    • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
    • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
    • If the Condition Key column of an action is empty (-), the action does not support any condition keys.

    For details about the condition keys defined by IMS, see Conditions.

  • The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for IMS.

Table 1 Supported Actions

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

ims:images:list

Viewing images

list

-

g:EnterpriseProjectId

-

ims:images:get

Viewing details about a specified image

read

image *

-

-

ims:images:create

Creating image metadata

write

-

-

ims:images:share

NOTE:

The action ims:images:share is not recommended. Instead, the following actions are recommended for sharing images:

  • ims:images:addMember
  • ims:images:deleteMember
  • ims:images:updateMemberStatus

Sharing images

permission_management

image *

-

ims:images:copyInRegion

Replicating images within a region

write

image *

ims:images:copy

ims:images:copyCrossRegion

Replicating images across regions

write

image *

ims:images:copy

ims:quotas:get

Querying the image quota

read

-

-

-

ims:images:upload

Uploading images

write

image *

-

-

ims:wholeImages:create

Creating full-ECS images

write

-

-

ims:images:export

Exporting images

read

image *

-

-

ims:dataImages:create

Creating data disk images from external image files

write

-

-

ims:serverImages:create

Creating images

write

-

-

ims:images:setTags

Updating image tags

tagging

image *

ims:images:update

ims:images:getTags

Querying image tags

read

-

ims:images:list

ims:images:deleteImage

Deleting images

write

image *

-

ims:images:update

ims:images:updateImage

Updating image information

write

image *

-

-

ims:images:listOsVersion

Querying OSs supported by images

list

-

-

ims:images:list

ims:images:getJob

Querying progresses of asynchronous tasks

read

-

-

ims:images:list

ims:images:import

Importing images

write

-

-

ims:images:setOrDeleteTags

Adding or deleting image tags in a batch

write

-

-

ims:images:updateMemberStatus

Updating the status of members who can use shared images

write

image *

g:RequestTag/<tag-key>

ims:images:share

ims:images:addMember

Adding a tenant that can use a shared image

write

image *

ims:images:share

ims:images:deleteMember

Deleting a tenant from the group where the members can use a shared image

write

image *

ims:images:share

ims:images:listImagesByTag

Querying images by tag

read

-

-

ims:images:list

ims:images:showImageTags

Querying tags of an image

read

image *

ims:images:list

ims:images:listImageTags

Querying project tags

list

-

-

-

An IMS API usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by IMS APIs

API

Action

Dependencies

GET /v2/cloudimages

ims:images:list

-

GET /v2/images/{image_id}

ims:images:get

-

POST /v2/images

ims:images:create

-

POST /v2/images/{image_id}/members

ims:images:share

ims:images:get

POST /v1/cloudimages/{image_id}/copy

ims:images:copyInRegion

ims:serverImages:create

POST /v1/cloudimages/{image_id}/cross_region_copy

ims:images:copyCrossRegion

-

GET /v1/cloudimages/quota

ims:quotas:get

-

PUT /v1/cloudimages/{image_id}/upload

PUT /v2/images/{image_id}/file

ims:images:upload

  • ims:images:get
  • ims:images:update

POST /v1/cloudimages/wholeimages/action

ims:wholeImages:create

-

POST /v1/cloudimages/{image_id}/file

ims:images:export

  • obs:object:GetObject
  • obs:object:PutObject
  • POST /v2/cloudimages/quickimport/action (required only for quickly importing a data disk image)
  • POST /v1/cloudimages/dataimages/action

ims:dataImages:create

-

  • PATCH /v2/cloudimages/{image_id} (required only for enterprise project migration)
  • POST /v2/cloudimages/action
  • OST /v2/cloudimages/quickimport/action (required only for quickly importing a system disk image)
  • POST /v1/cloudimages/{image_id}/copy (required only by enterprise project users)

ims:serverImages:create

-

PUT /v1/cloudimages/tags

ims:images:setTags

-

GET /v1/cloudimages/tags

ims:images:getTags

-

DELETE /v2/images/{image_id}

ims:images:deleteImage

-

  • PATCH /v2/cloudimages/{image_id}
  • PATCH /v2/images/{image_id}

ims:images:updateImage

-

GET /v1/cloudimages/os_version

ims:images:listOsVersion

-

GET /v1/cloudimages/job/{job_id}

ims:images:getJob

-

POST /v2/cloudimages/quickimport/action

ims:images:import

  • ims:dataImages:create
  • ims:serverImages:create

POST /v2/{project_id}/images/{image_id}/tags/action

ims:images:setOrDeleteTags

  • ims:images:setTags
  • ims:images:deleteTags
  • PUT /v1/cloudimages/members
  • PUT /v2/images/{image_id}/members/{member_id}

ims:images:updateMemberStatus

-

POST /v1/cloudimages/members

ims:images:addMember

-

DELETE /v1/cloudimages/members

ims:images:deleteMember

-

POST /v2/{project_id}/images/resource_instances/action

ims:images:listImagesByTag

-

GET /v2/{project_id}/images/{image_id}/tags

ims:images:showImageTags

-

GET /v2/{project_id}/images/tags

ims:images:listImageTags

-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, a resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to the resource. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can specify in identity policy statements for IMS.

Table 3 Resource types supported by IMS

Resource Type

URN

Image

ims:<region>:<account-id>:image:<image-id>

  • <region> indicates the region where a user is authorized to perform operations.
  • <account-id> indicates the ID of an authorized user account. Obtain an account ID as instructed in API Credentials.
  • <image-id> indicates the ID of the image on which a user is authorized to perform operations.

You can use a wildcard (*) in URN to indicate all resources.

Conditions

A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.

  • The condition key that you specify can be a global or service-specific condition key.
    • Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, IAM automatically obtains such information and authenticates users. For details, see Global Condition Keys.
    • Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, ims:) only apply to operations of IMS. For details, see Table 4.
    • The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
  • A condition operator, condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see Condition operators.

The following table lists the condition keys that you can define in identity policies for IMS. You can include these condition keys to specify conditions for when your identity policy is in effect.

Table 4 Service-specific condition keys supported by IMS

Condition Key

Value Type

Single-valued/Multivalued

Description

ims:TargetOrgPaths

string

Multivalued

Filters access based on the Organizations Path of the specified sharing account.

ims:Encrypted

boolean

Single-valued

Controls operations such as image import and replication based on whether images are encrypted.

ims:TargetBucketOrgPaths

string

Multivalued

Filters access based on the Organizations Path of the specified destination bucket owner account.

ims:OriginBucketOrgPaths

string

Multivalued

Filters access based on the Organizations Path of the specified source bucket owner account.

ims:SourceAvailabilityZone

string

Multivalued

Filters access based on the specified AZ.

ims:InstanceId

string

Single-valued

Controls full-ECS image creation based on the specified ECS ID.

ims:VaultId

string

Single-valued

Controls creation and cross-region replication of full-ECS images based on the specified vault ID.

ims:VolumeId

string

Multivalued

Controls image creation based on the specified volume ID.

ims:BackupId

string

Single-valued

Controls full-ECS image creation based on the specified backup ID.

ims:Region

string

Single-valued

Controls cross-region replication based on the specified destination region.