The smartest (often) way to run instances on AWS is to buy "reserved" instances - for either one or three years.
My goal here is to run the WordPress charm on t1.micro instances as per the default setup recommended (4 or 5 instances, for memory). It would make the most sense to use reserved instances, to ensure my costs are the lowest they can be.
Now, I have two issues:
juju 0.7 (I've not tested the Go version) doesn't like t1.micro instances and appears to lose contact with them after AWS instantiates them. There are others reporting the same thing.
If I've pre-reserved a number of instances, how do I "hard-code" these into juju's settings to ensure they are used in the environment, rather than "randoms"?
If I can crack the code on this, then I'm off and running!!