New Amazon Cloud Features: Elastic Load Balancing, Auto Scaling and CloudWatch
Last week, Amazon released some extremely interesting services that extend the functionality of Amazon Elastic Clouds (EC2): Elastic Load Balancing , Auto Scaling and CloudWatch . If they were still free, it would be really cool! But about everything in order.
Imagine that you have several instances running in the Amazon cloud that perform the same task. Elastic Load Balancing allows you to automatically distribute incoming requests to specified instances. Moreover, it can detect fallen instances and automatically redirect traffic to workers, while non-working instances again fail, which of course greatly increases the reliability of the entire system. The balancer can work both within one zone (meaning the physical location of servers) and between instances located in different zones, which further increases the reliability of your system as a whole.
The Amazon balancer is also integrated with CloudWatch (read below), so the number of requests and the delay of requests are reported by CloudWatch in its report. Running a little ahead, it should also be noted that Elastic Load Balancing is quite friendly with Auto Scaling and can work together.
Of course, balancing can be done with the use of, for example, nginx , installed on one of the instances, but the reliability of such a solution will be lower, since when this instance falls, your entire system will fall.
')
A delicious opportunity that allows you to automatically increase or decrease the number of running instances, depending on the conditions you specify. You can configure that when the load on each instance in the group exceeds 70 percent, three more new instances automatically start up, and when the load decreases below 30 percent, the same number of instances automatically stop. Moreover, it is possible to set a waiting interval to prevent triggers in case of accidental short-term drops or load increases. All this is very convenient for servers experiencing uneven load during the day, when at night and in the morning the load is very low, and in the evening it becomes the maximum.
You can also configure Auto Scaling to support a fixed number of instances in a group. When one of the instances fails, a new one will automatically start running. When working together with the balancer described above, you can configure Auto Scaling so that when the response from the instance is delayed by more than, for example, 4 seconds during the 15-minute interval, new instances are automatically launched.
Service that supports monitoring and collecting data from selected working instances. Within a few minutes after the launch of CloudWatch for a given instance, it begins to collect and save the necessary data. CloudWatch can collect the following information: CPU utilization, read / write from disk, and instance network traffic. Remember that using CloudWatch automatically includes using Auto Scaling, described above. The collected data is saved for two weeks, even if the observed instances were already stopped.
Elastic Load Balancing will cost $ 0.025 per hour of operation of one balancer and another $ 0.008 will be charged for 1 GB of traffic from outside passing through the balancer. For 10 working instances and 100 GB of incoming traffic per month, you get $ 18 + $ 0.8 = $ 18.8 per month.
Auto Scaling is free for those using the CloudWatch service, that is, it works only with it. CloudWatch costs $ 0.015 per hour for each instance being monitored. For one instance, this is $ 10.8 per month.
In short, I also want to mention another new Amazon service: AWS Import / Export , which allows you to speed up the transfer of large amounts of data to and from Amazon Web Services. Import / Export transfers your data directly to or from storage devices using a high-speed internal network to bypass the Internet. At the moment, the service is in the limited beta stage. The main uses of its use:
So far, all new features work only in the American zone, but soon they promise to add them to the European one.
Elastic load balancing
Imagine that you have several instances running in the Amazon cloud that perform the same task. Elastic Load Balancing allows you to automatically distribute incoming requests to specified instances. Moreover, it can detect fallen instances and automatically redirect traffic to workers, while non-working instances again fail, which of course greatly increases the reliability of the entire system. The balancer can work both within one zone (meaning the physical location of servers) and between instances located in different zones, which further increases the reliability of your system as a whole.
The Amazon balancer is also integrated with CloudWatch (read below), so the number of requests and the delay of requests are reported by CloudWatch in its report. Running a little ahead, it should also be noted that Elastic Load Balancing is quite friendly with Auto Scaling and can work together.
Of course, balancing can be done with the use of, for example, nginx , installed on one of the instances, but the reliability of such a solution will be lower, since when this instance falls, your entire system will fall.
')
Auto scaling
A delicious opportunity that allows you to automatically increase or decrease the number of running instances, depending on the conditions you specify. You can configure that when the load on each instance in the group exceeds 70 percent, three more new instances automatically start up, and when the load decreases below 30 percent, the same number of instances automatically stop. Moreover, it is possible to set a waiting interval to prevent triggers in case of accidental short-term drops or load increases. All this is very convenient for servers experiencing uneven load during the day, when at night and in the morning the load is very low, and in the evening it becomes the maximum.
You can also configure Auto Scaling to support a fixed number of instances in a group. When one of the instances fails, a new one will automatically start running. When working together with the balancer described above, you can configure Auto Scaling so that when the response from the instance is delayed by more than, for example, 4 seconds during the 15-minute interval, new instances are automatically launched.
Cloudwatch
Service that supports monitoring and collecting data from selected working instances. Within a few minutes after the launch of CloudWatch for a given instance, it begins to collect and save the necessary data. CloudWatch can collect the following information: CPU utilization, read / write from disk, and instance network traffic. Remember that using CloudWatch automatically includes using Auto Scaling, described above. The collected data is saved for two weeks, even if the observed instances were already stopped.
Issue price
Elastic Load Balancing will cost $ 0.025 per hour of operation of one balancer and another $ 0.008 will be charged for 1 GB of traffic from outside passing through the balancer. For 10 working instances and 100 GB of incoming traffic per month, you get $ 18 + $ 0.8 = $ 18.8 per month.
Auto Scaling is free for those using the CloudWatch service, that is, it works only with it. CloudWatch costs $ 0.015 per hour for each instance being monitored. For one instance, this is $ 10.8 per month.
Conclusion
In short, I also want to mention another new Amazon service: AWS Import / Export , which allows you to speed up the transfer of large amounts of data to and from Amazon Web Services. Import / Export transfers your data directly to or from storage devices using a high-speed internal network to bypass the Internet. At the moment, the service is in the limited beta stage. The main uses of its use:
- Data migration
- Backup data saved in S3
- Sharing large amounts of data
- Disaster recovery
So far, all new features work only in the American zone, but soon they promise to add them to the European one.
Source: https://habr.com/ru/post/60425/
All Articles