docs
patch
infra/staging-rds-encrypt-at-rest
#1 / 1
docs: record staging RDS encryption-at-rest fix
Fixed the StorageEncrypted:false gap flagged in Phase 1's hardening checklist. RDS storage encryption can't be enabled on an existing instance, so this required snapshot -> encrypted copy (via KMS) -> restore into a new instance (musehub-staging-db-v2). Verified data matched exactly before cutover (74 tables, 28 repos, 8 identities on both sides). DATABASE_URL updated in SSM, staging redeployed, verified live via /healthz and a real repo-list API query.
Old unencrypted musehub-staging-db instance retained (not deleted) through the same 2+ week safety window pattern used elsewhere in this migration -- it is no longer receiving traffic. Both staging and production RDS instances are now encrypted at rest.
sha256:c157efa528d47a47935835da16b3f7a81dfe444cedc435aa4c47123e1fe433ce
sha
~6
symbols
1 changed · 1061 in snapshot
files
sha256:2130f9aa1de818b87a1eb694c0cd620efa8d23ae9c6b6344d87cee8b30bba173
snapshot
~6
symbols modified
1
file changed
1061
files in snapshot
0
dead code introduced
Semantic Changes
6 symbols
+
.vscode/
+
alembic/
+
deploy/
+
docs/
+
musehub/
+
scripts/
+
src/
+
src/ts/
+
tests/
+
tools/
~
table
Files Changed
~1
1061 in snapshot
~1
1061 in snapshot
← Older
Oldest on infra/staging-rds-encrypt-at-rest
All commits
Newer →
Latest on infra/staging-rds-encrypt-at-rest
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:c157efa528d47a47935835da16b3f7a81dfe444cedc435aa4c47123e1fe433ce --body "your comment"
No comments yet. Be the first to start the discussion.