Actions Supported by Identity Policy-based Authorization
IAM provides system-defined identity policies to define typical cloud service permissions. 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 also 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 How IAM Is Different from Organizations for Access Control?.
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 edit an IAM custom identity policy, see Creating a Custom Identity Policy.
- For details about how to use these elements to edit a custom SCP, see Creating an SCP.
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 the URN in the Resource element of 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 SWR, 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 is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by SWR, 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 SWR.
| Action | Description | Access Level | Resource Type (*: required) | Condition Key | Alias |
|---|---|---|---|---|---|
| swr:namespace:createNamespace | Grants permission to create namespace for shared registry. | Write | namespace * | - | - |
| swr:namespace:deleteNamespace | Grants permission to delete namespace for shared registry. | Write | namespace * | - | - |
| swr:namespace:listNamespaces | Grants permission to list namespaces for shared registry. | List | namespace * | - | - |
| swr:namespace:getNamespace | Grants permission to get namespace for shared registry. | Read | namespace * | - | - |
| swr:repo:createRepo | Grants permission to create repository for shared registry. | Write | repo * | - | - |
| - | |||||
| swr:repo:deleteRepo | Grants permission to delete repository for shared registry. | Write | repo * | - | - |
| swr:repo:listRepos | Grants permission to list repositories for shared registry. | List | repo * | - | - |
| swr:repo:listSharedRepos | Grants permission to list shared repositories for shared registry. | List | repo * | - | - |
| swr:repo:getRepo | Grants permission to get repository for shared registry. | Read | repo * | - | - |
| swr:repo:updateRepo | Grants permission to update repository for shared registry. | Write | repo * | - | - |
| - | |||||
| swr:repo:deleteRepoTag | Grants permission to delete tag of repository for shared registry. | Write | repo * | - | - |
| swr:repo:createRepoTag | Grants permission to create tag of repository for shared registry. | Write | repo * | - | - |
| swr:repo:listRepoTags | Grants permission to list tags of repository for shared registry. | List | repo * | - | - |
| swr:repo:createRepoDomain | Grants permission to create access domain of repository for shared registry. | Permission_management | repo * | - | - |
| - | |||||
| swr:repo:deleteRepoDomain | Grants permission to delete access domain of repository for shared registry. | Permission_management | repo * | - | - |
| swr:repo:listRepoDomains | Grants permission to list access domains of repository for shared registry. | List | repo * | - | - |
| swr:repo:getRepoDomain | Grants permission to get access domain of repository for shared registry. | Read | repo * | - | - |
| swr:repo:updateRepoDomain | Grants permission to update access domain of repository for shared registry. | Permission_management | repo * | - | - |
| swr:repo:createRepoShare | Grants permission to create repo share rule of repository for shared registry. | Permission_management | repo * | - | - |
| - | |||||
| swr:repo:deleteRepoShare | Grants permission to delete repo share rule of repository for shared registry. | Permission_management | repo * | - | - |
| swr:repo:listRepoShares | Grants permission to list repo share rules of repository for shared registry. | List | repo * | - | - |
| swr:repo:getRepoShare | Grants permission to get repo share rule of repository for shared registry. | Read | repo * | - | - |
| swr:repo:updateRepoShare | Grants permission to update repo share rule of repository for shared registry. | Permission_management | repo * | - | - |
| swr:repo:createAutoSyncRepoJob | Grants permission to create auto sync repository job for shared registry. | Write | repo * | - | - |
| - | |||||
| swr:repo:createManualSyncRepoJob | Grants permission to create manual sync repository job for shared registry. | Write | repo * | - | - |
| - | |||||
| swr:repo:deleteAutoSyncRepoJob | Grants permission to delete auto sync repository job for shared registry. | Write | repo * | - | - |
| swr:repo:listAutoSyncRepoJobs | Grants permission to list auto sync repository jobs for shared registry. | List | repo * | - | - |
| swr:repo:getSyncRepoJobInfo | Grants permission to get auto sync repository job info for shared registry. | Read | repo * | - | - |
| swr:repo:createTrigger | Grants permission to create trigger for shared registry. | Write | repo * | - | - |
| swr:repo:deleteTrigger | Grants permission to delete trigger for shared registry. | Write | repo * | - | - |
| swr:repo:listTriggers | Grants permission to list triggers for shared registry. | List | repo * | - | - |
| swr:repo:getTrigger | Grants permission to get trigger for shared registry. | Read | repo * | - | - |
| swr:repo:updateTrigger | Grants permission to update trigger for shared registry. | Write | repo * | - | - |
| swr:repo:createRetention | Grants permission to create retention for shared registry. | Write | repo * | - | - |
| swr:repo:deleteRetention | Grants permission to delete retention for shared registry. | Write | repo * | - | - |
| swr:repo:listRetentionHistories | Grants permission to list retention histories for shared registry. | List | repo * | - | - |
| swr:repo:listRetentions | Grants permission to list retentions for shared registry. | List | repo * | - | - |
| swr:repo:getRetention | Grants permission to get retention for shared registry. | Read | repo * | - | - |
| swr:repo:updateRetention | Grants permission to update retention for shared registry. | Write | repo * | - | - |
| swr::createLoginSecret | Grants permission to create login secret for shared registry. | Write | - | - | - |
| swr::createAuthorizationToken | Grants permission to create a new temporary access credential for shared registry. | Write | - | - | - |
| swr::listQuotas | Grants permission to list quotas for shared registry. | List | - | - | - |
| swr::getDomainOverview | Grants permission to get overview of domain for shared registry. | Read | - | - | - |
| swr::getDomainResourceReports | Grants permission to get down flow reports of domain for shared registry. | Read | - | - | - |
| swr:namespace:multipartUpload | Grants permission to multipart upload for shared registry. | Write | namespace * | - | - |
| swr:namespace:createNamespaceAccess | Grants permission to create namespace access for shared registry. | Permission_management | namespace * | - | - |
| swr:namespace:deleteNamespaceAccess | Grants permission to delete namespace access for shared registry. | Permission_management | namespace * | - | - |
| swr:namespace:getNamespaceAccess | Grants permission to get namespace access for shared registry. | Read | namespace * | - | - |
| swr:namespace:updateNamespaceAccess | Grants permission to update namespace access for shared registry. | Permission_management | namespace * | - | - |
| swr:repo:createRepoAccess | Grants permission to create repository access for shared registry. | Permission_management | repo * | - | - |
| swr:repo:deleteRepoAccess | Grants permission to delete repository access for shared registry. | Permission_management | repo * | - | - |
| swr:repo:getRepoAccess | Grants permission to get repository access for shared registry. | Read | repo * | - | - |
| swr:repo:updateRepoAccess | Grants permission to update repository access for shared registry. | Permission_management | repo * | - | - |
| swr:repo:upload | Grants permission to upload repository for shared registry. | Write | repo * | - | - |
| - | |||||
| swr:repo:download | Grants permission to download repository for shared registry. | Read | repo * | - | |
| - | |||||
| swr:repo:getRepoTag | Grants permission to query tag of repository for shared registry. | Read | repo * | - | - |
| swr:repo:listAccessories | Grants permission to list accessories of image tag for shared registry. | List | repo * | - | - |
| swr:repo:listReferences | Grants permission to list reference tags of cosign signature image for shared registry. | List | repo * | - | - |
| swr:repo:getRepoTagConfig | Grants permission to query image config for basic registry. | Read | repo * | - | - |
Each API of SWR usually supports one or more actions. Table 2 lists the supported actions and dependencies.
Resources
A resource type (Resource) defines the resources on which an identity policy takes effect. In Table 3, if a specific operation has an associated resource type, then in the identity policy statement containing that operation, the policy will only take effect on the specified resource when the corresponding resource URN is provided. If no resource URN is specified, the policy will apply to all resources under the designated resource type. If no resource type is defined, the default value of Resource is *, meaning the policy applies to all resources. In addition, you can set conditions in the identity policy to further refine and restrict the resource type.
The following table lists the resource types that you can define in identity policy statements for SWR.
Conditions
Condition Key Overview
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 condition key or a 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, the system 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, swr) apply only to operations of the xx service. 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 operators.
Service-specific condition keys supported by SWR
The following table lists the condition keys that you can define in identity policies for SWR. You can include these condition keys to specify conditions for when your identity policy is in effect.
| Service-specific Condition Key | Type | Single-valued/Multivalued | Description |
|---|---|---|---|
| swr:TargetOrgPath | string | Single-valued | Filters access by destination's OrgPath. |
| swr:TargetOrgId | string | Single-valued | Filters access by destination's OrgId. |
| swr:TargetAccountId | string | Single-valued | Filters access by destination's AccountId. |
| swr:AllowPublicAccess | boolean | Single-valued | Filters access by the repos that can be set to public. |
| swr:TargetRegion | string | Single-valued | Filters access by target region. |
| swr:AllowCredentialType | string | Single-valued | Filters access by the credential type. |
| swr:RepositoryIsPublic | boolean | Single-valued | Filters access by public repositories. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
