similar to: Enabling enhanced neetworking for CentOS 6 bqse images in AWS

This is not really a problem at all. when you launch your image for the first time, you can specify a larger / volume size and cloud-init-tools will take care of the rest. This is well documented in the AWS userguides. -- Kelly Prescott On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote: > I'm staring at the free CentOS images on AWS, and seeing that whoever > set those up elected to use a

to follow-up, I will give an example. Here is the listing for the official centos AMI: IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen BLOCKDEVICEMAPPING EBS /dev/sda1

I think the command-line is far more flexable then the GUI interface. I use ec2-api-tools, but the python boto stuff works virtually the same. On Thu, 30 Apr 2015, Nico Kadel-Garcia wrote: > On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott <kprescott at coolip.net> wrote: >> to follow-up, I will give an example. >> Here is the listing for the official centos AMI: >>

hi Guys, We've been waiting on the AWS-MP services ( therefore the CentOS images ) to become available in Sydney but thats not happened yet and the messages from AWS are still the same : 'soon'. In the interim, should we just go ahead and make them availble via our account ? Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key :

hi, ? CentOS 6.3 (x86_64) ? Release Media: https://aws.amazon.com/marketplace/pp/B00A6L6F9I ? CentOS 6.4 (x86_64) ? Release Media: https://aws.amazon.com/marketplace/pp/B00DGYP804 are now marked for and updated to run with the m3 and c3 instance types. I'm still working with the amazon crew to get the 6.5 images online and an automated pipeline proposed ( hopefully, also adopted ) to get

On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott <kprescott at coolip.net> wrote: > to follow-up, I will give an example. > Here is the listing for the official centos AMI: > > IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS > HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace > available public [marketplace:

https://forums.aws.amazon.com/thread.jspa?messageID=481859&#481859 https://forums.aws.amazon.com/thread.jspa?messageID=453572&#453572 This is a timebomb waiting to strike so many people who like do daily snapshot backups and keep them for few weeks and not realizing their snapshots are useless if they had accidentally mess up some boot related file earlier on. Another scenario you mess

On 05/04/17 14:56, John Peacock wrote: > > We want to be able to usethe 10G networking that c4.8xlarge instances > provide and we want to base all of our images directly on the official > Centos6 release AMI. > Can you try ami-500d8546 i us-east-1 and let me know if that works for the c4.8large ? I've asked, a few times, for the CentOS Linux images in AMP to be enabled for

I asked back in September: https://lists.centos.org/pipermail/centos-virt/2016-September/005219.html and again in November: https://lists.centos.org/pipermail/centos-virt/2016-November/005257.html about getting c4.8xlarge enabled for the official image in AWS Marketplace: https://aws.amazon.com/marketplace/pp/B00NQAYLWO?ref=cns_srchrow Now that the 6.9 release is coming, it would be

hi guys, So it turns out that Sydney is too new a zone and not in the regular AWS image-production-pipeline. Although that should get fixed soon, in the mean time, should we go ahead and push images there ourselves ? - kb -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key :

I'm staring at the free CentOS images on AWS, and seeing that whoever set those up elected to use a partition for /dev/xvda1 rather than taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", etc. for each disk and use those directly as a file system. The result is that if you elect to allocate a larger base disk image, for example allocating 50 Gig to

Greetings! Can someone please explain the process for publishing CentOS 7 AMI's to AWS? I see the "official" CentOS marketplace page here: https://aws.amazon.com/marketplace/pp/B00O7WM7QW However, if I select us-west-2 and launch based on the current AMI that was released on 2/26/2016, I see that it is CentOS 7.2.1511 at boot up. Do new AMI's get published on a particular

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, why are larger AWS instances c5d.9xlarge and c5d.18xlarge (NVMe SSD attached) NOT supported by Centos7 AMI, while smaller instances (e.g. c5d.4xlarge) are supported? Also regular c5.9/18xlarge are supported. Thanks, Jens-Uwe Jens-Uwe Schl??ler -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, Can you please share a sample code which fetches the station list from the > Icecast server and can play a station. > I am attaching a very basic, bare-bone example in Python which: - fetches the XML file - converts it into a DOM object - loops over it, extracting for each station it's server name, URL, bitrate and genre. To play a URL, just feed it to the underlying player.

I tried to establish connection to my aws s3 account like this in my irb console - AWS::S3::Base.establish_connection!(:access_key_id => ''my access key'', :secret_access_key => ''my secret key'', :server => " s3-ap-southeast-1.amazonaws.com") And it works well and prompt this - => #<AWS::S3::Connection:0x8cd86d0

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 973d90a Added AWS as sponsor 973d90a is described below commit 973d90a1c09ad0ef6efdf200cc0e102f75442448 Author: Fabian Arrotin <arrfab at centos.org> AuthorDate: Tue Dec 3

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

On 04/12/2016 01:37 PM, Peter Steele wrote: > On 04/11/2016 11:33 AM, Laine Stump wrote: I wouldn't be too quick to > judgement. First take a look at tcpdump on the bridge interface that > the containers are attached to, and on the ethernet device that > connects the bridge to the rest of Amazon's infrastructure. If you see > packets from the container's IP going out

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