3 ms·
Having used both Marketplace AMIs and non-marketplace (community) AMIs, I find the Marketplace ones to be quite painful to use. I want my tools to be able to go
by helper 11y ago
Having used both Marketplace AMIs and non-marketplace (community) AMIs, I find the Marketplace ones to be quite painful to use. I want my tools to be able to go out and get the latest AMI automatically and launch that instance, but it is basically impossible to do this with things in the Marketplace. Amazon makes you jump through a bunch of hoops as if you are paying extra for this marketplace AMI even if it is provided for free.
The nicest experience I've had is with the Ubuntu community AMIs. Ubuntu keeps a listing of their official AMIs[1] and there is a JSON api that they provide so you can fetch that information programtically.
[1]: https://cloud-images.ubuntu.com/locator/ec2/ https://cloud-images.ubuntu.com/locator/ec2/
- cperciva 11y agoHuh. To me, "go out and get the latest release automatically" is terrifying; you should be testing new releases before you deploy them. It would be simple enough to extract the AMI numbers from FreeBSD release announcements though; the main reason I encourage people to use the Marketplace AMIs is that the AWS Marketplace provides useful statistics about how many instances are running.
- helper 11y agoMaybe "release" isn't the correct term. Ubuntu publishes new AMIs with the latest security patches quite regularly. When I spin up a new instance on say 14.04 I want it to boot with a fully patched kernel.