Help Center/ Organizations/ User Guide/ Managing SCPs/ Actions Supported by SCP-based Authorization/ Migration/ Object Storage Migration Service (OMS)
Updated on 2024-07-05 GMT+08:00
Share

Object Storage Migration Service (OMS)

The Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

This topic describes the elements used by Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

  • 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 SCP.
  • 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 SCP statements.
    • If this column includes a resource type, you must specify the URN in the Resource element of your 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 OMS, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an SCP 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 is empty (-) for an action, the action does not support any condition keys.

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

The following table lists the actions that you can define in SCP statements for OMS.

Table 1 Actions supported by OMS

Action

Description

Access Level

Resource Type (*: required)

Condition Key

oms:task:list

Grants permission to list migration tasks.

list

task

-

oms:task:create

Grants permission to create a migration task.

write

task

-

oms:task:get

Grants permission to query details about a migration task.

read

task

-

oms:task:delete

Grants permission to delete a migration task.

write

task

-

oms:task:update

Grants permission to update a migration task.

write

task

-

oms:synctask:list

Grants permission to list synchronization tasks.

list

synctask

-

oms:synctask:create

Grants permission to create a synchronization task.

write

synctask

-

oms:synctask:get

Grants permission to query details about a synchronization task.

read

synctask

-

oms:synctask:delete

Grants permission to delete a synchronization task.

write

synctask

-

oms:synctask:statistics

Grants permission to query statistics about a synchronization task.

read

synctask

-

oms:synctask:update

Grants permission to update a synchronization task.

write

synctask

-

oms:synctask:createEvent

Grants permission to create a synchronization event.

write

synctask

-

oms:taskgroup:create

Grants permission to create a migration task group.

write

taskgroup

-

oms:taskgroup:list

Grants permission to list migration task groups.

list

taskgroup

-

oms:taskgroup:get

Grants permission to query details about a migration task group.

read

taskgroup

-

oms:taskgroup:delete

Grants permission to delete a migration task group.

write

taskgroup

-

oms:taskgroup:update

Grants permission to update a migration task group.

write

taskgroup

-

oms::listObjects

Grants permission to list objects in a bucket.

list

-

-

oms::checkCdnInfo

Grants permission to check the connectivity between a bucket and CDN.

read

-

-

oms::listBuckets

Grants permission to list buckets.

list

-

-

oms::listBucketRegions

Grants permission to query the region of a bucket.

list

-

-

oms::checkBucketPrefix

Grants permission to check whether a bucket has objects with a specified prefix.

read

-

-

oms::listCloudRegions

Grants permission to query regions supported for a cloud vendor.

list

-

-

oms::listCloudTypes

Grants permission to list supported cloud vendors.

list

-

-

Each API of OMS usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by OMS APIs

API

Action

Dependencies

GET /v2/{project_id}/tasks

oms:task:list

-

POST /v2/{project_id}/tasks

oms:task:create

-

GET /v2/{project_id}/tasks/{task_id}

oms:task:get

-

DELETE /v2/{project_id}/tasks/{task_id}

oms:task:delete

-

POST /v2/{project_id}/tasks/{task_id}/stop

oms:task:update

-

POST /v2/{project_id}/tasks/{task_id}/start

oms:task:update

-

PUT /v2/{project_id}/tasks/{task_id}/bandwidth-policy

oms:task:update

-

PUT /v2/{project_id}/tasks/{task_id}/access-keys

oms:task:update

-

GET /v2/{project_id}/sync-tasks

oms:synctask:list

-

POST /v2/{project_id}/sync-tasks

oms:synctask:create

-

GET /v2/{project_id}/sync-tasks/{sync_task_id}

oms:synctask:get

-

DELETE /v2/{project_id}/sync-tasks/{sync_task_id}

oms:synctask:delete

-

GET /v2/{project_id}/sync-tasks/{sync_task_id}/statistics

oms:synctask:statistics

-

POST /v2/{project_id}/sync-tasks/{sync_task_id}/stop

oms:synctask:update

-

POST /v2/{project_id}/sync-tasks/{sync_task_id}/start

oms:synctask:update

-

POST /v2/{project_id}/sync-tasks/{sync_task_id}/events

oms:synctask:createEvent

-

POST /v2/{project_id}/taskgroups

oms:taskgroup:create

-

GET /v2/{project_id}/taskgroups

oms:taskgroup:list

-

GET /v2/{project_id}/taskgroups/{group_id}

oms:taskgroup:get

-

DELETE /v2/{project_id}/taskgroups/{group_id}

oms:taskgroup:delete

-

PUT /v2/{project_id}/taskgroups/{group_id}/stop

oms:taskgroup:update

-

PUT /v2/{project_id}/taskgroups/{group_id}/start

oms:taskgroup:update

-

PUT /v2/{project_id}/taskgroups/{group_id}/retry

oms:taskgroup:update

-

PUT /v2/{project_id}/taskgroups/{group_id}/update

oms:taskgroup:update

-

POST /v2/{project_id}/objectstorage/buckets/objects

oms::listObjects

-

POST /v2/{project_id}/objectstorage/buckets/cdn-info

oms::checkCdnInfo

-

POST /v2/{project_id}/objectstorage/buckets

oms::listBuckets

-

POST /v2/{project_id}/objectstorage/buckets/regions

oms::listBucketRegions

-

POST /v2/{project_id}/objectstorage/buckets/prefix

oms::checkBucketPrefix

-

GET /v2/{project_id}/objectstorage/data-center

oms::listCloudRegions

-

GET /v2/{project_id}/objectstorage/cloud-type

oms::listCloudTypes

-

Resources

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

The following table lists the resource types that you can define in SCP statements for OMS.

Table 3 Resource types supported by OMS

Resource Type

URN

Task

oms:<region>:<account-id>:task:*

oms:<region>:<account-id>:task:<task-id>

SyncTask

oms:<region>:<account-id>:synctask:*

oms:<region>:<account-id>:synctask:<synctask-id>

TaskGroup

oms:<region>:<account-id>:taskgroup:*

oms:<region>:<account-id>:taskgroup:*

Currently, synchronization task APIs are available only in CN South-Guangzhou-InvitationOnly, CN North-Beijing4, and CN East-Shanghai1.

Conditions

OMS does not support service-specific condition keys in an SCP.

It can only use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Migration