Updated on 2024-04-09 GMT+08:00

ServiceStage

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 section describes the elements used by IAM custom identity policies and 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 identity policy 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 ServiceStage, 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 ServiceStage, see Conditions.

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

Table 1 Actions supported by ServiceStage

Action

Description

Access Level

Resource Type

Condition Key

servicestage:app:getApplication

Querying an application

read

app

  • g:EnterpriseProjectId
  • g:ResourceTag

servicestage:app:createApplication

Creating an application

write

app

  • g:EnterpriseProjectId
  • g:RequestTag
  • g:TagKeys

servicestage:app:modifyApplication

Updating an application

write

app

  • g:EnterpriseProjectId
  • g:ResourceTag
  • g:RequestTag
  • g:TagKeys

servicestage:app:deleteApplication

Deleting an application

write

app

  • g:EnterpriseProjectId
  • g:ResourceTag

servicestage:app:listApplication

Querying the application list

list

-

-

servicestage:app:getConfiguration

Querying application configuration

read

app

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:app:deleteConfiguration

Deleting application configuration

write

app

  • g:EnterpriseProjectId
  • g:ResourceTag

servicestage:app:modifyConfiguration

Updating application configuration

write

app

  • g:EnterpriseProjectId
  • g:ResourceTag

servicestage:app:getComponent

Querying an application component

read

app

  • g:EnterpriseProjectId
  • g:ResourceTag

servicestage:app:createComponent

Creating an application component

write

app

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:app:modifyComponent

Updating an application component

write

app

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:app:deleteComponent

Deleting an application component

write

app

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:app:listComponent

Querying the application component list

list

-

-

servicestage:environment:create

Creating an environment

write

environment

  • g:EnterpriseProjectId
  • g:RequestTag
  • g:TagKeys

servicestage:environment:get

Querying an environment

read

environment

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:environment:list

Querying the environment list

list

-

-

servicestage:environment:modify

Updating an environment

write

environment

  • g:ResourceTag
  • g:EnterpriseProjectId
  • g:RequestTag
  • g:TagKeys

servicestage:environment:delete

Deleting an environment

write

environment

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:environment:tag

(TMS users) Creating an environment tag

tagging

environment

  • g:ResourceTag
  • g:EnterpriseProjectId
  • g:RequestTag
  • g:TagKeys

servicestage:app:tag

(TMS users) Creating an application tag

tagging

app

  • g:ResourceTag
  • g:EnterpriseProjectId
  • g:RequestTag
  • g:TagKeys

servicestage:environment:listResourcesByTag

(TMS users) Querying environments by tag

read

environment

  • g:RequestTag
  • g:TagKeys

servicestage:app:listResourcesByTag

(TMS users) Querying applications by tag

read

app

  • g:RequestTag
  • g:TagKeys

servicestage:environment:unTagResource

(TMS users) Deleting an environment tag

tagging

environment

  • g:ResourceTag
  • g:RequestTag
  • g:EnterpriseProjectId
  • g:TagKeys

servicestage:app:unTagResource

(TMS users) Deleting an application tag

tagging

app

  • g:ResourceTag
  • g:EnterpriseProjectId
  • g:RequestTag
  • g:TagKeys

servicestage:environment:listTags

(TMS users) Querying the environment tag list

read

-

-

servicestage:app:listTags

(TMS users) Querying the application tag list

read

-

-

servicestage:pipeline:get

Querying a pipeline

read

pipeline

-

servicestage:pipeline:create

Creating a pipeline

write

pipeline

-

servicestage:pipeline:modify

Updating a pipeline

write

pipeline

-

servicestage:pipeline:delete

Deleting a pipeline

write

pipeline

-

servicestage:pipeline:list

Querying the pipeline list

list

-

-

servicestage:assembling:runtimeList

Querying the technology stack list

read

-

-

servicestage:assembling:getInfo

Querying a build task

list

-

-

servicestage:assembling:create

