1. Image pull command
+If you need to grant your enterprise personnel permission to access your SWR resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your cloud resources.
+
With IAM, you can create IAM users and grant them permission to access only specific resources. For example, if you want some software developers in your enterprise to be able to use SWR resources but not be able to delete the resources or perform any other high-risk operations, you can create IAM users and grant permission to use SWR resources but not permission to delete them.
+
If your cloud account does not require individual IAM users for permissions management, you can skip this section.
+
IAM is a free service. You only pay for the resources in your account.
+
SWR Permissions
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and then attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
+
SWR is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for SWR resources in the selected projects. When accessing SWR, the users need to switch to the authorized region.
+
You can grant permissions by using roles and policies.
+
- Roles: A coarse-grained authorization strategy that defines permissions by job responsibility. Only a limited number of service-level roles are available for authorization. Cloud services often depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant IAM users only permission to manage a certain type of ECSs.
+
Table 1 and Table 2 describe all system-defined policies and roles of SWR.
+
+
Table 1 System-defined policies of SWR (recommended)Policy
+ |
+Description
+ |
+Type
+ |
+
|---|
+
+SWR FullAccess
+ |
+Full permissions for SWR.
+ |
+System-defined policy
+ |
+
+SWR OperateAccess
+ |
+Operation permissions for SWR.
+ |
+System-defined policy
+ |
+
+SWR ReadOnlyAccess
+ |
+Read-only permission for SWR.
+ |
+System-defined policy
+ |
+
+
+
+
+
+
Table 2 System-defined roles of SWRRole
+ |
+Description
+ |
+Type
+ |
+
|---|
+
+SWR Admin
+ |
+Administrator permissions for SWR. Users with this role can perform all operations on SWR resources.
+ |
+System-defined role
+ |
+
+Tenant Administrator
+ |
+Administrator permissions for all services except IAM. Users with this role can perform all operations on SWR resources.
+ |
+System-defined role
+ |
+
+ServiceStage Developer
+ |
+ServiceStage developer permissions. For example, users with this role can pull images.
+ |
+System-defined role
+ |
+
+
+
+
+
Table 3 lists the common operations supported by system-defined permissions for SWR.
+
+
Table 3 Common operations supported by system-defined permissionsOperation
+ |
+SWR FullAccess
+ |
+SWR OperateAccess
+ |
+SWR ReadOnlyAccess
+ |
+SWR Administrator
+ |
+Tenant Administrator
+ |
+
|---|
+
+Uploading/Pushing an Image
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Downloading/Pulling an Image
+ |
+√
+ |
+√
+ |
+√
+ |
+√
+ |
+√
+ |
+
+Adding a trigger
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Modifying an image
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Sharing an image
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Assigning permissions
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Deleting an image or a tag
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Creating an organization
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+Deleting an organization
+ |
+√
+ |
+√
+ |
+x
+ |
+√
+ |
+√
+ |
+
+
+
+
+
+
If you need to assign different permissions to employees in your enterprise to access your SWR resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, enabling secure access to your cloud resources.
-
With IAM, you can use your account to create IAM users, and assign permissions to the users to control their access to specific cloud resources. For example, some software developers in your enterprise need to use SWR resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using SWR resources.
-
If your account does not require individual IAM users for permissions management, skip this section.
-
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
-
By default, new IAM users do not have any permissions granted. You need to add them to one or more groups and attach permissions policies or roles to these groups. In this way, the users can inherit permissions from the groups and perform operations on specific cloud resources.
-
SWR is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select projects in specific regions, the users only have permissions for SWR resources in the selected projects. If you set Scope to All resources, the users have permissions for SWR resources in all region-specific projects. When accessing SWR, the users need to switch to the authorized region.
-
-
Table 1 System-defined permissions for SWRName
- |
-Description
- |
-Type
- |
-
|---|
-
-SWR Administrator
- |
-SWR administrator permissions, including all SWR permissions.
- |
-System-defined role
- |
-
-Tenant Administrator
- |
-Administrator permissions for all services except IAM, including all SWR permissions.
- |
-System-defined role
- |
-
-Tenant Guest
- |
-Read-only permissions for all services except IAM, including permissions such as image pull.
- |
-System-defined role
- |
-
-ServiceStage Developer
- |
-ServiceStage developer permissions, including permissions such as image pull.
- |
-System-defined role
- |
-
-
-
-
-
- You can grant permissions (read, write, and manage permissions), to different users for them to access either a specific image or images in a specific organization.
-
-
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
to view the latest information about traces.
on the left of a trace to expand its details.
+
