The best way to implement a NAS on AWS
If, for backwards compatibility reasons, you want something equivalent to a NAS on AWS, with the ability to have multiple read/write clients to a filesystem, what's the best solution? I could see connecting to a remote NAS over Direct Connect, running an NFS server backed by EBS volumes or ephemeral storage/S3, or something else. Obviously re-architecting the application is a far better option in the long run.
Option 1 (low availability, low scalability, low cost):
- 1 EC2 instance
- Multiple EBS volumes in a RAID0 or RAID10 configuration.
- NFS service for clients
Option 2 (medium availability, high scalability, high cost):
- Multiple EC2 instances (same region)
- Multiple EBS volumes per instance (again, RAID0 or RAID10)
- Gluster shared filesystem across all instances
- Gluster NFS service for clients
Option 3 (high availability, high scalability, very simple, very affordable)
- Zadara Storage
- NAS in the Cloud: http://www.zadarastorage.com/sol...
- Pricing: http://www.zadarastorage.com/pri...
Not an appliance but storage as a service inside the AWS EC2 cloud.
Option 4 (enterprise-grade NAS features, fully configured in 24 minutes)
- SoftNAS
- NAS-as-a-Service Network Attached Storage Software
- Free trial: Network Attached Storage Software
- Cross availability zone block replication
No comments: