Score:0

Why does AWS take a long time to change the password of DB Clusters?

cn flag

I'm running this command to change the master user password of a DB Cluster on AWS:

aws rds modify-db-cluster --db-cluster-identifier development-db \
    --region us-east-2 --master-user-password newpassword --apply-immediately \
    --no-cli-pager > /dev/null

When I do this the status of the cluster changes from available to resetting-master-credentials. Sometimes it'll be in this status for minutes at a time and it just doesn't make any sense to me - I'd expect this change to be near instantaneous.

Any ideas as to why it wouldn't be?

cn flag
Bob
Without any knowledge of RDS internals: in many cloud products changed settings are effected by a re-deploy of the product and not by updating the running product. So aws doesn't execute a MySQL native `ALTER USER 'MasterUser' IDENTIFIED BY 'New-Password'` but instead starts new rds instances with the new password as an altered boot option and then shifts load to those new instances. That takes more time. But that is an educated guess.
Tim avatar
gp flag
Tim
You'd have to ask AWS that question as it's an implementation detail.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.