Creating a build task

write

assembling

-

servicestage:assembling:modify

Updating a build task

write

assembling

-

servicestage:assembling:delete

Deleting a build task

write

assembling

-

servicestage:assembling:list

Querying the build task list

list

-

-

servicestage:repositoryAuth:list

Obtaining the repository authorization list

list

-

-

servicestage:repositoryAuth:get

Obtaining repository authorization

read

repositoryAuth

-

servicestage:repositoryAuth:create

Creating repository authorization

write

repositoryAuth

-

servicestage:repositoryAuth:delete

Deleting repository authorization

write

repositoryAuth

-

servicestage:environment:listTagsForResource

(EPS users) Querying the environment tag list

read

environment

  • g:ResourceTag
  • g:EnterpriseProjectId

servicestage:app:listTagsForResource

(EPS users) Querying the application tag list

read

app

  • g:ResourceTag
  • g:EnterpriseProjectId

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

Table 2 Actions and dependencies supported by ServiceStage APIs

API

Action

Dependencies

GET /v2/{project_id}/cas/metadata/runtimes

servicestage:app:listApplication

-

GET /v2/{project_id}/cas/metadata/flavors

servicestage:app:listApplication

-

POST /v2/{project_id}/cas/environments

servicestage:environment:create

-

GET /v2/{project_id}/cas/environments

servicestage:environment:list

-

PUT /v2/{project_id}/cas/environments/{environment_id}

servicestage:environment:modify

-

DELETE /v2/{project_id}/cas/environments/{environment_id}

servicestage:environment:delete

-

GET /v2/{project_id}/cas/environments/{environment_id}

servicestage:environment:get

-

PATCH /v2/{project_id}/cas/environments/{environment_id}/resources

servicestage:environment:modify

-

POST /v2/{project_id}/cas/applications

servicestage:app:createApplication

-

GET /v2/{project_id}/cas/applications

servicestage:app:listApplication

-

PUT /v2/{project_id}/cas/applications/{application_id}

servicestage:app:modifyApplication

-

DELETE /v2/{project_id}/cas/applications/{application_id}

servicestage:app:deleteApplication

-

GET /v2/{project_id}/cas/applications/{application_id}

servicestage:app:getApplication

-

PUT /v2/{project_id}/cas/applications/{application_id}/configuration

servicestage:app:modifyConfiguration

-

DELETE /v2/{project_id}/cas/applications/{application_id}/configuration

servicestage:app:deleteConfiguration

-

GET /v2/{project_id}/cas/applications/{application_id}/configuration

servicestage:app:getConfiguration

-

POST /v2/{project_id}/cas/applications/{application_id}/components

servicestage:app:createComponent

servicestage:assembling:getInfo

servicestage:assembling:create

GET /v2/{project_id}/cas/applications/{application_id}/components

servicestage:app:listComponent

-

PUT /v2/{project_id}/cas/applications/{application_id}/components/{component_id}

servicestage:app:modifyComponent

-

DELETE /v2/{project_id}/cas/applications/{application_id}/components/{component_id}

servicestage:app:deleteComponent

-

GET /v2/{project_id}/cas/applications/{application_id}/components/{component_id}

servicestage:app:getComponent

-

POST /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances

servicestage:app:createComponent

servicestage:assembling:getInfo

servicestage:assembling:create

GET /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances

servicestage:app:listComponent

-

POST /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances/{instance_id}/action

servicestage:app:modifyComponent

-

PUT /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances/{instance_id}

servicestage:app:modifyComponent

-

DELETE /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances/{instance_id}

servicestage:app:deleteComponent

-

GET /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances/{instance_id}

servicestage:app:getComponent

-

GET /v2/{project_id}/cas/applications/{application_id}/components/{component_id}/instances/{instance_id}/snapshots

servicestage:app:getComponent

-

GET /v2/{project_id}/cas/jobs/{job_id}

servicestage:app:listApplication

