etcd 3.3.3 and password changes: Noteworthy at Compose


This is your weekly summary of Compose news for those changes and updates which can make your life easier. In this edition, etcd 3.3.3 is now available on Compose and we show you how you should change your admin password. Also a look back at the past week's articles, including the latest stage of the Grand Tour.

etcd 3.3 now available

The latest edition of etcd, 3.3.3, is now available on Compose for you to deploy or upgrade to. The etcd 3.3 release by CoreOS included a lot of new engineering. A switch to a maintained fork of boltdb called bbolt for the backend and a smarter client balancer are among the changes. Combined with numerous fixes from both before and after the release of 3.3.0, etcd 3.3.3 is another great update for the database.

You can upgrade to etcd 3.3.3 today by going to the Settings view in the Compose console for your etcd deployment. For new deployments, etcd 3.3.3 is the current default, so head to Create Deployment if you want to get started with exploring its powerful consensus mechanism and modern gRPC-based API.

An aside: The 3.3 release also saw a number of new, interesting "experimental" features added to etcd. Given their "experimental" status, we won't be making them available at this time, but we look forward to when the etcd v2 API emulation moves to production in a later version.

Admin Passwords and You

TL;DR: Use the Compose console's Change Password setting or Change Password API call when you want to change your password and keep your cluster working.

All of the Compose database deployments are made up of multiple processes working together. To keep them working like that, we manage an administration level user and password so Compose processes can check health and change settings from the web UI. On some Compose databases (PostgreSQL, Compose for MySQL, Redis, Scylla, etcd, and RethinkDB) we make this password available to account owners through the UI and API.

There is a temptation to take possession of this administration user by logging into the database itself and changing the password. Don't do this. As Compose databases are small clusters, usually all that happens is one node changes its password and then other nodes can't talk to it and, well, it's not good.

The safe way to change the admin level user is through the Compose console's change password option. You'll know whether you can do this by looking at the Connection Info. There'll be a Credentials section and after the Password field will be a Change link if the feature is available.

Connection Info's Credentials

This will do a fully coordinated password change across the deployment ensuring that everything stays operating smoothly.

If you want to automate your password changes, and assuming that you have a database that supports password changing, then you will be able to use the /2016-07/deployments/:id/password API endpoint to change the password. If you do use this, remember to poll the returned recipe's endpoint to find out when the password change has completed.

If your database doesn't support changing passwords through the Compose console, don't attempt to change any admin level user you don't recognize through the database. Contact and we'll guide you through the process.

Compose Articles.

In the past week of Compose Articles, we looked at connecting Node.js to Scylla and RethinkDB and rounded up the week's news in NewsBits:

That's it for this week's Noteworthy at Compose. Have a great week and we'll see you for the next Noteworthy in just under a week.

Read more articles about Compose databases - use our Curated Collections Guide for articles on each database type. If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at We're happy to hear from you.

Dj Walker-Morgan
Dj Walker-Morgan was Compose's resident Content Curator, and has been both a developer and writer since Apples came in II flavors and Commodores had Pets. Love this article? Head over to Dj Walker-Morgan’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.