AWS AMI Questions

Home » CentOS-Virt » AWS AMI Questions
CentOS-Virt 4 Comments

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. Any ideas?

Is it possible to download the AMI from somewhere and re-upload them so they don’t have the Marketplace restrictions? I checked, but it seems like they files there haven’t been updated in a while.

It’s my understanding that

4 thoughts on - AWS AMI Questions

  • Hi CS,

    those are all good questions and I asked quite similar ones already half a year ago:

    And apart from me, also other people raised the same issue, e.g. here:

    Or here:

    Unfortunately, the situation appears to not have changed until today. So the AMIs seem to not be available outside the AWS marketplace, you can’t get any instance-backed AMIs from the AWS marketplace and you also cannot convert the EBS-backed AMIs from the marketplace to instance-backed AMIs on your own because of the marketplace product license restrictions.

    It would be a cool thing to have official, instance-backed CentOS AMIs for AWS. But somehow, I’ve lost hope a bit meanwhile…

    Best regards, Michael

    Quoting CS :

  • Hi,

    No, there are a couple of issues with the way we do the AWS Market Place setup that make this inconvenient. But hang in there, I’m working on an alternative! will be the right place, that is exactly the target that I am working to develop.

    You should be able to use that service as is ( the aim of projectraindrops is not to deliver open source software, but to deliver and maintain a service that just-works and has a reasonable feature spec ).

    The CentOS images are not built with it, the CentOS images are build in a replica install that runs inside the CentOS buildservices.


  • Thanks Karanbir!

    Just one comment about the raindrops project; having it as a closed source project that’s separate from the official CentOS project, and has no recognizable organization behind, makes it hard to use in any sizable company. Inevitably there would be questions about security and verification of what is in the build, risk of being dependent on a project that may or may not be around in a few years. If it were open source, or perhaps under the CentOS brand, that would make it easier to use. Just an fyi…


  • Hi,

    Couple of things : runs completely disconnected from CentOS Project – there is no resource overlap other than the fact that I wrote some of the scripts behind it – and I do the same for as well. That is by design. Couple of wins in there is that we can build Fedora and Debian images as well at Raindrops, which we cant in the private instance that runs inside the CentOS buildservices[1].

    Also, the code behind it is basically just libvirt running kickstarts that users submit in native hypervisors. so the only bit that isnt already visible is the web interface ( which is sinatra running a few tasks to prep data for virt-install ).

    Finally, one of the things that I want to get to is being able to download a project raindrops VM that is already setup for a target environ: eg. click a button to have your own instance come up in AWS/EC2
    or download something that can run as a in-cloud-off-premise openstack vm or opennebula vm. I guess this is really what your request was about
    : and its something that is in the pipelines, blocker is mostly hours in a day, but I hope to have this done by the end of this year.

    Flipping over to the other side : AWS is a vendor environment, we try quite hard to not be a vendor specific effort and try to keep things as generic as possible. AWS for years refused to accept that CentOS was an entity or that CentOS images were in demand ( the first set of conversations I had with them was back in 2008… and it took till 2013
    to get that issue resolved ). In this case the resolution was them acknowledging that we exist, that the content we churn out is acceptable as is; essentially reducing ( but not removing ) the hostility that AWS
    has towards open source projects at large.

    And we on the other hand need to be careful about how we interface with them, and what that interface brings in and takes away from our side. After all, it might be a specific vendor environment – its still quite a large one.

    Hope this helps clear up a bit more of the air,

    – KB

    [1]: Since CentOS buildsys has no inbound content, we could / would not be able to expose that interface in a manner that would allow other distro’s content to be consumed in a sane manner.