EC2 Instances Future

[Arthur Chance]

On 04/11/13 15:43, Michael Sierchio wrote:
> I have constructed several AMIs.  If I get a sense for which flavor of
> instance/OS combos are of interest, I can roll a few and make them
> available.

I'd be more interested in a step by step How To so I could roll my own.

I need to use EU instances because of data protection laws, and the 
Windows tax on micro instances in the EU is a huge 75%!

> On Wed, Apr 10, 2013 at 8:25 PM, Don O'Neil <lists at lizardhill.com> wrote:
>> Have you made any AMI's based on this method? I would love to deploy a
>> medium or large instance that isn't subject to the 'tax', but don't really
>> know where to start to build one like this.
>>
>> -----Original Message-----
>> From: owner-freebsd-questions at freebsd.org
>> [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of Michael Sierchio
>> Sent: Wednesday, April 10, 2013 1:05 PM
>> To: jflowers
>> Cc: freebsd-questions at freebsd.org
>> Subject: Re: EC2 Instances Future
>>
>> I still follow Colin's original pattern of using a minimal "Linux"
>> grub boot EBS device (1GB), ext2fs, with the root partition being on another
>> (ufs2) EBS device.  This works very well, with a couple of caveats -
>>
>> - Install e2fsprogs (pkg or port) - you will need it, on occasion when
>> modifying the boot device (after mounting rw).
>>
>> - Kernel upgrades are tricky, so be careful
>>
>> - Edit /etc/freebsd-update.conf intelligently to prevent unintended
>> consequences
>>
>> Apart from that, I have been running i386 and amd64 instances this way, both
>> 8.3 and 9.1, without difficulty (apart from some Xen clock weirdness in
>> 8.3).
>>
>> No Windoze Tax. ;-)
>>
>> - M
>>
>>
>> On Wed, Apr 10, 2013 at 10:05 AM, jflowers <jflowers at ezo.net> wrote:
>>> Is there anything likely to be available in the future (3 months to a
>>> year) to avoid the Windows tax on FreeBSD instances for the smaller
>>> (t1.micro, m1.small, m1.medium) types?  I understand the problem but
>>> don't find anything much online about a possible solution.  Probably
>>> because I don't understand as much as I think.
>>>
>>> Thanks.
>>>
>>> --
>>> Jim Flowers <jflowers at ezo.net>