Adam Moussa ea9ab1c463 fix(infra): adopt existing data volume + cache AMI to stop replacement churn ... - 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:36:45 -04:00
..
file-share-stack.ts	fix(infra): adopt existing data volume + cache AMI to stop replacement churn	2026-06-05 13:36:45 -04:00