Production readiness — Section 7: Secrets and Application Configuration
0
Anchors
—
Blast radius
—
Churn 30d
0
Proposals
Secrets are currently hand-provisioned per instance (.env), not via the drafted SSM pipeline (deploy/secrets.sh) — only 3 of 7 required SSM parameters exist. Work: populate the missing SSM parameters, run secrets.sh against staging to prove it end-to-end, then decide whether production adopts it from day one.
Activity1
Update 2026-08-25: Resolved for Production — adopted the SSM Parameter Store pipeline (
deploy/secrets.sh) from day one rather than repeating staging's hand-provisioned/partial setup. All 6 secrets now live in/musehub/production/*as KMS-encrypted SecureString parameters;secrets.shruns end-to-end and regenerates.envcorrectly. Migration itself never exposed a secret value outside the instance — a temporary write policy was granted, used once, then removed and replaced with the correct least-privilege read-only policy.Staging remains at 3-of-7 parameters in SSM — completing that is a reasonable follow-up but wasn't required to answer this ticket's open question (which pipeline should production use). Answer: SSM, from day one.