Thanks Karol
My challenge with AWS EFS is waiting for it to be HIPAA/BAA certified. But good
to know it's a satisfactory option.
I like the aspect of not worrying about total storage space, in part why I was
looking at obox and S3 for the elastic scale.
------------------------------
Message: 5
Date: Sat, 10 Sep 2016 22:27:52 +0100
From: Karol Augustin <karol at augustin.pl>
To: dovecot at dovecot.org
Subject: Re: Use of obox2 and AWS S3
Message-ID: <1fbb9ac24386c29a92a320d2d1a399bd at augustin.pl>
Content-Type: text/plain; charset=US-ASCII
On 2016-09-01 2:59, Raymond Sellars wrote:
> Any one running a dovecot solution within AWS in general? Interested
> in best practice for the storage layer. Although NFS is possible its
> not really optimised for elastic cloud type hosting.
>
> Thanks
> Raymond
Hi Raymond,
I am using dovecot on EC2 instance with EFS storage backend. As the initial
performance is bad it scales pretty quickly with space used. So it handles
maildir storage very well. The latency is a little high but with indexes there
is no problem.
It works as NFS storage with unlimited space (8EB) and you pay for what you use.
So it turns out to be very cost effective as you do not have to worry about
reserving space.
For better performance you can keep indexes on ephermal storage or EBS, which
both have much lower access times.
As for 'elastic cloud type hosting' EFS store can be used by thousands
of instances in multiple AWS AZs at the same time, so it looks like it is
somehow optimized.
Best,
Karol
--
Karol Augustin
karol at augustin.pl
http://karolaugustin.pl/
+353 85 775 5312