Cloud for Beginners | AWS Cloud Practitioner Essentials Course | Part-6
Nephophilia Diary
I am on my journey to explore and deep dive into this fascinating cloud technology. I started to explore and understand the basic terms of cloud technology and came across the AWS Cloud Practitioner Essentials Course. The instructors in this course are Blaine Sundrud a Senior Instructional Designer, Morgan Willis a Senior Cloud Technologist and Rudy Chetty a Solutions Architect.
In the previous blog, we understood some of the fundamentals of Amazon EC2. In this blog which is Part 6 of my Cloud for Beginners Blog Series, we will learn and understand about Scaling Amazon EC2, Directing Traffic with Elastic Load Balancing and Messaging and Queuing.
We all love expanding our Horizons. The pursuit of expanding our horizons is an innate (inborn) human desire. Expanding one’s reach and scaling a business to serve a global audience is an aspiration shared by virtually every individual and organization. In today’s interconnected world, the desire to transcend geographical boundaries and provide services to a diverse spectrum of people is not just a dream but a strategic imperative.
Scaling a business for global outreach offers numerous advantages, including increased revenue potential, diversified customer bases, and access to new markets and opportunities. As technology continues to bridge gaps and facilitate global connectivity, the pursuit of scaling businesses to cater to the needs of many around the world remains a powerful driver of success and progress.
“What is meant by Scalability?”
Scalability involves beginning with only the resources you need and designing your architecture to automatically respond to changing demand by scaling out or in. As a result, you pay for only the resources you use. You don’t have to worry about a lack of computing capacity to meet your customers’ needs.
If you wanted the scaling process to happen automatically, which AWS service would you use? The AWS service that provides this functionality for Amazon EC2 instances is Amazon EC2 Auto Scaling.
Now Let us understand Amazon EC2 Auto Scaling
If you’ve tried to access a website that wouldn’t load and frequently timed out, the website might have received more requests than it was able to handle. This situation is similar to waiting in a long line at a coffee shop when there is only one barista present to take orders from customers.
Amazon EC2 Auto Scaling enables you to automatically add or remove Amazon EC2 instances in response to changing application demand. By automatically scaling your instances in and out as needed, you can maintain a greater sense of application availability.
Within Amazon EC2 Auto Scaling, you can use two approaches: dynamic scaling and predictive scaling.
Dynamic scaling responds to changing demand.
Predictive scaling automatically schedules the right number of Amazon EC2 instances based on predicted demand.
Mapping this to the Coffee Shop analogy, If customers increase at any point in time we have additional baristas to take out the burden and keep the customers Happy and Satisfied with their Orders. If the number of customers decreases then we reduce the baristas working in the Coffee Shop if needed and pay them only for the worked hours.
To scale faster, you can use dynamic scaling and predictive scaling together.
Suppose that you are preparing to launch an application on Amazon EC2 instances. When configuring the size of your Auto Scaling group, you might set the minimum number of Amazon EC2 instances at one. This means that at all times, there must be at least one Amazon EC2 instance running.
When you create an Auto Scaling group, you can set the minimum number of Amazon EC2 instances. The minimum capacity is the number of Amazon EC2 instances that launch immediately after you have created the Auto Scaling group. In this example, the Auto Scaling group has a minimum capacity of one Amazon EC2 instance.
Next, you can set the desired capacity at two Amazon EC2 instances even though your application needs a minimum of a single Amazon EC2 instance to run.
If you do not specify the desired number of Amazon EC2 instances in an Auto Scaling group, the desired capacity defaults to your minimum capacity.
The third configuration that you can set in an Auto Scaling group is the maximum capacity. For example, you might configure the Auto Scaling group to scale out in response to increased demand, but only to a maximum of four Amazon EC2 instances.
Because Amazon EC2 Auto Scaling uses Amazon EC2 instances, you pay for only the instances you use, when you use them. You now have a cost-effective architecture that provides the best customer experience while reducing expenses.
Thank you for reading my blog so far. Give it a Like if you loved it and stay tuned for more blogs.
To learn more about Auto-Scaling checkout the below link: