AMI retention & publish process to AWS
by pub＠wesleytech.com
Greetings! Can someone please explain the process for publishing Fedora AMI's to AWS?
I see the "official" Fedora Cloud page has 'Click to launch' base images for AWS here: https://alt.fedoraproject.org/cloud/
However, if I click to launch the GP2 HVM AMIs, I see the us-west-2 (Oregon) AMI listed is ami-3dea475d, which was published 2016-11-15.
Do new AMI's get published on a particular cadence? If so, how/when does that happen?
If I search for AMI's from the Fedora account ID (125523088429), I can see AMI's as recent as January 29th.
https://us-west-2.console.aws.amazon.com/ec2/v2/home?region=us-west-2#Ima...
Are all images published by the Fedora account suitable/recommended for use?
I'm assuming that the newest AMI's would have all updates and patches up to date as of the publish date, is this correct?
What is the retention policy on AMI's? Can we count on a particular AMI (eg; ami-d27bc3b2 ) being available and not disappearing for a specific amount of time?
Thanks for your help!
7 years, 2 months
- 3
- 2
I am on leave today
by Kushal Das
Hi all,
I am on leave today. I will check emails in my afternoon time, and later
at night.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
7 years, 2 months
- 1
- 0