AWS Auto Scaling: Scaling and Load Balancing Essentials

Here is a summary of the text in detailed bullet points:

• Before AWS Auto Scaling, enterprises had to purchase infrastructure upfront, which was a one-time cost, and they had to manage the infrastructure themselves, which was a burden.

• With AWS Auto Scaling, the application performance is maintained based on user requirements at the lowest possible price, and the cost optimization is achieved through automatic scaling.

• AWS Auto Scaling is a service that helps users monitor their applications and servers, and automatically adjusts the capacity of their infrastructure to maintain steadiness.

• The benefits of Auto Scaling include better fault tolerance, better cost management, reliability, scalability, and flexibility.

• Snapshots are backups of a single EBS volume, whereas AMIs are backups of an EC2 instance only.

• Snapshots are non-bootable images on EBS volumes, whereas AMIs are bootable images on EC2 instances.

• Creating an AMI image also creates EBS snapshots.

• To use AWS Auto Scaling, users need to configure a single unified scaling policy for application resources, select the service to scale, and optimize for cost or performance.

• There are different scaling plans, including dynamic scaling and predictive scaling.

• Dynamic scaling guides the service on how to optimize resources for availability and price.

• Predictive scaling predicts future workload based on daily and weekly trends and regular forecast future network traffic.

• Load balancers are necessary with Auto Scaling to distribute the load across multiple instances.

• There are three types of load balancers on AWS: Classic Load Balancer, Application Load Balancer, and Network Load Balancer.

• Classic Load Balancer is a primitive load balancer that is based on IP address and TCP port, and does not support host-based routing.

• Application Load Balancer performs tasks at the application level, supports host-based and path-based routing, and is used for HTTP and HTTPS traffic routing.

• Network Load Balancer performs tasks at layer 4 of the connection level, routes TCP traffic, and is suitable for managing massive traffic and low latencies.

• To create an Auto Scaling group, users need to create a launch configuration, select an Amazon Linux AMI, configure details, and specify the key pair.

• Users can create a new security group with the SSH port opened and accessible from anywhere.

• The key pair is used with all instances that are part of the Auto Scaling group.

• Users can select an existing key pair or create a new one.

• After creating the launch configuration, users can create an Auto Scaling group, specify the group name, group size, network, and availability zones.

• Users can configure scaling policies, including scaling between a minimum and maximum number of instances, and specifying the condition for scaling up or down.

• Users can use Average CPU Utilization as a metric for scaling, and specify a target value as a threshold for scaling up or down.

• Users can add notifications using SNS (Simple Notification Service) and get notified when a new instance is initiated.

• Tags are not mandatory but can be used to identify instances or their purpose.

• After creating the Auto Scaling group, users can verify the instance details and see that the instance has been initiated automatically by the Auto Scaling group.