All Products
Search

This Product

    Tair (Redis® OSS-Compatible):Convert to the cloud-native deployment mode

    Document Center

    Tair (Redis® OSS-Compatible):Convert to the cloud-native deployment mode

    Last Updated:Jan 23, 2026

    The Cloud-native deployment mode is compatible with newer Redis versions and provides a more flexible architecture. You can convert a Classic instance to a Cloud-native instance.

    Important

    This feature is in public preview. To use it, you can submit a ticket to request access.

    Conversion process

    image
    Important

    • During the instance switchover, a transient connection error occurs that lasts for less than 30 seconds. Ensure that your application has a reconnection mechanism.

    • The instance becomes read-only for less than one minute during the conversion. This allows the new instance to synchronize incremental data and prevents dual-write issues caused by DNS cache. The read-only period may be longer for instances that have high write workloads. Perform the conversion during off-peak hours.

    Prerequisites

    Billing method

    Only pay-as-you-go instances are supported. You must change subscription instances to pay-as-you-go.

    Network configuration

    • Bandwidth adjustment

    • Endpoint: If a cluster instance has an Internet endpoint or a direct connection endpoint, you must release these endpoints.

    Security configuration

    • For instances that allow password-free access from a virtual private cloud (VPC), you must add the CIDR block of the VPC to the whitelist. Then, change the parameter #no_loose_check-whitelist-always to yes.

    • For instances configured with security groups, you must add the CIDR block of the VPC to the whitelist. Then, delete the security group before you convert the instance to the cloud-native mode. After the conversion is complete, you can add the security group again.

    Feature compatibility

    • Conversion is not supported if multi-zone read/write splitting or Global Distributed Cache is enabled.

    • If TLS connections or data flashback (PITR) is enabled, you must disable these features before you proceed.

    • Instances with TDE (Transparent Data Encryption) enabled can only be converted to cloud-native instances compatible with Redis 6.0 or 7.0. Conversion to a Redis 5.0 compatible instance is not supported for these instances.

    Node type

    Only dual-replica (high availability) instances are supported. You must first upgrade single-replica (single-node) instances to dual-replica instances.

    Notes

    • After the conversion, the instance ID, endpoint, account and password, and IP whitelist settings remain unchanged. No data is lost from the instance.

    • If the original instance runs Redis 2.8 or 4.0, upgrade the instance to Redis 5.0 before you perform the conversion.

    • After a Tair (Enterprise Edition) instance is converted to the cloud-native deployment mode, its Terraform resource type changes from alicloud_kvstore_instance to alicloud_redis_tair_instance. For more information, see Tair Resources.

    Procedure

    1. Log on to the console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.

    2. In the Configuration Information section, click Convert To Cloud-native.

      Note

      This feature is in public preview. If you cannot find the button, submit a ticket to request access.

    3. Select the shard type and number of shards for the converted instance.

      Select an instance type that is the same as or higher than that of the original instance.

    4. Select the Billing Method, compatible instance version, Switch Time, and other configuration parameters.

      When you perform this operation, you can also upgrade the instance to a version newer than Redis 5.0, such as Redis 6.0 or Redis 7.0. For more information, see New features and compatibility of major versions of Redis Open-Source Edition.

    5. Read and select the checkbox to agree to the Terms of Service and the Conversion Notes. Then, click Buy Now.

      The instance status changes to Upgrading/Downgrading Across Architectures. When the instance status changes to Running, the conversion is complete.

    FAQ

    • Q: Why do I receive the error message The capacity of the requested instance is insufficient?

      A: This error indicates that the Cloud-native resources are insufficient in the zone where the original instance resides. This may occur if the original instance was created a long time ago. You can migrate the instance to another zone and try again.

    • Q: After the conversion is complete, I cannot connect to the instance using DMS.

      A: You must add the IP address of the DMS server to the whitelist.

    References