有人可以详细说明通过 Amazon Web Services 托管的这些基本概念吗？
我阅读了所有亚马逊文档，但我仍然感到困惑，或者我应该说对不同的术语不知所措。
我来自传统的网络托管环境，我唯一理解的概念是我拥有多少存储空间以及允许多少带宽。
以下是我迄今为止对亚马逊的了解以及我对亚马逊的很多疑问。
EC2 - 我假设有可以设置网络服务器 (IIS) 并运行 .NET 应用程序的实例吗？或者它已经为我设置好了？
EBS - 对于数据库？如果没有，我从哪里获得数据库服务器？数据库服务器（Sql server 2005或2008）是否已安装？什么是快照获取请求？和快照放置请求？
S3 - 这是做什么用的？我以为EBS是用于存储的，这里混淆了。为什么需要 S3？
弹性负载平衡 - 我认为负载平衡只是减轻 Web 服务器负担的一种方法。它如何与亚马逊合作？ “弹性”负载平衡是什么意思？
区域之间的数据传输 - 这是什么意思？以及如何控制数据传入和传出的区域？
我的要求如下
- 我需要一个 IIS 网络服务器来运行我的页面
- 我需要一个数据库服务器
- 我需要一个位置来存储我的文件（可以与 #1 位于同一“服务器”上吗）？
- 我需要数据库和文件服务器始终可恢复。 （我听说我们需要将其存储到 EBS 以避免数据丢失？）
- 如果一台 Web 服务器过载、执行缓慢，我需要将其切换到场中的另一台服务器。
- 如果流量激增，那么我需要一种方法来增加 CPU、内存等。很好地处理流量的能力（这是我假设的弹性的目的）
此外，我不太理解“如果你没有运行您的实例，请将其关闭，否则将会收费”。我将运行一个网站，最好是 24/7 保持运行。在什么情况下您有条件地启动或关闭实例？
[编辑]
您如何准确监控您的使用情况？所以你不会对几千美元感到惊讶吗？你可以给它加个帽子吗？我读过这样的故事：AWS 用户对 300 美元的账单或其他什么感到惊讶，因为他们在 Amazon 上没有太多托管服务，也没有任何流量密集型网站。
抱歉，我是“云”计算的新手。试图追上这里。
预先非常感谢
I read all over the Amazon documentations, but I'm still confused or should I say overwhelmed by the different terms.
I'm coming from a traditional web hosting environment where the only concept I understand is how much storage I have and how much bandwidth I'm allowed.
Here are what I understand so far about amazon and my questions about a lot of it.
EC2 - I assume are instances where I can set up my webserver (IIS) and run my .NET application? Or is it already setup for me?
EBS - For database? If not, where do I get the database server? Is the database server (Sql server 2005 or 2008) already installed? What is Snapshot Get Requests? and Snapshot Put Request?
S3 - What is this used for? I thought EBS is for storage, confused here. Why you need S3?
Elastic Load Balancing - I thought load balancing is just a way to alleviate the burdens on your web servers. how does it work with Amazon?
What do they mean by "elastic" load balancing?
Data Transfer between region - What does that mean? and how do you control which region the data transfers to and from?
My requirements are the following
- I need an IIS webserver to run my page
- I need a database server
- I need a location to store my files (can it be on the same "server" as #1)?
- I need the database and file servers to always be recoverable. (I heard we need to store it into EBS to avoid loss of data?)
- In case one web server is overloaded, performs slow, I need it to switch off to another server in the farm.
- If traffic spikes, then I need a way to increase CPU, memory, etc. The ability to handle traffic nicely (which is the purpose of elastic I'm assuming)
In addition, I don't really understand the concept of "if you are not running your instance, shut it down or else it will be charged". I will run a website which ideally is to keep it up 24/7. In what scenarios do you conditionally have the instances up or down?
[Edit]
And how do you exactly monitor your usage? So you don't get surprised with a couple thousands of dollars? can you put a cap on it? I read stories where AWS users got surprised by a $300 bill or whatever when they didn't have much hosted on Amazon nor have any traffic intensive sites.
Sorry, I'm a complete newbie to "cloud" computing. Trying to catch up here.
Thanks a lot in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您问了很多问题，但让我尝试提供一个高级概述：
You're asking a lot of questions, but let me try to provide a high-level overview:
我也许可以回答你的一些问题，但肯定不是全部。
EC2 是预先配置了许多不同选项的虚拟机。听起来你想要的是一个 Windows 实例。它们配备了许多不同的内存和 CPU 选项，具体取决于您认为您的应用程序需要什么。
EBS 基本上是容错文件系统。这是您放置文件的位置，包括数据库文件。
S3本质上是一个内容交付网络。一个 REST 友好的放置文件的地方。例如，如果您拥有的只是静态内容，您可以将整个内容放入 S3 存储桶中，而无需支付任何计算能力，只需支付存储和带宽费用（这很便宜）。
我应该补充一点，如果您愿意使用 EC2 实例来提供所有内容，则无需使用 S3。这都是一个选择的问题。
至于为什么要关闭一个实例——那是因为你没有使用它。例如，您将使用一个临时服务器在各种不同的场景中测试您的应用程序。您可以为每个场景使用不同的 EC2 实例，在您想要运行测试时启动它们，并在完成后停止它们。
至于 SQL Server，Amazon 提供的“预配置”EC2 实例之一包括已设置的 SQL Express。如果您不需要 SQL Express，那么我相信您将使用 SQL Server 许可证之一并将其安装在您的服务器上。
AWS 的伟大之处在于进入门槛非常低。只需几美元的投资，您就可以逛上一天，看看有什么可看的。当我第一次开始使用 AWS 时，我发现从小规模开始使用单个 EC2 实例很有帮助。只需打开 RDP 端口并连接即可。您很快就会有宾至如归的感觉，在云端拥有一台自己的机器。
让CDN和负载均衡的事情及时到来。
最后一点建议是，请记住您的 ESB 数据和实例必须位于同一区域。如果您在欧洲启动一台机器，并且您的 ESB 卷位于西雅图，那么您就不走运了。您必须将卷从一个区域移动到另一个区域（并且他们会为该数据传输收取一定费用）
I can perhaps answer some of your questions, but certainly not all.
EC2 are virtual machines preconfigured with a number of different options. It sounds like what you want is a Windows instance. They come with a number of different memory and cpu options depending on what you think your application will need.
EBS is basically your fault tolerant file-system. That is where you'll put your files, including your database files.
S3 is in essence a content delivery network. A REST friendly place to put files. For example if all you have is static content you could put the whole thing up in an S3 bucket, and not pay for any compute power, just storage, and bandwidth (which is cheap).
I should add, there is no need to use S3, if you are comfortable with using your EC2 instance to serve up all your content. Its all a question of options.
As to why would you shut off an instance -- that would be because you're not using it. For example, a staging server, that you would use to test your app, in a variety of different scenarios. You could have a different EC2 instance per scenario, start them when you want to run your tests and stop then when you're done.
As for SQL Server, one of the EC2 instances that Amazon offers "pre-configured" includes a SQL Express already set up. If you don't want SQL Express, then I beleive you'll have use one of your SQL Server Licences and install it on your server.
The great thing about AWS is the very low barrier to entry. For just a few dollars investment, you can poke around for a day and see what there is to see. When I first started with AWS I found it helpful to start small, with a single EC2 instance. Just open up the RDP ports and connect into it. You'll soon feel right at home, having a your own machine up in the cloud.
Let the CDN and load balancing things come in time.
On last bit of advice, is to remember that your ESB data and your instance must be in the same region. If you start a machine in Europe, and your ESB volume is in Seattle you're out of luck. You'll have to move your volume from one region to another (and they charge something for that data transfer)
这里的其他答案忽略了 EBS 和 S3 之间的一些重要区别。
S3 完全是按需付费。即您只需为您正在使用的存储和带宽付费。而使用 EBS，您需要预先决定您想要的 EBS 卷有多大，并且无论您实际使用多少数据，都需要支付全部金额。< /p>
单个 EBS 卷只能连接到一个 EC2 实例 - 您无法在多个实例之间同时共享它们。当然，这对您来说可能不是问题，但需要注意。它不是共享存储空间。另一方面，可以使用简单的 URL 从任何地方访问 S3 上的资源。
The others answers here have missed some important distinctions between EBS and S3.
S3 is completely pay-as-you-use. ie you only pay for the storage and bandwidth that you are using. Whereas with EBS you need to decide up front how big you want your EBS volume to be and you pay for the entire amount regardless of how much data you are actually using.
A single EBS volume can only be connected to one EC2 instance - you cannot share them simultaneously between multiple instances. Of course this may not be an issue for you, but its something to be aware of. Its not a shared storage space. On the other hand, resource on S3 are accessible from anywhere using a simple url.