我们应该在生产中使用什么AWS配置？
我一直在研究AWS。我似乎有点困惑。在上线之前，我们需要一个用于生产目的的单一盒子。它将具有 MySQL、SVN、Java 和一些其他自定义属性。
1) 如果我们只是开发而不是上线，我应该注册 AWS 的哪些功能。你能建议一个配置吗？我们现在希望将成本保持在尽可能低的水平。
2) 是否可以获得带有 SVN 和 MySQL 等预捆绑内容的实例？我在哪里看？
3) 如果我们只是开发，我应该选择什么实例类型？以下是我的选择： http://aws.amazon.com/ec2/instance-types/
4)预订和点播哪个对我们来说更具成本效益？我认为按需服务会很便宜，因为除了开发人员之外我们没有流量，但我喜欢保留实例让我提前知道我将花费什么。有人有这里的经验吗？
谢谢。
I have been researching AWS. It seems a little confusing to me. We want a single box for production purposes before we go live. It will have MySQL, SVN, Java, and a few other custom attributes.
1) What features of AWS should I sign up for if we are only developing - not live. Can you suggest a configuration? We are looking to keep our costs as low as possible right now.
2) Is it possible to get an instance with pre-bundled stuff like SVN and MySQL? Where do i Look?
3) What instance type should I be selecting if we are only developing? Here are my choices:
http://aws.amazon.com/ec2/instance-types/
4) Which would be more cost-effective for us - reserved or on-demand? I suppose on-demand would be cheap because we have no traffic other than dev stuff but I like that the reserved instances will let me know what I will be spending ahead of time. Anybody have any experience here?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
1) 您可能想从 EC2 开始。之后您可以查看例如 S3。
2) 是的，在 EC2 的AWS 管理控制台中搜索现成的 AMI（亚马逊系统映像）其中包含您需要预先配置的内容。
3）您可以从最便宜的微型实例开始。但请注意，它们只是 32 位的。当您觉得微型实例限制太多（需要更多内存或 CPU 能力）时，只需切换到小型实例类型即可。
4) 对于您的使用案例，了解预留实例是否比按需实例便宜的唯一方法是估计您预计在未来 1 或 3 年内消耗的每种实例类型的小时数，并比较以美元为单位的成本两个选项。如果您的开发实例整夜运行（即它们全天候运行），那么如果您确定将继续使用 AWS 至少 1 或 3 年，那么预留实例肯定会更便宜。
1) You probably want to start with EC2. After that you can have a look at for example S3.
2) Yes, in the AWS Management Console for EC2 search for ready-built AMIs (Amazon Machine Image) that contain what you need pre-configured.
3) You can start with Micro instances which are the cheapest. Note though that they are 32-bit only. When you feel Micro instances are too limiting (need more memory or CPU power), just switch up to the Small instance type.
4) The only way to know if Reserved instances are cheaper than On-Demand for your use case is to estimate the number of hours of each instance type you expect to consume during the next 1 or 3 years, and compare the cost in dollars of the two options. If your development instances are left running over night (i.e., they are running around the clock), then most certainly Reserved instances will be cheaper if you are sure you will keep using AWS for at least 1 or 3 years.
我想在 @Seppo 的 答案。
我不会从保留开始
实例。如果您预订了怎么办
实例然后结果是
不宜。首先测试一下（即使
它只持续几个小时）
正常的现收现付关税。你可以
轻松更改现有实例
稍后转移到保留实例。只是
通过购买预留实例，
您将更改您的账单费率
现有实例。
您不必为了节省资金而运行一整年（或 3 年）的预留实例。您无需预先支付整个期间的费用 - 只需支付押金 - 因此您只需运行几个月（取决于实例类型）即可实现收支平衡。
I want to add a few things to @Seppo's answer.
I would not start with a reserved
instance. What if you reserve an
instance and then it turns out to be
not suitable. Test it first (even if
its only for a few hours) on the
normal pay as you go tariff. You can
easily change the existing instance
to a reserved instance later. Just
by purchasing a reserved instance,
you will change your billing rate on
the existing instance.
You do not have to run a reserved instance for the full year (or 3) to save money. You are not paying for the entire period up front - only a deposit - so you only need to run it for a few months (depending on the instance type) to break even.