Update Daml Index Database Password on the Scaled Client Node on AWS

You can change the password of the existing Daml index database after the reconfigure deployment to bind the newly created nodes to the existing VMware Blockchain topology.

As a best practice, changing the Daml Index database password is recommended if you have a weak password or you suspect a security threat.

Prerequisites

• Verify that you have newly scaled Replica nodes. See Scale-Up Deployed VMware Blockchain Nodes on AWS.

• Verify that the newly scaled nodes are bound to the existing VMware Blockchain topology. See Bind the Newly Deployed VMware Blockchain Nodes on AWS.

• Note the Client node IP address, andClient node Daml database password details.

  The details are available in the deployed VMware Blockchain Orchestrator output directory, /home/blockchain/output.

Procedure

1. SSH into the Client node to change the password.
2. Connect to the Daml index database and change the indexdb user password.

   [ec2-user@ip-172-31-71-18 ~]$ docker exec -it daml_index_db bash
   root@a36614ecff20:/# psql -U indexdb
   psql (11.13 (Debian 11.13-1.pgdg90+1))
   Type "help" for help.
   
   indexdb=# \password
   Enter new password: <ENTER_NEW_PASS>
   Enter it again: <ENTER_NEW_PASS_AGAIN>
   indexdb=# \q
   root@a36614ecff20:/# exit

3. Use the VI editor in the Client node VM to edit the configuration files to reflect the new password.

   • Daml Ledger API configuration file /config/daml-ledger-api/environment-vars

   • Daml index database configuration file /config/daml-index-db/environment-vars

   • Telegraf configuration file /config/telegraf/telegraf.conf

   Sample Configuration Commands

   # Update the password in the three configuration files. Replace <old_password> and <new_password> before running the command below.
   sudo sed -i 's/<old_password/<new_password>/g' /config/telegraf/telegraf.conf /config/daml-ledger-api/environment-vars /config/daml-index-db/environment-vars

4. Restart the containers.

   docker restart daml_ledger_api daml_index_db telegraf

5. (Optional) Check the container logs for any errors and resolve the errors.

   If transient errors appear after all the containers are restarted and running, resolve these errors.

6. Update the new password in the VMware Blockchain Orchestrator output files.