CentOS 7 (x86_64) - with Updates HVM
Centos.org | 1901_01Linux/Unix, CentOS 7 - 64-bit Amazon Machine Image (AMI)
No new image is available to mitigate Meltdown and Spectre
Looking at the images available, I see no new image is available to mitigate Meltdown and Spectre. This is basic. This is a crucial update and customer are supposed to upgrade on their own
- Leave a Comment |
- Mark review as helpful
Instance limitations makes this image close to useless
This image is locked to just a number instance types. If you plan to change instance type in the future DO NOT USE THIS IMAGE!
AWS Support can't do nothing about it!
Bug report
Will the new version of centos7, Did you fix the bug "modify the system time then the system crash" ? Hope to be answered
i3.large instance type not available
AMIs do not support i3.large instance types
Recent bug report https://bugs.centos.org/view.php?id=12883 was resolved with rest of i3 instances enabled, but i3.large was skipped
Selinux fails to update, crashes VM
We didn't used to have any issues with this AMI, not sure what has changed or what I'm doing differently but my steps are pretty simple. 1.Choose Centos 7 AMI 2.20 GB drive chosen 3.Set network stuff 3. Launch 4. Run sudo yum update -y 5. Crashes on selinux-* update stuff Workaround for now sudo yum update -y --exclude=selinux*
Incorrect Marketplace restrictions in place
We started experimenting with CentOS7 Marketplace images, but had a node fail. The Marketplace images have a marketplace restriction which prevents an EBS volume from being mounted onto another node for examination or recovery of data off the root partition:
Error attaching volume: Cannot attach volume 'vol-xxx' with Marketplace codes as the instance 'i-xxx' is not in the 'stopped' state.
This error message, from the Amazon reps on the Amazon Support Forums, indicate that the volume has a restriction against being mounted as a secondary volume.
security groups
When trying to launch an AMI from the marketplace, there is no way to associate more than one security group.
64bit only is not a functional spec at this time
The new CentOS 7 is attempting to join Red Hat Enterprise in going strictly 64bit with no 32bit binary support. This has numerous issues with backward compatibility and with many current applications. For instance wine is not functional in such an environemtn because too much software is still 32bit
