CentOS 7 (x86_64) - with Updates HVM
CentOS.org | 2002_01Linux/Unix, CentOS 7 - 64-bit Amazon Machine Image (AMI)
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
- Leave a Comment |
- Mark review as helpful
Simple, clean, minimal CentOS 7 image
If you are looking for a simple, minimal CentOS 7 image - here it is. Selinux enabled, no additional packages pre-installed, the cloud-init script does only necessary minimum. Perfect!
As it is mentioned from other posts, this is a marketplace image with some restrictions (mounting, cloning, ...), it doesn't concern us so far.
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.
This is NOT VERSION 7 it is version 6.4!!!
Provisioned this AMIS which is advertised as being version 7.
After provisioning, it turns out it is version 6.4.
Provisioned a second one to make sure I didn't make a mistake.
See below:
>cat centos-release
CentOS release 6.4 (Final)
cfn-init is not working!
I installed this Centos 7 AMI and the cfn-init script is failing.
Here is the errors from /var/log/cloud-init.log
+ /opt/aws/bin/cfn-init -v --stack q1 --resource WebServerInstanceA --configsets All --region us-west-2
/var/lib/cloud/instance/scripts/part-001: line 4: /opt/aws/bin/cfn-init: No such file or directory
When I check the /opt and find the cfg-init file, none was found. When doing ls on the /opt directory, no directory or files?
[root@ip-10-8-8-32 opt]# pwd
/opt
[root@ip-10-8-8-32 opt]# ls -al
total 4
drwxr-xr-x. 2 root root 6 Jun 10 2014 .
dr-xr-xr-x. 17 root root 4096 Oct 7 12:19 ..
Is this a bug? my AMI use is ami-d440a6e7
security groups
When trying to launch an AMI from the marketplace, there is no way to associate more than one security group.
Well version
trying for the poc enivorment and it is a better version for me.
but i am not sure some billing question will could release on the product pages.
Works great after a little setup
We were looking for a bare bones install to play with CentOS 7 before deploying in a production environment and this image is perfect for that.
The AWS instructions say to connect as root but the image forced us to connect as centos. Once we were in, we were able to use sudo to set a strong password for the root user and su to root. We realize that logging in as root in a production environment is a bad thing but for testing we expect full root access. Glad this image gave us that ability...hope it doesn't get taken away.
At least It's better than their CentOS 6 AMIs...
To be honest, the AMIs from CentOS.Org are generally disappointing. While they're great starting points for creating more useful AMIs, they're not otherwise well-suited for generic use.
While it's nice that they're finally releasing AMIs with cloud-init, it's a bit disappointing that the AWS cli tools aren't included. It's really not that hard to export the SRPMs from an Amazon Linux instance and build them for other instance types. So, really not sure why CentOS doesn't include them. It's literally five minutes worth of work (if'you've scripted the process out). That they don't even include the awscli package from either pypi or from S3 is even more disappointing - as there's next to zero work to install that package.
Why is this a gripe-point for me? No AWS CLI tools greatly limits what you can do with your AMI: there's little point attaching an instance role if you've got no tools to make use of that role; if you want to make use of the HVM optimized drivers, no AWS RPMs means you're kinda boned, too.