Estos contenidos se han traducido de forma automática para su comodidad, pero Huawei Cloud no garantiza la exactitud de estos. Para consultar los contenidos originales, acceda a la versión en inglés.
Centro de ayuda/ Object Storage Service/ Guía del usuario/ Control de permisos/ Mecanismos de control de permisos/ IAM Permissions
Actualización más reciente 2024-09-18 GMT+08:00
Ver PDF
Compartir

IAM Permissions

You can create IAM users under a registered cloud service account, and then use IAM policies to control users' access permissions to cloud resources.

permisos de IAM define the actions that can be performed on your cloud resources. In other words, permisos de IAM specify what actions are allowed or denied.

permisos de IAM with OBS permissions take effect on all OBS buckets and objects. To grant an IAM user the permission to operate OBS resources, you need to assign one or more OBS permission sets to the user group to which the user belongs.

For details about OBS permissions controlled by IAM policies, see Permissions Management.

permisos de IAM Application Scenarios

permisos de IAM are used to authorize IAM users under an account.

  • Controlling permissions to cloud resources as a whole under an account
  • Controlling permissions to all OBS buckets and objects under an account
  • Controlling permissions to specified cloud resources under an account

Policy Structure and Syntax

A policy consists of a version and statements. Each policy can have multiple statements.

Figura 1 Policy structure

Policy syntax example:

{
	"Version": "1.1",
	"Statement": [
                {
			"Effect": "Allow",
			"Action": [
				"obs:bucket:HeadBucket",
				"obs:bucket:ListBucket",
				"obs:bucket:GetBucketLocation"
			],
			"Resource": [
				"obs:*:*:bucket:*"
			],
			"Condition": {
				"StringEndWithIfExsits": {
					"g:UserName": ["specialCharacter"]
				},
				"Bool": {
					"g:MFAPresent": ["true"]
				}
			}
		}
	]
}
Tabla 1 Policy syntax parameters

Parameter

Description

Version
The version number of a policy.
  • 1.0: RBAC policies. An RBAC policy consists of permissions for an entire service. Users in a group with such a policy assigned are granted all of the permissions required for that service.
  • 1.1: Fine-grained policies. A fine-grained policy consists of API-based permissions for operations on specific resource types. Fine-grained policies, as the name suggests, allow for more fine-grained control on specific operations and resources than RBAC policies. For example: You can restrict an IAM user to access only the objects in a specific directory of an OBS bucket.

Statement

Permissions defined by a policy, including Effect, Action, Resource, and Condition. Condition is optional.

  • Effect

    The valid values for Effect are Allow and Deny. System policies contain only Allow statements. For custom policies containing both Allow and Deny statements, the Deny statements take precedence.

  • Action

    Permissions of specific operations on resources in the format of Service name:Resource type:Operation. A policy can contain one or more permissions. The wildcard (*) is allowed to indicate all of the services, resource types, or operations depending on its location in the action. OBS has two resource types: bucket and object.

    For details about actions, see Bucket-Related Actions and Object-Related Actions.

  • Resource

    Resources on which the policy takes effect in the format of Service name:Region:Domain ID:Resource type:Resource path. The wildcard (*) is allowed to indicate all of the services, regions, resource types, or resource paths depending on its location in the action. In the JSON view, if Resource is not specified, the policy takes effect for all resources.

    The value of Resource supports uppercase (A to Z), lowercase (a to z) letters, digits (0 to 9), and the following characters: -_*./\. If the value contains invalid characters, use the wildcard character (*).

    OBS is a global service. Therefore, set Region to *. Domain ID indicates the ID of the resource owner. Set it to * to indicate the ID of the account to whom the resources belong to.

    Examples:

    • obs:*:*:bucket:*: all OBS buckets
    • obs:*:*:object:my-bucket/my-object/*: all objects in the my-object directory of the my-bucket bucket
  • Condition

    Conditions for the policy to take effect (Optional). Format: Condition operator:{Condition key:[Value 1, Value 2]}

    The condition includes the global service condition name and cloud service condition name. The condition names supported by OBS are the same as those in the bucket policy. When configuring in IAM, add obs:. For details, see Conditions.

    The value of Condition can contain only uppercase (A to Z), lowercase (a to z) letters, digits (0 to 9), and the following characters: -,./_@#$%&. If the value contains unsupported characters, consider using the condition operator for fuzzy match, such as StringLike and StringStartWith.

    Examples:

    • StringEndWithIfExists":{"g:UserName":["specialCharacter"]}: The statement is valid for users whose names end with specialCharacter.
    • "StringLike":{"obs:prefix":["private/"]}: When listing objects in a bucket, you need to set prefix to private/ or include private/.
  • Fine-grained permission control at the Resource level will be deployed in regions one after another. Before using this feature, ensure that the region where your bucket resides supports the feature.
  • To use the fine-grained permission control at the Resource level, submit a service ticket to OBS.

Authentication of permisos de IAM

The authentication of permisos de IAM starts from the Deny statements. The following figure shows the authentication logic for resource access.

Figura 2 Authentication logic

The actions in each policy are in the OR relationship.

  1. A user accesses the system and makes an operation request.
  2. The system evaluates all the permission policies assigned to the user.
  3. In these policies, the system looks for explicit deny permissions. If the system finds an explicit deny that applies, it returns a decision of Deny, and the authentication ends.
  4. If no explicit deny is found, the system looks for allow permissions that would apply to the request. If the system finds an explicit allow permission that applies, it returns a decision of Allow, and the authentication ends.
  5. If no explicit allow permission is found, IAM returns a decision of Deny, and the authentication ends.