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

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.
主站蜘蛛池模板: 阳朔县| 怀远县| 喀什市| 桂平市| 城固县| 临桂县| 鱼台县| 石景山区| 泾阳县| 扎赉特旗| 盐城市| 资溪县| 四川省| 益阳市| 虞城县| 盈江县| 昔阳县| 武山县| 会东县| 古蔺县| 丰县| 阿图什市| 潜山县| 贺州市| 灵璧县| 祁阳县| 万州区| 分宜县| 赣州市| 红安县| 德江县| 博白县| 琼中| 西安市| 囊谦县| 大港区| 永顺县| 兴城市| 黄龙县| 青海省| 怀化市|