Description of problem:
Apparently AWS is deprecating AMIs which were originally published > 2yrs ago starting July 30th 2022. Per their note the images don't go away but calls to the DescribeImages api call will stop showing them. Can someone check to make sure that the mapi-aws won't run into problems creating new instances on long lived clusters? I did a quick search for that call in mapi-aws and didn't find it but by no means should my naive search be trusted.

As we all know, we don't manage the AMI with the lifecycle of the cluster, it's effectively set in stone at install time unless an admin takes action to update the image and machine config necessary to ignite the newer images.


Version-Release number of selected component (if applicable):
4.1

How reproducible:
unknown, this is really a request that we investigate to ensure we don't have a problem coming at us on July 30th when they start deprecating AMIs. The outcome of this investigation will likely need to make it into a KCS which can be published to allay customer concerns when they receive similar emails.

Additional info: The full contents of an email AWS delivered to customer using images which will be deprecated follows with select redactions.

====== cut/paste ======
On March 31, 2022, EC2 announced that all public AMIs will have the deprecation time set to two years after their creation date [1]. Once an AMI is deprecated, it will no longer appear in DescribeImages [2] API calls for users that are not the owner of the AMI. Deprecating an AMI only reduces the visibility of the AMI in untargeted searches, but continues to be usable and available to you. Users of a deprecated AMI can continue to launch instances and describe the deprecated AMI using its ID. Deprecation time for all public AMIs will now be set automatically to two years after their creation. Public AMIs already older than two years will be deprecated on July 30, 2022 instead of the originally stated date of June 30 to give you time to assess and mitigate potential impact to your workflows which may perform DescribeImages requests that do not specify image IDs.

We have identified that you have launched one or more instances in the last month using a public AMI which will be deprecated on July 30, 2022. While you will continue to be able to launch instances using the AMI IDs, the AMIs will not be visible on the public AMI catalog [3] or in DescribeImages calls by default once deprecated. To list deprecated AMIs in the DescribeImages API calls, you must specify the --include-deprecated parameter [4]. If you would like to view details about the deprecated AMI, you can describe it using its ID as well. This message is to notify you of the upcoming change, and does not require any action from you.

The following is a list of old public AMIs you have used for instance launches in the last month in the AP-SOUTHEAST-1 Region :
ami-0d76ac0ebaac29e40

To learn more about viewing and managing the deprecation time for your AMIs, please refer to the "Deprecate an AMI" documentation [5].

If you have any further questions or comments regarding this matter, please contact AWS Support [6].


[1] https://aws.amazon.com/about-aws/whats-new/2022/03/amazon-machine-images-public-visibility-two-years/
[2] https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeImages.html
[3] https://aws.amazon.com/blogs/aws/new-ami-catalog-and-new-ami-launch-button-are-now-available/
[4] https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html
[5] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ami-deprecate.html
[6] https://aws.amazon.com/support 
====== cut/paste ======