On Oct 10, 2014, at 10:12 PM, Edward Ned Harvey (lopser) <lop...@nedharvey.com> wrote:
>> From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org] >> On Behalf Of Simon Lyall >> >> Any reason you are running a t1.micro instead of a t2.micro ? The t2's are >> cheaper (especially in US regions), have more RAM and CPU etc. > > Didn't know about t2 until today. And didn't consider changing the machine > type just because I heard of t2. Don't know what the difference is - When I > created the machine a year ago, t1 was the type available. Do I have to > destroy and recreate machines every year? Perhaps. One thing to note: t2’s are only available inside VPC’s. (Default VPC’s are acceptable.) This will be an issue for you, but probably not a huge one if it’s a singleton. As of Dec 2013, you can’t even get EC2 classic accounts, so you might as well learn to love the new world. Benefit: You can update what SG’s are attached to VPC systems. There are plenty of other differences, but most of them are shielded by Default VPC. However, if you’re using cloud formation, you should read carefully. And if you’re building boxes w/o CF, you should look at that, to help give you version controllable templates of your systems & builds. The only other acceptable way to do this these days is w/ custom scripts that call the SDK’s but are version controlled too. Using the Console to build systems is the same thing as using the shell to configure your systems. — and consider using a template engine (erb, etc) to process the cloud formation stack when you hit your pain point…. (Why yes, I’ve been working in AWS for the past year. Heavily.) Matthew Barr mb...@mbarr.net _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
