CentOS 7 (x86_64) - with Updates HVM
Centos.org | 2002_01Linux/Unix, CentOS 7 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
created a new instance and couldn't ssh to server
Created a new instance with this image and couldn't SSH to server. I get this error.
~ % ssh -i "20201124.pem" centos@ec2-18-144-138-35.us-west-1.compute.amazonaws.com
centos@ec2-18-144-138-35.us-west-1.compute.amazonaws.com: Permission denied (gssapi-keyex,gssapi-with-mic).
- Leave a Comment |
- 1 comment |
- Mark review as helpful
Version 2002_01 Doesn't work
Seems like it doesn't boot.
Tried to deploy twice.
No output in the EC2 Instance Connect either.
Didn't expect this will happen with AMI from CentOS.
Not working ATM
Tried to launch this instance for 3 times now and am not able to connect properly.
Hope it gets fixed soon.
1/2 check passed
EC2 statucs checks report 1/2 check passed.
- System status checks passed
- Instance status checks failed.
Don't waste your time on this image.
Not working, simply.
As of June 17, 2020,
I tried to lauch an instance with this image,
but failed to connect with it.
EC2 statucs checks report 1/2 check passed.
- System status checks passed
- Instance status checks failed.
Don't waste your time on this image.
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
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*