-

POST /v3/{project_id}/cas/environments

servicestage:environment:create

-

GET /v3/{project_id}/cas/environments

servicestage:environment:list

-

PUT /v3/{project_id}/cas/environments/{environment_id}

servicestage:environment:modify

-

DELETE /v3/{project_id}/cas/environments/{environment_id}

servicestage:environment:delete

-

GET /v3/{project_id}/cas/environments/{environment_id}

servicestage:environment:get

-

PUT /v3/{project_id}/cas/environments/{environment_id}/resources

servicestage:environment:modify

-

GET /v3/{project_id}/cas/environments/{environment_id}/resources

servicestage:environment:list

-

POST /v3/{project_id}/cas/applications

servicestage:app:createApplication

-

GET /v3/{project_id}/cas/applications

servicestage:app:listApplication

-

PUT /v3/{project_id}/cas/applications/{application_id}

servicestage:app:modifyApplication

-

GET /v3/{project_id}/cas/applications/{application_id}

servicestage:app:getApplication

-

GET /v3/{project_id}/cas/applications/{application_id}/configuration

servicestage:app:getConfiguration

-

PUT /v3/{project_id}/cas/applications/{application_id}/configuration

servicestage:app:modifyConfiguration

-

DELETE /v3/{project_id}/cas/applications/{application_id}/configuration

servicestage:app:deleteConfiguration

-

POST /v3/{project_id}/cas/applications/{application_id}/components

servicestage:app:createComponent

servicestage:assembling:getInfo

servicestage:assembling:create

GET /v3/{project_id}/cas/applications/{application_id}/components

servicestage:app:listComponent

-

GET /v3/{project_id}/cas/components

servicestage:app:listComponent

-

PUT /v3/{project_id}/cas/applications/{application_id}/components/{component_id}

servicestage:app:modifyComponent

-

DELETE /v3/{project_id}/cas/applications/{application_id}/components/{component_id}

servicestage:app:deleteComponent

-

GET /v3/{project_id}/cas/applications/{application_id}/components/{component_id}

servicestage:app:getComponent

-

POST /v3/{project_id}/cas/applications/{application_id}/components/{component_id}/action

servicestage:app:modifyComponent

-

GET /v3/{project_id}/cas/applications/{application_id}/components/{component_id}/records

servicestage:app:listComponent

-

GET /v3/{project_id}/cas/runtimestacks

servicestage:app:listApplication

-

GET /v1/{project_id}/git/auths

servicestage:repositoryAuth:list

-

GET /v1/{project_id}/git/auths/{repo_type}/redirect

servicestage:repositoryAuth:get

-

POST /v1/{project_id}/git/auths/{repo_type}/oauth

servicestage:repositoryAuth:create

-

POST /v1/{project_id}/git/auths/{repo_type}/personal

servicestage:repositoryAuth:create

-

POST /v1/{project_id}/git/auths/{repo_type}/password

servicestage:repositoryAuth:create

-

DELETE /v1/{project_id}/git/auths/{name}

servicestage:repositoryAuth:delete

-

GET /v2/{project_id}/servicestage-environment/{environment_id}/tags

servicestage:environment:listTagsForResource

-

GET /v2/{project_id}/servicestage-application/{app_id}/tags

servicestage:app:listTagsForResource

-

Resources

A resource type indicates the resources that an SCP 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 ServiceStage.

Table 3 Resource types supported by ServiceStage

Resource Type

URN

app

servicestage:<region>:<account-id>:app:<app-id>

environment

servicestage:<region>:<account-id>:environment:<environment-id>

pipeline

servicestage:<region>:<account-id>:pipeline:<pipeline-id>

assembling

servicestage:<region>:<account-id>:assembling:<assembling-id>

repositoryAuth

servicestage:<region>:<account-id>:repositoryAuth:<repositoryAuth-id>

Conditions

ServiceStage does not support service-specific condition keys in SCPs.

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