Commit graph

3 commits

Author SHA1 Message Date
Adam Moussa
2c45931741
fix(infra): adopt existing data volume + cache AMI to stop replacement churn (#5)
Some checks are pending
Deploy / deploy (push) Waiting to run
- Import vol-04d951cccacc435b5 (the real 500GiB data volume, orphaned by
  the 2026-06-05 redeploy) via Volume.fromVolumeAttributes — unmanaged,
  so CloudFormation can attach but never create/replace/delete it.
- Remove the inline /dev/xvdf blockDevice (this is what created the
  empty volume that shadowed the data).
- cachedInContext: true + committed cdk.context.json so AMI updates are
  deliberate (uncached lookup replaced the instance on every new AL2023
  release).
- Includes the previously-deployed-but-uncommitted 2026-05-27 work:
  standalone volume pattern, volume-wait userdata, SFTP access.

Deploy replaces the instance once; userdata's blkid guard mounts the
existing filesystem without formatting.
2026-06-05 13:40:05 -04:00
Adam Moussa
cced82c0d7 Remove unused FB_HASH variable from user data
FileBrowser's users add command hashes internally.
2026-05-14 15:35:51 -04:00
Adam Moussa
427242499d Initial file-share stack
CDK stack deploying a t4g.small EC2 instance with Samba and FileBrowser
for personal file storage over the site-to-site VPN. Includes 500 GiB
gp3 data volume with daily DLM snapshots.
2026-05-14 15:23:38 -04:00