gabriel / musehub public
fix BREAKING fix/bootstrap-instance-stale-prod-id #1 / 1
AI Agent gabriel · 5 hours ago · Sep 10, 2026 · Diff

fix: bootstrap-instance.sh PROD_INSTANCE pointed at the legacy EC2 instance

Production cut over to a dedicated AWS account (672469410277) on 2026-08-25 per docs/infrastructure.md — the real production instance is i-043aaed71bef11903 (100.60.14.220, DNS-confirmed via Cloudflare A records for musehub.ai/www.musehub.ai). i-0855d6efe7fa1a49d is the legacy instance in the shared Nonproduction account, explicitly documented as "legacy, not decommissioned yet."

deploy/push.sh already had the correct new instance ID; only bootstrap-instance.sh still had the stale reference. Found while chasing down a red herring in a production SSM investigation — the legacy instance's own IAM-profile gap is separately documented as a known non-issue post-migration ("no longer applies"), so no other fix was needed there.

Confirmed no other file in the repo still references the legacy instance ID (grep across the whole tree, excluding .muse/).

sha256:6289ca9041bde60fb7b75a41efc72ac62e74a2830dfaf41eccacd8c6ea9eb73a sha
sha256:b25f48bad15abb3c46960f21526236a0eb31aa4143e5955282e4bfd373a75003 parent
1 changed · 1071 in snapshot files
sha256:6cf8b6a899fc3fb8544c32b3a73577109b8b3ad0c042b9341f87d71c0d1228f7 snapshot
1
file changed
1071
files in snapshot
Semantic Changes
~ deploy/bootstrap-instance.sh .sh
Files Changed
~1
1071 in snapshot
~ deploy/bootstrap-instance.sh .sh
← Older Oldest on fix/bootstrap-instance-stale-prod-id
All commits
Newer → Latest on fix/bootstrap-instance-stale-prod-id

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:6289ca9041bde60fb7b75a41efc72ac62e74a2830dfaf41eccacd8c6ea9eb73a --body "your comment"