All Products
Search

This Product

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

    Document Center

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

    Last Updated:Mar 30, 2026

    The Cloud-native deployment mode is compatible with higher Redis versions and provides a more flexible architecture. This topic describes how to convert a Classic instance to a Cloud-native instance.

    Important

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

    How it works

    Important

    • Ensure your application has a reconnection mechanism.

    • The instance becomes read-only for less than one minute during the conversion. This helps the new instance quickly synchronize incremental data and prevents dual-write issues caused by DNS caching. If the instance handles a large number of write requests, the read-only duration may be longer. We recommend that you perform the conversion during off-peak hours.

    Limitations

    Billing requirements

    Only pay-as-you-go instances are supported. Subscription instances must first be converted to pay-as-you-go instances.

    Network configuration

    • Bandwidth adjustment

    • Endpoints: You must release any public or direct connection endpoints on the cluster instance.

    Security configuration

    • Add the IP addresses of all clients to the instance's whitelist. This includes clients in the instance's VPC and clients in other VPCs connected via tunnels. If you do not enable public access for the instance, you can add 0.0.0.0/0 to the whitelist. Then, set the parameter #no_loose_check-whitelist-always to yes.

    • If a security group is configured for the instance, you must add the CIDR block of the VPC to the whitelist, remove the security group, and then convert the instance. After the conversion is complete, you can re-associate the security group with the instance.

    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 first disable these features.

    • Instances with TDE enabled can be converted only to a cloud-native instance that is compatible with Redis 6.0 or 7.0, not Redis 5.0.

    Node type

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

    Considerations

    • After the conversion, no data is lost, and the instance ID, endpoint, accounts, passwords, and IP whitelist configurations remain unchanged.

    • If the original instance runs Redis 2.8 or 4.0, upgrade it to Redis 5.0 before converting.

    • 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 section, click Convert to cloud-native.

      Note

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

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

      Choose specifications equal to or higher than those of the original instance.

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

      During this operation, you can also upgrade the instance to a version higher than Redis 5.0, such as Redis 6.0 or Redis 7.0. For more information, see New features and compatibility of major versions.

    5. Read and select the checkbox to agree to the service agreement 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 "The capacity of the requested instance is insufficient" error message?

      A: This error message indicates that Cloud-native resources are insufficient in the zone where your original instance is located. This issue may occur for instances that were created a long time ago. You can migrate the instance to another zone and try again.

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

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

    Related topics