All Products
Search
Document Center

Data Transmission Service:Identity management

Last Updated:Mar 28, 2026

Access Data Transmission Service (DTS) through Resource Access Management (RAM) identities — not directly with your Alibaba Cloud account. RAM provides three identity types to fit different access patterns: RAM users for individuals and programs, RAM user groups for managing sets of users together, and RAM roles for granting temporary access to trusted entities.

Who should read this

  • DTS users: If you need DTS access and cannot perform a task, ask your administrator to update your permissions. See System policies for DTS and Custom policies for DTS for available permissions.

  • Account administrators: Use this page to understand the identity types available and the security practices to apply when granting DTS access.

RAM users

A RAM user is a persistent identity you can create under your Alibaba Cloud account. After granting the appropriate permissions, a RAM user can access Alibaba Cloud resources through the Alibaba Cloud Management Console or by calling API operations.

RAM users can be created by Alibaba Cloud accounts and by RAM users or RAM roles that have administrative rights.

When creating a RAM user, set the Access Mode based on how the user will access resources:

Access modeHow it worksWhen to use
Console AccessLog on to the Alibaba Cloud Management Console with a username and passwordHuman users who need console access
Using permanent AccessKey to accessMake API calls using an AccessKey pairPrograms and automated scripts
BothSupports both console and API accessUsers who need both access methods

Security practices

  • Create a dedicated admin RAM user first. Use your Alibaba Cloud account to create one RAM user with administrative rights, then use that RAM user to create and manage all other RAM users. Avoid using the Alibaba Cloud account for routine access.

  • Separate individual users from program users. A RAM user for a person has console access; a RAM user for a program uses an AccessKey pair. Mixing the two creates unnecessary risk — unintended manual changes can affect automated workflows and vice versa.

  • Enable multi-factor authentication (MFA) for console users. MFA adds a second verification step when logging in, reducing the risk of unauthorized access if a password is compromised.

  • Grant least-privilege permissions. Give each RAM user only the permissions required for their specific tasks. Start with system-managed policies for common use cases, then tighten access by defining custom policies scoped to your actual requirements.

  • Never embed AccessKey credentials in code. A leaked AccessKey pair compromises every resource in your account. Use Security Token Service (STS) tokens or environment variables to pass credentials at runtime instead.

  • Set up single sign-on (SSO) if your organization uses an identity provider. SSO lets RAM users log on to Alibaba Cloud from your enterprise identity management system, centralizing access control.

Related topics

RAM user groups

A RAM user group is a collection of RAM users that share the same set of permissions. Assign permissions to the group rather than to individual users, and every member inherits those permissions automatically.

Security practices

  • Apply least-privilege permissions at the group level. Grant only the permissions the group needs to perform its responsibilities.

  • Update group membership when duties change. Remove a RAM user from a group as soon as that user no longer needs the group's level of access.

  • Revoke permissions that the group no longer needs. Review group policies regularly and remove permissions that are no longer required.

Related topics

RAM roles

A RAM role is a virtual identity with attached policies but no permanent credentials — no logon password and no AccessKey pair. To use a RAM role, a trusted entity must first assume it. When a trusted entity calls the AssumeRole operation, it receives a temporary STS token that grants access to Alibaba Cloud resources as the role.

Security practices

  • Avoid changing the trusted entity of a role after creation. Changing the trusted entity can cause permission loss that disrupts your workloads. Adding a new trusted entity introduces privilege escalation risk. If changes are necessary, test them fully before applying to a production role.

  • Set an appropriate STS token validity period. Shorter validity periods reduce the window of exposure if a token is compromised. The maximum validity period is bounded by the maximum session duration configured for the RAM role.

  • Set an appropriate maximum session duration for the RAM role. This controls the upper limit for any STS token issued for the role. Keep it as short as your use case allows.

  • Set up SSO for RAM roles if your organization uses an identity provider. Role-based SSO lets your enterprise users assume RAM roles directly from your identity management system.

The maximum validity period of an STS token cannot exceed the maximum session duration set for the RAM role. Configure both values deliberately.

Related topics

References