Permissions

If you need to grant your enterprise personnel permission to access your LTS 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 Huawei Cloud resources. If your HUAWEI ID does not require IAM for permissions management, you can skip this section.

IAM is a free service. You only pay for the resources in your account.

With IAM, you can control access to specific Huawei Cloud resources. For example, if you want some software developers in your enterprise to be able to use LTS resources but do not want them to be able to delete resources or perform any other high-risk operations, you can create IAM users and grant permission to use LTS resources but not permission to delete them.

IAM supports role/policy-based authorization and identity policy-based authorization.

The following table describes the differences between these two authorization models.

**Table 1** Differences between role/policy-based and identity policy-based authorization
Authorization Model	Core Relationship	Permissions	Authorization Method	Scenario
Role/Policy	User-permission-authorization scope	System-defined roles System-defined policies Custom policies	Assigning roles or policies to principals	To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It provides a limited number of condition keys and cannot meet the requirements of fine-grained permissions control. This method is suitable for small- and medium-sized enterprises.
Identity policy	User-policy	System-defined identity policies Custom identity policies	Assigning identity policies to principals Attaching identity policies to principals	You can authorize a user by attaching an identity policy to it. User-specific authorization and a variety of key conditions allow for more fine-grained permissions control. However, this model can be hard to set up. It requires a certain amount of expertise and is suitable for medium- and large-sized enterprises.

Assume that you want to grant IAM users permission to create ECSs in CN North-Beijing4 and OBS buckets in CN South-Guangzhou. With role/policy-based authorization, the administrator needs to create two custom policies and assign both to the IAM users. With identity policy-based authorization, the administrator only needs to create one custom identity policy and configure the condition key g:RequestedRegion for the policy, and then attach the policy to the users or grant the users the access permissions to the specified regions. Identity policy-based authorization is more flexible than role/policy-based authorization.

Policies/identity policies and actions in the two authorization models are not interoperable. You are advised to use the identity policy-based authorization model. For details about system-defined permissions, see Role/Policy-based Authorization and Identity Policy-based Authorization.

For more information about IAM, see IAM Service Overview.

Role/Policy-based Authorization

LTS supports role/policy-based authorization. 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.

LTS is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for LTS resources in the selected projects. If you set Scope to All resources, the users have permissions for LTS resources in all region-specific projects. When accessing LTS, the users need to switch to the authorized region.

Table 2 lists all the system-defined permissions for LTS. System-defined policies in role/policy-based authorization are not interoperable with those in identity policy-based authorization.

**Table 2** System-defined permissions for LTS
Role/Policy Name	Description	Type	Dependencies
LTS FullAccess	Full permissions for LTS. Users with these permissions can perform operations on LTS.	System-defined policy	CCE Administrator, OBS Administrator, FunctionGraph FullAccess, and AOM FullAccess
LTS ReadOnlyAccess	Read-only permissions for LTS. Users with these permissions can only view LTS data.	System-defined policy	CCE Administrator, OBS Administrator, and AOM FullAccess
LTS Administrator	Administrator permissions for LTS.	System-defined role	Tenant Guest and Tenant Administrator

Table 3 lists the common operations supported by system-defined permissions for LTS.

**Table 3** Common operations supported by system-defined permissions
Operation	LTS FullAccess	LTS ReadOnlyAccess	LTS Administrator
Querying a log group	√	√	√
Creating a log group	√	×	√
Modifying a log group	√	×	√
Deleting a log group	√	×	√
Querying a log stream	√	√	√
Creating a log stream	√	×	√
Modifying a log stream	√	×	√
Deleting a log stream	√	×	√
Configuring log collection from hosts	√	×	√
Configuring delimiters	√	×	√
Querying a filter	√	√	√
Creating a filter	√	×	√
Disabling a filter	√	×	√
Enabling a filter	√	×	√
Deleting a filter	√	×	√
Querying an alarm rule	√	√	√
Creating an alarm rule	√	×	√
Modifying an alarm rule	√	×	√
Deleting an alarm rule	√	×	√
Viewing a log transfer task	√	√	√
Creating a log transfer task	√	×	√
Modifying a log transfer task	√	×	√
Deleting a log transfer task	√	×	√
Enabling a log transfer task	√	×	√
Disabling a log transfer task	√	×	√
Installing ICAgent	√	×	√
Upgrading ICAgent	√	×	√
Uninstalling ICAgent	√	×	√

Identity Policy-based Authorization

LTS supports identity policy-based authorization. Table 4 lists all the system-defined identity policies for LTS. System-defined policies in identity policy-based authorization are not interoperable with those in role/policy-based authorization.

**Table 4** System-defined identity policies for LTS
Identity Policy Name	Description	Type
LTSReadOnlyAccessPolicy	Read-only permissions for LTS.	System-defined policy
LTSFullAccessPolicy	Full permissions for LTS.	System-defined policy

Table 5 lists the common operations supported by system-defined identity policies for LTS.

**Table 5** Common operations supported by system-defined policies
Operation	LTSFullAccessPolicy	LTSReadOnlyAccessPolicy
Querying a log group	√	√
Creating a log group	√	×
Modifying a log group	√	×
Deleting a log group	√	×
Querying a log stream	√	√
Creating a log stream	√	×
Modifying a log stream	√	×
Deleting a log stream	√	×
Configuring log collection from hosts	√	×
Configuring delimiters	√	×
Querying a filter	√	√
Creating a filter	√	×
Disabling a filter	√	×
Enabling a filter	√	×
Deleting a filter	√	×
Querying an alarm rule	√	√
Creating an alarm rule	√	×
Modifying an alarm rule	√	×
Deleting an alarm rule	√	×
Viewing a log transfer task	√	√
Creating a log transfer task	√	×
Modifying a log transfer task	√	×
Deleting a log transfer task	√	×
Enabling a log transfer task	√	×
Disabling a log transfer task	√	×
Installing ICAgent	√	×
Upgrading ICAgent	√	×
Uninstalling ICAgent	√	×