similar to: Instance-backed CentOS AWS AMIs?

Some additional info... AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS team, not by AWS. Details and suggestions to contact this list for assistance are published at both https://wiki.centos.org/Cloud/AWS and https://wiki.centos.org/Cloud/AWS Basically, the maintainer of the Centos.org AWS account just needs to add/approve the current AMIs for the g3.* instance

Hello- Does anyone one this list maintain the official CentOS 6 + 7 AMIs in AWS? If so, could you please enable those images for use with the new g3.* instance types? If this list is the wrong place for this request, please point me in the right direction. Thanks! -Stephan

On 07/26/2017 09:29 AM, Stephan Koledin wrote: > Some additional info... > > AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS > team, not by AWS. Details and suggestions to contact this list for > assistance are published at both https://wiki.centos.org/Cloud/AWS and > https://wiki.centos.org/Cloud/AWS > > Basically, the maintainer of the Centos.org

Hi all, the current AWS Marketplace CentOS7 AMIs (1602) are restricted to an outdated subset of EC2 instance types (at least m4.16xlarge and x1.* are missing). The AMIs are also based on 7.2.1511, which is now quite outdated. Are there any concrete plans to update the AMIs? Is this due to a lack of time, or are there other roadblocks that prevent an update? Cheers, Kad

Hi list, I've noticed that instance-backed AMIs no longer seem to exist for the 'official' CentOS images, though the EBS ones are fine.. Looking at the wiki (http://wiki.centos.org/Cloud/AWS), the AMIs listed on marketplace are slightly newer than what's listed on the wiki, so just wondering if something got overlooked after the last build? Cheers, -- Richard Clark richard at

Hi, We have noticed that the CentOS 7 AMIs in AWS do not delete their root volumes on termination. It appears this is the way that the AMIs were created. The AWS Linux AMIs appear to have this enabled. So they do delete their root volumes on termination. Does anyone know why the CentOS AMIs are created so that they don't delete their root volumes on termination? Herc

Hello all, and thank you very much for the Centos 7 HVM AMI [1], greatly appreciated! This AMI does not work on the newly launched AWS Frankfurt region (eu-central-1). Any plans for fixing that? According to the AWS announcement [2], "The Region supports all sizes of T2, M3, C3, R3, and I2 instances". (We'll be running the CentOS 7 HVM AMI going forward, but looks like none of

You can always build your own, no? (Sent from iPhone, so please accept my apologies in advance for any spelling or grammatical errors.) > On Feb 2, 2017, at 5:28 PM, Kadrach <kadrach at gmail.com> wrote: > > Hi all, > > the current AWS Marketplace CentOS7 AMIs (1602) are restricted to an > outdated subset of EC2 instance types (at least m4.16xlarge and x1.* > are

Hi there, Long-time user of CentOS 7 AMIs from the AWS Marketplace. I see that the latest CentOS 7 and all CentOS 8 AMIs are only available outside of the Marketplace ("These images are published outside of the AWS Market Place and are shared directly" - https://wiki.centos.org/Cloud/AWS) I'm really keen to understand if this is short-term situation, or if this is the indefinite

I'm trying to automate identification of CentOS AWS images. It appears that official CentOS AMIs have an OwnerID value of 410186602215, but I'm not sure if that value is transient or specific to one or more AWS regions. Is there a maintainer lurking here that can confirm or deny? Here's the base query I'm testing: aws ec2 describe-images \ --owners 410186602215 \

Hi, I'm running CentOS 6.2 x86_64 as xen guest on a CentOS 5.7 dom0. The host is running 2.6.18-274.7.1.el5xen, the guest 2.6.32-220.2.1.el6.x86_64. Memory for domU is set to 1024 MB and "xm list" shows these 1024 MB. But "free -m" on the guest system shows only 652 MB. When I set up a CentOS 5.x guest with 1024 MB "free -m" shoes 1024 MB. Anyone else seeing

Hi, I'm VNCing into my KVM server and opening virt-manager. When trying to manage a newly created guest, I'm finding the mouse pointer stays on the outside of its virtual machine window. Any insight as to why its tracking so oddly? Thanks in advance, - aurf

We've been using CentOS 5 with Xen on our machines for a while now and have really grown to appreciate it. The lack of Xen for Centos 6 is the reason we haven't upgraded yet, but with Xen4CentOS6 we have all the tools we need. The concern some of are having is that when CentOS7 comes out, which will be probably less than a year, is that Xen support for CentOS6 will evaporate. I know this

Just want to let you guys know that, although it may have been around for a bit, bringing Xen back to CentOS is awesome and I really appreciate it. I was very disappointed when RedHat dropped support as Xen is awesome. Thanks for the effort!

Hi folks, I had a few questions in regards to the CentOS AMI: Are there instance backed versions of the AWS marketplace CentOS builds? It looks like there might have been at one point, but I'm not seeing them now, and since they're marked as being from the marketplace we're having some difficulties attaching the volumes to another system to create an instance backed version of it.

Hi, I'm seeing some strange behavior when trying to use the latest CentOS 7 AMI from the AWS marketplace. The AMI that we've been using previously is "ami-02eac2c0129f6376b" released January 30, 2019 at 6:40:58 PM Today I saw a new AMI with ID "ami-0c3b960f8440c7d71" that was released February 21, 2020 at 3:50:07 Both these AMIs are owned by AWS account

Hi, I'm working on building a cluster on AWS atop CentOS 7. For development, I've been working in the eu-west-1 (Ireland) region, where the AWS MarketPlace provides an official CentOS 7 AMI (ami-e4ff5c93). However, the production deployment is taking place in AWS's GovCloud region for regulatory reasons, and there, I couldn't find an official CentOS 7 AMI. Are there plans to

I, Just wondering if anyone was able to look at this option with the current images or could share some tips on copying the image to another AWS account so we can use EBS encryption on the volume without tainting the image too much? Thanks. Andrew. -----Original Message----- From: Andrew Hodgson Sent: 27 July 2017 15:09 To: centos-virt at lists.centos.org Subject: Copying CentOS AMIs for EBS

Hi All, It's very helpful that CentOS release official AMIs in AWS EC2 marketplace. However, compare to official RedHat Linux and Amazon Linux AMIs in EC2, current official CentOS AMIs in marketplace does not support cloud-init or user-data scripts. which means that these AMIs doesn't support automation and dev-op operations. Since AWS CloudFormation also leverage user-data for initial

Hi, I am trying to copy the latest CentOS image to my own AWS account so that I can enable EBS volume encryption. It currently looks like the option when sharing the image is not enabled to allow direct copying of the snapshots, and I am wondering if this could be looked at? I can start an instance with this AMI, then create a new snapshot for the purpose of enabling EBS volume encryption, but