Renaming Critical Commands for DCS Instances

Certain high-risk commands can be modified for DCS Redis instances. Once a command is modified, it is only known to the modifier. The original command is blocked to be run by other users.

Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, HGETALL, SCAN, HSCAN, SSCAN, and ZSCAN commands. For Proxy Cluster instances, you can also rename the DBSIZE and DBSTATS commands.

Only DCS Redis 4.0 and later instances support command renaming.
An instance will restart when its commands are renamed. Exercise caution.
Renaming takes effect immediately once it is complete. Renamed commands will not be displayed on the console for security purposes.
A command can be renamed multiple times. Each new name overwrites the previous name. To restore a high-risk command, or if a renamed command is forgotten, rename the command.
A command cannot be renamed to other original commands. For example, KEYS can be renamed to KEYS or ABC123, but cannot be renamed to SCAN.
Renaming a command starts only with a letter and contains 4–64 characters of letters, digits, hyphens (-), and underscores (_).

Renaming Critical Commands

Log in to the DCS console.
Click in the upper left corner of the management console and select the region where your instance is located.
In the navigation pane, choose Cache Manager.
In the Operation column of an instance, choose More > Command Renaming.
Select a command, enter a new name, and click OK.

In the Command Renaming dialog box, click Add Command to rename multiple commands at the same time. After renaming commands, you can view the renaming operation record on the Background Tasks page.

Figure 1 Renaming commands