Applicability of Aminator for a particular usecase

[c.bala...@gmail.com]

Hi,

I would like to know if aminator can be used for my particular usecase. I maintain a project foo and I have an EC2 instance where foo is installed (using apt). I would like to automate the following, using a script.


1. Get the instance.
2. Run a command specific to foo on the instance.
3. Run apt-get update, apt-get install foo on the instance (to update foo to latest version. I can also provide a deb file directly, instead of using apt)
4. Create AMI from the instance and make it public
5. Copy the AMI to all regions and make all of them public.

Is all the steps described above possible with aminator? If not, can I know which all steps are possible?

For the remaining steps, what is suggested? SDK? DIrect API calls?

Regards
Balasankar C

[Brian Moyles]

Hi there,

If you're looking for something that works against a live instance and runs copyImage to turn that instance into an image, you're probably better off with something like Packer (https://www.packer.io/ ) instead of Aminator. Aminator's sole mode of operation today is to work against volumes through chroot.

Thanks!

Brian

--
You received this message because you are subscribed to the Google Groups "Aminator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aminator+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Richard Gooch]

Which is the hard part for you? Constructing the image content or publishing AMIs into multiple regions?

When you refer to making the AMIs public, do you mean as community images? Or available within your account? Are the AMIs encrypted or not?

You could use Aminator to build the image content and publish an AMI in the same account+region, but you'd have to change to the Aminator model (mounting a volume, chrooting into the volume and installing software). Do you really need to perform updates on a running system?

If you're stuck with updating a running system and once you have tooling to support that, you could use ami-publisher to upload your system contents and quickly publish AMIs globally. This would avoid the expense of having to stop the instance, snapshot+register and then start the instance again.
https://docs.google.com/document/d/1UL20UZuYvjyA1mVzU2jy9QFvflTaxJz5qOf643JG1EQ/pub

Regards,

Richard....