Point 2 doesn't require a custom AMI if you don't want it to. You can do autoscaling with a virgin AMI and use user-data bootstrapping to get chef-client on there and running.
Details on my site here: http://www.trailhunger.com/blog/technical/2011/05/28/keeping-an-amazon-elastic-compute-cloud-ec2-instance-up-with-chef-and-auto-scaling/
Cheers,
EdwardOn Thu, Sep 13, 2012 at 9:15 AM, John Martinez < " target="_blank"> > wrote:
On Sep 13, 2012, at 9:01 AM, Daniel DeLeo < " target="_blank"> > wrote:On Thursday, September 13, 2012 at 7:46 AM, Maven User wrote:
Hi all -
With knife's ec2 plugin (which is awesome), I can create and instance from an ami, but I cannot go the other way.
The use case is this:
virgin ubuntu 12.X ami -> knife clone/bootstrap with our product -> create ami from this instance (for consumption elsewhere)
Before I start diving down this rabbit hole, is/was there a reason NOT to do this? Time? Or was there a technical reason? Does this feature exist and I don't see it?
Just curious, seems like a good feature to have but don't want to waste a ton of time if there was a technical reason NOT to do this.
Creating an AMI is an involved process. Most people only follow the pattern you describe when their initial chef-client runs take a prohibitive amount of time and they need really fast instance creation for things like autoscaling.Concur. From my experience, the two main reasons I use to create custom AMIs in AWS to use in conjunction with Chef:
- To cut-down on instance boot up time (as described by Daniel)
- You are using Autoscaling or CloudFormation where the knife API command can't be used
-john
Cloudreach Limited is a limited company registered in England with registered number 06975407 The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved. This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.
Archive powered by MHonArc 2.6.16.