similar to: AWS EC2 - CentOS 6 + 7 AMIs for new g3.* instance types?

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

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 are not available in AWS MP (only the EBS ones are there). Still though, also the instance-backed AMIs are listed as published and available on your wiki: http://wiki.centos.org/Cloud/AWS I've seen that the same question was asked already before but I'm not sure the answer given actually covered the whole question:

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

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

I looked everywhere for information on how to install wine in the Amazon AWS cloud. Can somebody please point me to some working binaries and which AMI to use? And possibly some installation instructions? I'm just trying to run some simple Windows console applications (from MS-DOS)... nothing fancy. But wine just doesn't want to install or run in AWS. Surely many people have

I've created an EC2 AMI for AWS that essentially represents a CentOS 7 "hypervisor" image. I deploy instances of these in AWS and create an number of libvirt based lxc containers on each of these instances. The containers run fine within a single host and have no problem communicating with themselves as well as with their host, and vice versa. However, containers hosted in one

My wiki name: WarrenTurkal Page for addition: https://wiki.centos.org/Cloud/AWS Proposed addition: I would like to add a column for the product code for the CentOS images listed with AWS marketplace URLs. I use the product code for "CENTOS-7 x86_64" to find the AMIs to start hosts with that image in each region of AWS. Thanks, wt

On 04/01/2016 02:07 PM, Laine Stump wrote: > On 03/31/2016 06:43 PM, Peter Steele wrote: >> I've created an EC2 AMI for AWS that essentially represents a CentOS >> 7 "hypervisor" image. I deploy instances of these in AWS and create >> an number of libvirt based lxc containers on each of these instances. >> The containers run fine within a single host and

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

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

Hi I plan to host Asterisk instances on AWS/EC2 servers. Requirement is to run asterisk instance with transcoding (g.729 + g.711) and full recording. Number of concurrent calls expected are 500+. 2 instances will be configured for 100% redundancy. Heart beat will be used to determine active instance. How should I choose EC2 instance? How many vCPU, RAM should be selected? I am assuming that

On 22/02/16 22:58, Warren Turkal wrote: > My wiki name: WarrenTurkal > > Page for addition: https://wiki.centos.org/Cloud/AWS > > Proposed addition: I would like to add a column for the product code > for the CentOS images listed with AWS marketplace URLs. I use the > product code for "CENTOS-7 x86_64" to find the AMIs to start hosts > with that image in each

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 Jeff Are you aware of any challenges of hosting it on AWS? It will help me to work out alternate plan. Is there any recommendation? Should I split it to multiple instances and balance traffic across multiple small server instances? I can use Kamailio to balance traffic. I see many posts referring to AWS deployment. Please help me to choose AWS server instance. *Thanks & Regards,*

On 04/02/2016 05:20 PM, Laine Stump wrote: > You say they can talk among containers on the same host, and with their > own host (I guess you mean the virtual machine that is hosting the > containers), but not to containers on another host. Can the containers > communicate outside of the host at all? If not, perhaps the problem is > iptables rules for the bridge device the containers

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

On 04/11/2016 11:33 AM, Laine Stump wrote: > Interesting. That functionality was moved out of the kernel's bridge > module into br_netfilter some time back, but that was done later than > the kernel 3.10 that is used by CentOS 7. Are you running some later > kernel version? > > If your kernel doesn't have a message in dmesg that looks like this: > > bridge:

Digital ocean offers ssd on all the virtual machines. Uptime is good. Jai Rangi Www.didforsale.com www.cebodtelecom.com www.cebod.com > On Mar 8, 2015, at 8:11 AM, Jeff LaCoursiere <jeff at jeff.net> wrote: > > > Amazon instances are shared resources. I wouldn't want to count on timing or disk throughput, and you can't just ask them to do "ssd" - its a