CentOS 7 (x86_64) - with Updates HVM

This is the Official CentOS 7 x86_64 HVM image that has been built with a minimal profile, suiteable for use in HVM instance types only. The image contains just enough packages to run within AWS, bring up an SSH Server and allow users to login. Please note that this is the default CentOS-7 image that we recommend everyone uses. It contains packages that are updated at points in time to include critical security updates. See more

Customer Reviews

48
Create Your Own Review

Bug report

  • By dennis
  • on 05/18/2017

Will the new version of centos7, Did you fix the bug "modify the system time then the system crash" ? Hope to be answered

Create a swap file!

  • By Searvo
  • on 05/13/2017

Please be aware this instance is pretty much useless with less than 1GB of ram unless you create a swap file. This process is really simple and all you need is a 2GB swap partition to get anything done. Currently running nano for all my purposes.

Only issue is kdump won't start on instances with < 2GB ram

  • By bdavis
  • on 04/20/2017

Only issue is kdump won't start on instances with < 2GB ram, tracked this down to the crashkernel=auto setting. Changing to pre-determined value seemed to allow kdump to start successfully.

i3.large instance type not available

  • By cOrtEx
  • on 04/11/2017

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

Simple, clean, minimal CentOS 7 image

  • By Simple, clean, minimal CentOS 7 image
  • on 01/03/2017

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

  • By dataman
  • on 08/26/2016

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

  • By Jeff P.
  • on 03/22/2016

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!!!

  • By W. Flame
  • on 02/02/2016

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!

  • By Amazon Customer
  • on 01/13/2016

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

  • By Krish
  • on 12/23/2015

When trying to launch an AMI from the marketplace, there is no way to associate more than one security group.