The mentioned t1.micro, m1.large and m3.large Instance Types are all previous generation Instance Types, meaning they are PV and not HVM. After chatting with AWS Support I've learned that PV based Instance Types cannot be upgraded to HVM based Instance Types. All current Instance Types are HVM based. This doesn't mean we can't create PV based Instance Types anymore as you can still choose one of the previous generation Instance Types, but I'm not sure if that helps us.
I think we should consider switching to HVM based Instance. Not covered by this JIRA, but this should not concern our Voyent Alert! Clusters as they are already running on t2 HVM based Instance Types. So sticking to apps1, demo1 and proxy1 for now on our "old" production account. Any attached custom Volumes should be a breeze to "port" over as we just need to re-attach them to a new replacement Instance. The problem lies with the standard provided 8 GB root Volumes. These Volumes cannot be reattached to a new HVM based Instance as the Linux kernel installed on it will not run. This means that whatever we have installed on the root Volume of the mentioned Instances we need to reinstall on the respective replacement Instances.
I feel that demo1 and especially proxy1 are probably fairly easy to recreate, as proxy1 just runs Apache HTTP Server I believe, and demo1 just has Java installed on the root Volume (all the Tomcat servers are installed on the added custom Volume). The apps1 Instance is likely harder to recreate. Maybe Jeremy can make an assessment of what needs to be done to recreate the apps1 Instance if we decide to do so.
Evidently, there will be some downtime when switching over from one to the other.
For both the ken.fyten@icesoft.com and engineering.support@icesoft.com accounts I did a fair amount of clean up already (not necessarily related to this case, but still...):
I'm currently looking into Snapshots that can be removed...