These are times where many companies are focusing on the basics of their IT operations and are asking themselves how they can operate more efficiently to make sure that every dollar is spent wisely. This is not the first time that we have gone through this cycle, but this time there are tools available to CIOs and CTOs that help them to manage their IT budgets very differently. By using infrastructure as a service, basic IT costs are moved from a capital expense to a variable cost, building clearer relationships between expenditures and revenue generating activities. CFOs are especially excited about the premise of this shift.


  1. The pay-as-you-go model。对于这种效率有显着的优势,因为只有一个实际消耗的资源只付钱。如果沿权利收入的申请量表产生尺寸,则这些成本将符合所产生的收入。

  2. Managing peak capacity。Many IT organizations need to maintain extra capacity for anticipated peak loads, capacity that sits idle for most of the time. These peak loads can be driven by customer demand such as in the online world, but it can also be capacity required to execute essential IT tasks such as periodic document indexing or business tasks such as closing the books at the end of a quarter. This is often the first step that our enterprise customers take to become familiar with using infrastructure as a service. After successfully running some of their peaks jobs they will then starting moving more permanent processing into the cloud.

    A great example in the online world is the Indy 500 organization that normally runs 50 servers to serve their customers, but during the races move all of their processing into Amazon EC2 to handle all traffic no matter how many hundreds of thousands of customers show up at the same time. The savings for the Indy IT budget during the races this spring was over 50%.

  3. 成本较低的可靠性更高。使用不同的数据中心和网络提供商协商几个合同,以确保IT任务可以生存复杂的故障情景是一项艰巨的任务,许多组织发现很难以成本有效的方式实现这一目标。亚马逊EC2与其区域和可用性区域为客户提供了在单个定价模型中获得具有高度冗余网络功能的多个高端数据中心,而无需任何谈判。



But we have learned at Amazon that having a low cost infrastructure is only the starting point of being as efficient as possible. You need to make sure that your applications will make use of the infrastructure in an adaptive and scalable manner to achieve a high degree of efficiency. In the Amazon architecture being incrementally scalable is key. This means that services' and applications' main course of action to handle increasing load or larger datasets is to grow one unit at a time. A more precise definition can be found这里

All services at Amazon are built to be horizontally scalable. An efficient request routing mechanism delivers requests to services in a manner that optimizes performance at a certain efficiency point. Capacity is acquired and released on short time frames to handle increase and decreases in resource usage. To achieve this principle of automatic scaling our services there are four basic components that need to work together:

  1. Elastic Compute Capacity。The basic resources required to execute our services and applications need to be able to grow and shrink at a moment's notice in a fully automated fashion. This is the fundamental premise behind Amazon EC2; whenever an Amazon service requires additional capacity it can use a simple API call to acquire additional capacity without any interference from operators or data techs, and can release it when no longer needed.

  2. 监测。我们无处不能衡量每种可能的资源使用参数,每个应用柜台和每个客户的体验。每秒监控数据的许多千兆位通过亚马逊网络持续流动,以确保我们的客户在他们期望和效率级别的级别进行服务。我们真的不在乎对平均值或中位数,因为我们在99.9百分位数的绩效,这对于确保所有客户提供正确的经验非常重要。

  3. Load balancing。使用我们使用多个算法智能地路由请求的监视信息,以提供具有预期性能的响应的服务实例。实际上平衡负载是请求路由系统的二级任务,因为它是客户的经验,我们最具驱动。优化任务是在最佳资源利用率下提供正确的客户体验。

  4. 自动缩放。Using Monitoring data, Load balancing and EC2, the auto-scaling service monitors service health and performance, brings more capacity on-line if needed or reduces the number of instances to meet efficiency goals. It spreads instances over multiple availability zones and regions to achieve the desired reliability guarantees. All without interference of developers or operators.


scale LB monitoring



他们将首先在私人测试版中发布,您可以express your interest在AWS网站上的该程序。在帖子上可以找到更多细节Amazon Web Services blog

Graphic by Renato Valdés Olmos of后岗位