What does (EC2) "AMI: Unavailable" mean and how do I handle it?

I am running two EC2 instances (Linux and Windows) on AWS that were run based on AMIs provided by Amazon. Everything works fine, but after a couple of weeks I noticed that in Windows Instance, under the Description tab, it says "AMI: Unavailable (ami-f0c9ff84)".

I haven't done a reboot on this EC2 in over a month and I'm curious that after a reboot everything will work without issue. Is "AMI unavailable" a serious problem? Why is AMI unavailable? I'm not sure if I need to take some action on my part (for example, to get an EBS snapshot in case of a failed reboot, whatever).

Should I be concerned that restarting the instance won't work while it says "AMI is unavailable"?

Thanks in advance!


source to share

2 answers

In the meantime, this was addressed in the AWS team's response to an identical question asked in the AWS Forum, see EC2 AMI Reports: Not Available :

This is an AWS owned AMI that is no longer in the public domain as it is deprecated. This will not affect your current instance. Additionally, if you create an EBS AMI for your executable instance, you will back up your current configuration over time - which you can use to run duplicate instances.

Currently AWS has provided a 32-bit AMI for Windows Server 2008: AMI-541dcf3d



As the other answer suggests, this is not a problem. It just means that the original AMI used to create your instance is no longer available (so you won't be able to recreate your instance from the same image as you originally).



All Articles