Amazon EC2 注意事项 - 冗余和弹性 IP
我的任务是确定我们是否应该将电子商务网站迁移到 Amazon EC2。目前，我们使用 Amazon S3 来存储大量图像和文件。我们的主机成本将增加约 20 美元/月，但我们可以以几千美元的价格出售我们的服务器。这一切都是因为如果我们的服务器发生问题，目前还没有适当的程序。
亚马逊 EC2 的可靠性如何？冗余是否良好，我在常见问题解答中没有看到任何相关内容，这是我们当前系统上的一个问题，我正在寻求解决。
弹性IP有好处吗？听起来您可以将 DNS 指向该 IP，然后在 Amazon 端将该 IP 地址重新路由到任何 EC2 实例，这样如果第一个实例失败，您就可以轻松启动并运行另一个实例。
我知道可扩展性，我问的是冗余和可靠性。
I've been tasked with determining if Amazon EC2 is something we should move our ecommerce site to. We currently use Amazon S3 for a lot of images and files. The cost would go up by about $20/mo for our host costs, but we could sell our server for a few thousand dollars. This all came up because right now there are no procedures in place if something happened to our server.
How reliable is Amazon EC2? Is the redundancy good, I don't see anything about this in the FAQ and it's a problem on our current system I'm looking to solve.
Are elastic IPs beneficial? It sounds like you could point DNS to that IP and then on Amazon's end, reroute that IP address to any EC2 instance so you could easily get another instance up and running if the first one failed.
I'm aware of scalability, it's the redundancy and reliability that I'm asking about.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
在工作中，我有大约 20-40 个实例在一年多的时间里一直运行。我认为我们已经收到来自亚马逊的 1-3 封警报电子邮件，建议我们终止并启动另一个实例（大概是因为他们正在检测底层硬件中可能存在的故障）。我们从来没有遇到过突然宕机的情况，这看起来相当不错。
弹性 IP 非常棒，并且是解决方案的一部分。另一部分是能够快速启动新实例。我了解到，您不应该关心实例的停机，更重要的是使用适当的负载平衡并能够快速启动商品实例。
At work, I've had something like 20-40 instances running at all times for over a year. I think we've had 1-3 alert emails come from amazon suggesting that we terminate and boot another instance (presumably because they are detecting possible failure in the underlying hardware). We've never had an instance go down suddenly, which seems rather good.
Elastic IP's are amazing and are part of the solution. The other part is being able to rapidly bring up new instances. I've learned that you shouldn't care about instances going down, that it's more important to use proper load balancing and be able to bring up commodity instances quickly.
是的，这非常好。如果您无法整合并发冗余（其中有多台服务器同时满足请求），那么使用弹性 IP 快速重定向到另一个 EC2 实例将是最大限度减少停机时间的一种方法。
Yes, it's very good. If you aren't able to put together a concurrent redundancy (where you have multiple servers fulfilling requests simultaneously), using the elastic IP to quickly redirect to another EC2 instance would be a way to minimize downtime.
是的，我认为从内部服务器迁移到亚马逊在经济上肯定很有意义。 EBS 支持的实例可确保即使计算机重新启动，瞬态内存也不会丢失。如果您的应用程序和数据层之间有明确的分离，并且可以将它们放在不同的机器上，那么您可以为数据构建更好的冗余。
例如，如果您使用 mysql，那么您可以考虑使用 Amazon RDS 服务 - 它为您提供高度可用且可靠的 MySQL 实例，完全托管（补丁等）。然后，通过负载平衡，通过拥有更多较小的实例而不是一个较大的实例，可以使应用程序层更具弹性。
您将节省的成本实际上是硬件维护以及构建灾难恢复所需的成本。
Yeah I think moving from inhouse server to Amazon will definitely make a lot of sense economically. EBS backed instances ensure that even if the machine gets rebooted, the transient memory is not lost. And if you have a clear separation between your application and data layer and can have them on different machines, then you can build even better redundancy for your data.
For ex, if you use mysql, then you can consider using Amazon RDS service - which gives you a highly available and reliable MySQL instance, fully managed (patches and all). The application layer then can be made more resilient by having more smaller instances rather than one larger instance, through load balancing.
The cost you will save on is really hardware maintenance and the cost you would have to incur to build in disaster recovery.