2023 November 5
We have been running on the AWS Linux 2023 platform since 2023-10-16 with no problems and we're not going back, so it's time to get rid of the legacy instance and its storage volumes, which are running up bills whilst sitting there idle. These are: Instance: i-0756b0658cac51c9d (Scanalyst (Linux 2 Legacy)) /dev/xvda vol-075b7c5e09688d5e6 (Scanalyst L2 root) 32 Gb /dev/sdb vol-0dd32c02c3bbe7e18 (Scanalyst L2 server) 128 Gb Detached volumes with Volumes panel/select volume/Actions/Detach volume. Instance storage tab shows no volumes attached. Deleted volumes with Volumes panel/select volume/Actions/Delete volume. Terminated instance with Instances panel/select instance/Instance state/ Terminate instance. Status went to Shutting-down, then Terminated. We'll confirm it's gone on the morrow. And...it's gone! Now let's clean up ancient Scanalyst backup images and their associated file system snapshots. Our policy is to keep backups around for about the last six months, but these only get cleaned up when I get around to it, such as today. Here are the backups to be purged, with each listed by its AMI name, AMI ID, and associated file system snapshots, from oldest to newest. Note that when deleting a backup you must first delete the AMI ("Deregister AMI") and then manually delete the file system snapshots. You can't delete the snapshots while they're attached to an AMI. Scanalyst Backup 2022-08-12 ami-027d2af449a36b93b Root snap-051e6dd486aeb083a Server snap-0eae8c50c88a1e804 Scanalyst Backup 2022-09-29 ami-0a8dd1d348e7cb480 Root snap-0191f87734bed6bc4 Server snap-0d9ce824b0d65575d Scanalyst Backup 2022-11-02 ami-00582249f4fecd748 Root snap-0fb07d2230caddd92 Server snap-00644fa844a49db8b Scanalyst Backup 2022-11-15 ami-014818d3be9bdfe1a Root snap-0b555e3cb1330ad44 Server snap-0b225a05f2e850aa9 Scanalyst Backup 2022-11-30 ami-0f14c9c685e0f742b Root snap-00f00d9ad3487c01e Server snap-04c09d9a2e8ff74ca Scanalyst Backup 2023-01-04 ami-0aea3cc0e0cd2db03 Root snap-094cd8bb7ed24e7fd Server snap-0a730d2540e3d4759 Scanalyst Backup 2023-01-13 ami-0ebedba2578b7a820 Root snap-0d6f995e991ce9d9d Server snap-0e641cc093dfc3de8 Scanalyst Backup 2023-01-26 ami-0a961e0164b0a48cc Root snap-0e0cc57fc452a2525 Server snap-0aafa313d255911dd Scanalyst Backup 2023-03-03 ami-00b01cfd8b1c32ef7 Root snap-069a21550c62aa652 Server snap-0b25ff7df3942435b Scanalyst Backup 2023-03-17 ami-09ea87968630d8b41 Root snap-0bb8ac1b46b8805a5 Server snap-036cc92464c885fd0 Scanalyst Backup 2023-04-18 ami-0a329322db25d00a4 Root snap-0507b136c61445d66 Server snap-0901fe0bd4ec72b2b On 2021-10-03, during the initial configuration of the system, we had to resize the root volume due to Docker's insistence on installing itself and its applications there. Before the hazardous resizing step, I made the following snapshot of the original root volume: Scanalyst root backup 2021-10-03 01:11 snap-04347d032d7206aa9 The resizing went OK, and I promptly forgot about the snapshot, leaving it around and running up storage charges to the present day. I stumbled over it while doing the above cleanups and deleted it today.