Skip to content

fix(mqtt): force instance replace on user_data change #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BK1031 merged 1 commit into from
Jun 5, 2026
Merged

fix(mqtt): force instance replace on user_data change #72

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions infra/modules/mqtt-ec2/main.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,14 @@ resource "aws_instance" "this" {
mqtt_password_mapache = random_password.mqtt_mapache.result
})

# Force instance replacement when user_data changes. Without this, the
# AWS provider's default is to call ModifyInstanceAttribute, which
# *stores* the new user_data but doesn't re-execute it — the file lands
# only on the next stop+start. We learned this the hard way: a normal
# apply that added a third nanomq user updated state in place but left
# the running broker with the old /etc/nanomq_pwd.conf.
user_data_replace_on_change = true

# user_data is intentionally NOT in ignore_changes: nanomq carries no
# persistent state, so legitimate config edits (new user, ACL change)
# should flow through a normal `terraform apply` and trigger the ~90s
Expand Down
Loading