官术网_书友最值得收藏!

Creating auto scaling groups 

So far, we have seen various services provided by AWS EC2. We have also seen the dynamic nature of the cloud that lets us spin any number of instances, volumes, load balancers, and so on.

When we deploy an application in production, we are likely to see non-uniform traffic patterns.

We might see a pattern where peak time starts at mid-afternoon and ends at midnight. For such cases, we might need to add more resources at certain times to keep our application latency uniform. Using auto scaling groups, we can achieve this goal. AWS EC2 provides three major components for auto scaling EC2 instances:

  • Launch Configurations act a template for auto scaling groups to launch EC2 instances. It contains information like the AMI ID, the security group, and so on required to launch an EC2 instance.
  • Auto Scaling Groups is a collection of EC2 instances which share similar characteristics. This is defined in the launch configuration. Auto scaling groups are configured with parameters such as a maximum number of instances, a minimum number of instances, scaling policies, and load balancers to manage EC2 instances.
  • Scaling Group Policies are policies attached to an auto scaling group, which define actions like scale up or scale down. These policies are hooked with CloudWatch metrics alarm, which notifies the policy to increase or decrease EC2 instances in auto scaling groups.
主站蜘蛛池模板: 三门县| 特克斯县| 阿荣旗| 理塘县| 灵寿县| 鹤岗市| 长汀县| 汉源县| 台北市| 泰来县| 榆树市| 清徐县| 清水河县| 广饶县| 肥城市| 胶南市| 富锦市| 阳江市| 新安县| 河北区| 永顺县| 东平县| 郧西县| 隆昌县| 托里县| 清丰县| 古蔺县| 平顺县| 句容市| 弋阳县| 福贡县| 海淀区| 宁都县| 岳池县| 全南县| 黎城县| 永平县| 枝江市| 廉江市| 固安县| 遂溪县|