similar to: CentOS 6 + Updates (HVM) AMI Breaks on attached instance storage

Hello, list. Yesterday I tried changing the instance type of my c1.medium instances on AWS to c3.large and I wasn't able to do so. It looks like the official Centos AMI on market place is still not ready for c3.large. This is the error message I received: "The instance configuration for this AWS Marketplace product is not supported. Please see

Hello, We have launched some EC2 servers 6 month ago using the CentOS 8 MarketPlace AMI 47k9ia2igxpcce2bzo8u3kj03 ( https://aws.amazon.com/marketplace/pp/prodview-ndxelprnnxecs) Now we have migrated these servers to CentOS Stream 8. We can change the instance type of these servers until m6i and c6i Intel based CPU, but we cannot change the instance type to new ADM Epyc c6a and m6a. There is an

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

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, the updated Amazon Web Service AMI (ami-4ac6653d) has a serious bug. It is not possible to resize a disk after creating a new volume with a size greater than 8GB. resize2fs does nothing. The previous AMI worked perfectly but is no longer available. This bug is a show stopper for using CentOS on AWS. Regards, Thorsten PS: It would also be great to have a CentOS 6 AMI with HVM

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

This is an automated email from the git hooks/post-receive script. arrfab pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new d2b87a3 Reflected new 7.9.2009 release and updated AMI IDs for AWS d2b87a3 is described below commit d2b87a32dda9b2e3b16ad2a55343ae63d000a64d Author: Fabian Arrotin <arrfab

Is there any chance we could get a PV AMI for CentOS 7 to match the HVM version at https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8&sr=0-2&qid=1442957668341 We have prepurchased reserved instances based on older PV machines (m1, c1, etc) It would be very very helpful to have a PV AMI so we could migrate to CentOS 7 on those image types.

This is an automated email from the git hooks/post-receive script. arrfab pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new 34ad21c Updated page for AWS AMI images ID and link 34ad21c is described below commit 34ad21c7bdf8b4190fed5ab9facc149199598da2 Author: Fabian Arrotin <arrfab at

Hi John On 07/09/16 15:50, John Peacock wrote: > I have done that, but the point of the request is that we would like to > have an official upstream AMI that we can use as the basis for our > work. I'm guessing that the reason for the blacked out instance type is > that early 6.x kernels didn't have the patches necessary to support 36 > vCPU's present in the

On Sep 23, 2015, at 9:03 AM, Karanbir Singh <mail-lists at karan.org <mailto:mail-lists at karan.org>> wrote: >> On 22/09/15 22:37, Jo Rhett wrote: >>> Is there any chance we could get a PV AMI for CentOS 7 to match the HVM version at https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8&sr=0-2&qid=1442957668341

On Sep 23, 2015, at 9:03 AM, Karanbir Singh <mail-lists at karan.org> wrote: > On 22/09/15 22:37, Jo Rhett wrote: >> Is there any chance we could get a PV AMI for CentOS 7 to match the HVM version at https://aws.amazon.com/marketplace/pp/B00O7WM7QW/ref=srh_res_product_title?ie=UTF8&sr=0-2&qid=1442957668341 >> >> We have prepurchased reserved instances based on

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

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

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

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

When launching CentOS Stream for aarch64 in us-east-1 using the CentOS-sponsored AMI (ami-0a311be1169cd6581, found at https://wiki.centos.org/Cloud/AWS <https://wiki.centos.org/Cloud/AWS>) I am able to launch the EC2 instance using a Gravitron2 processor, as expected. However, when attempting to login to that instance, I get a password prompt for the ec2-user, centos, and root users. This

On 28/09/15 14:55, Patrick Varilly wrote: > 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,

Hello Folks, I am looking for official centos 6 x86_64 AMI's for the Singapore region. I found an ebs backed Centos image from http://wiki.centos.org/Cloud/AWS (ami-3e22616c) in the market place <https://aws.amazon.com/marketplace/ordering/ref=dtl_psb_continue?ie=UTF8&pr oductId=adc4348e-1dc3-41df-b833-e86ba57a33d6&region=ap-southeast-1> . However I am unable to find

Getting this API error trying to launch CentOS 7 (x86_64) - with Updates HVM AMI with AWS c5.large instance type in us-west-2: ==> amazon-ebs: Error launching source instance: InvalidParameterCombination: Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'c5.large' instance type. Ensure that you are using an AMI that is enabled for ENA. AMI ID