DCS Instance Passwords

Passwords can be configured to control access to your DCS instances, ensuring the security of your data.

You can set a password during or after instance creation. For details on how to set a password after an instance has been created, see Resetting Instance Passwords.

You can choose whether to enable password-free access based on your security and convenience trade-off.

Scenarios Requiring Passwords

For a DCS instance that is used on the live network or contains important information, you are advised to set a password.
For a DCS instance with public access enabled, a password must be set to ensure data security.

For details on how to access an instance with a password, see Accessing a DCS Instance.

Using Passwords Securely

Hide the password when using redis-cli.
If the -a <password> option is used in redis-cli in Linux, the password is prone to leakage because it is logged and kept in the history. You are advised not to use the -a <password> option when running commands in redis-cli. After you have connected to Redis, run the auth command to complete authentication, as shown in the following example:
```
$ redis-cli -h 192.168.0.148 -p 6379
redis 192.168.0.148:6379>auth yourPassword
OK
redis 192.168.0.148:6379>
```
Use interactive password authentication or switch between users with different permissions.
If the script involves DCS instance access, use interactive password authentication. To enable automatic script execution, manage the script as another user and authorize execution using sudo.
Use an encryption module in your application to encrypt the password.