问题描述
我公司正在打造一个SaaS产品（PHP），需要一些磁盘空间，在第一1TB应该是足够了，但可能需要在未来更多的磁盘空间。
My company is building a SAAS product (PHP) that needs some disk space, at first 1TB should be enough, but it may need more disk space in the future.
1 - 展望AWS选项EBS解决方案似乎是一种可靠的选择。但是，如果我需要超过1TB？我现在就可以使用多个EBS卷，但话又说回来我还需要管理哪里哪里存储，因为大多数我的档案文件下一个文件夹中。
1 - Looking into AWS options the EBS solution seems like an reliable option. But if I need more than 1TB? I now that you can use multiple EBS volumes but then again I would also need to manage where the files where stored, since most of my files are under a single folder.
2 - S3可能是最好的解决办法，但我们需要重写所有的应用程序文件访问S3 API ...
2- S3 is probably the best solution but we would need to rewrite all the application file access to the S3 API...
3另外，如果我需要使用多个Web服务器进行负载均衡，我可以安装在多个EC2实例一个EBS卷？我supose这是不对的......
3- Also, if I need to use multiple web servers for load balancing can I mount a EBS volume in multiple EC2 instances? I supose this is wrong...
4 - 是一个很好的做法，以存储在EBS下实例存储的源文件（快于EBS我supose），内容的文件？还是应该一切都将在EBS存储？
4 - Is a good practice to store the source files under Instance Storage (faster then EBS I supose), and the content files on EBS? Or should everything be stored under EBS?
推荐答案
答3：不，你不能在同一时间安装在多个实例EBS卷。我相信也AWS不是NFS友好无论是在情况下，你要通过NFS挂载它们。
Answer to 3: No you can't mount an EBS volume on multiple instances at the same time. I believe also AWS is not NFS friendly either in case you want to mount them across NFS.
答4：使用实例存储只为你不在乎它消灭了，当你关机的实例信息。当然，它的速度更快，但它也更不稳定。
Answer to 4: Use Instance Storage just for information that you don't care if it's wiped out when you shutdown the instance. Of course it's faster but it's also more volatile.
有关存储我相信你应该使用从最快以下存储层次（还建议由Amazon）来最慢，从低容量的可能性更高容量的建筑师您的应用程序。
For storage I believe you should architect your app using the following memory hierarchy (also recommended by Amazon) from fastest to slowest and from possibility of lower capacity to higher capacity.
Instance Store -> EBS -> S3 -> Glacier
像@马克·贝克说，长期大量的数据增长，我只想建议坚持S3，并允许用户通过HTTP（或HTTPS），让亚马逊处理所有的负载均衡来访问它。 EBS和实例存储（按顺序）的多为短期的。
Like @Mark Baker said, for long term large data growth I would just recommend to stick to S3 and allow users to access it through http (or https) and letting Amazon handler all the load balancing. EBS and Instance store (in that order) are more for shorter term.
如果您正在使用EBS你可能会写一些自动化的移动数据从EBS到S3定期。
If you are currently using EBS you can probably write some automation that moves data from EBS to S3 on a periodic basis.
这是我在过去使用的另一种方法是安装使用 s3fs 和移动某些文件定期到S3只留下符号链接在EBS卷。
Another approach that I've used in the past is mounting your S3 bucket using s3fs and moving some of the files on a periodic basis to S3 leaving only symlinks in the EBS volume.
这篇关于亚马逊AWS EC2存储选项的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！