#295 Drop "Standard" AMIs
Opened 6 years ago by puiterwijk. Modified 2 years ago

I think that having the "Standard" images uploaded and listed on our website has no benefits, and only increases user confusion ("Which image type do I want?").
Especially since the only thing it impacts is the default storage type selection in AWS, but it can still be overridden in the wizard: even with a GP2 image, I can spawn either a GP2 or Standard backed instance by selecting in the wizard.

Since Amazon themselves is trying to push people to GP2, I think we should keep those and drop Standard: try to either start our Standard AMI, or the GP2 and select Standard for root storage, and you get the following message:

General Purpose (SSD) volumes provide the ability to burst to 3000 IOPS per volume, independent of volume size, to meet the performance needs of most applications and also deliver a consistent baseline of 3 IOPS/GiB.

[X] Make General Purpose (SSD) the default boot volume for all instance launches from the console going forward (recommended).
[ ] Make General Purpose (SSD) the boot volume for this instance.
[ ] Continue with Magnetic as the boot volume for this instance.

Free tier eligible customers can get up to 30GB of General Purpose (SSD) storage.

+1
Also, fedimg load will reduce to half if we drop uploading Standard images

Is anyone aware of any downside in dropping Standard images?

I think I'm +1 - @davdunc or @jdoss - any thoughts?

Also. Maybe we should not do this in the middle of a release cycle and just plan to make the change for F30 ?

I personally think we can just drop them from the website now and don't add them for arm64.

Sounds like a good idea.

Metadata Update from @ngompa:
- Issue tagged with: AWS

4 years ago

Metadata Update from @mhayden:
- Issue assigned to mhayden

2 years ago

Agreed in today's cloud meeting that I'll write up a proposal to get this done. Getting the GP2 > GP3 switch approved was pretty easy here:

https://fedoraproject.org/wiki/Changes/CloudEC2gp3

Log in to comment on this ticket.

Metadata