AFAIK AMIs are fixed. You make your instance as you like it, then run some special voodoo to save it off as an AMI. Later you can run the AMI, change it, build a new one, but that's a new one. Yeah anyone can do it.
I think this came up before and my only question is, what's the use case for this we're trying to answer? So far it sounds like a regular instance with a copy of a Mahout .jar. Is this meaningfully more useful for someone than simply providing the .jar? I can't exactly migrate from one Mahout AMI to another in any sense, when upgrades are provided -- AMIs aren't a mechanism for distributing a library. We're also not talking about providing a ready-to-go Hadoop cluster. And shouldn't. This is something Elastic Mapreduce is already great for. Once upon a time I wrote an AMI that would fire up, automatically download data from a location, run recommendations, upload them, and quit. Pretty simple, pretty nice. *That* kind of thing I think is really useful. The AMI is like one big remote method invocation. On Mon, Jan 18, 2010 at 3:26 PM, Grant Ingersoll <[email protected]> wrote: > > On Jan 18, 2010, at 10:20 AM, Robin Anil wrote: > >> Perfect!. We can have two ami's. Mahout trunk and mahout release version. > > Cool. I'll get my base AMI up (just as soon as I figure out the security > stuff) and then we can coordinate. Is it possible to have multiple people > "manage" an AMI so that the Mahout committers can reasonably take on keeping > them up to date? > > -Grant
