EC2 instance Autoscaling

UpdatedJanuary 16, 2024

•3 min read•View as Markdown

Lokendra Bhat

"Success is not final; failure is not fatal." I don't care if I fail or succeed; I never give up.

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Restore — What Happens After ddrescue Saves Your Data

"ddrescue got your data off the dying drive. Now what? This is where you actually get it back." 🚑 The Big Picture First A lot of people think ddrescue restores data. It doesn't — not directly. Here

Mar 29, 20268 min read

ddrescue — Your Data's Last Lifeline

"Your hard drive is making a clicking sound. Your stomach drops. Don't panic — ddrescue has your back." 🤔 What Even Is ddrescue? Imagine your hard drive is a library. Some books are fine. Some are

Mar 28, 202612 min read

Mastering SELinux: The Complete Guide for DevOps Engineers

Most teams treat SELinux as an obstacle. The teams that thrive in production treat it as a superpower. Here's everything you need to know to move from frustrated to fluent. If you've ever Googled a

Mar 27, 202613 min read

Application load balancer Demonstration

Application Load Balancer? A load balancer serves as the single point of contact for clients. The load balancer distributes incoming application traffic across multiple targets, such as EC2 instances, in multiple Availability Zones. This increases th...

Jan 15, 20245 min read

Lokendra

16 posts

Let's begin:

In EC2 -> Load Balancing session select Load Balancers and Create load balancer Select Application load balancer

Basic configuration

Load balancer name: WebELB
Select VPC: myVPC
Mappings: Select at least two AG so select both public subnets of different AG

Security groups

Security group: Select that you created to access HTTP

Listener and routing

Protocol: HTTP Port: 80
Create target group as:
- Target group name: web-app
- VPC: myVPC
  
  Next
- Register the targets session leave it as default and
  
  Create target group

-Go back to the load balancer tab, refresh, and select the target group that you created

Creating a launch template

In the EC2 left bar there is an instances section in which Launch Templates also select and create launch templates as:

Launch template name: webtemp
Template version description: For autoscaling use
Select Provide guidance to help me set up a template that I can use with EC2 Auto Scaling
Application and OS Images: select My AMIs and leave the default option
Instance type: t3.micro or other free tiers if exits
Key pait(login)-> Key pair name: don't include in the launch template
Network Settings-> Subnet: Don't include in launch template Firewall(security group): Select the existing security group and select that you created for HTTP access
Leave all defaults and Create launch template

Creating an Auto Scaling group

Choose the Launch template that we created and From Action dropdown select Create Auto Scaling group

Name ->
- Auto Scaling group name: Web Auto Scaling Group
- All Default and Next
Network ->
- VPC: myVPC
- Availability Zones and subnets: Select both private subnets
- Choose Next
Load balancing ->
- Select Attach to an existing load balancer
  - Existing load balancer target groups: Select web-app that you created
- Health checks:- Select Turn on Elastic Load Balancing health checks
- Choose Next
Configure group Size and scaling policies - optional
- -> Group size - optional
  - Desired capacity: 2
  - Minimum capacity: 2
  - Maximum capacity: 4
- -> Scaling policies - optional
  - Select Target tracking scaling policy
    - Metric type: choose Average CPU utilization
    - Target value: 50
    - Choose Next
Add notifications - optional
- Choose Next
Add tags - optional
- Choose Add tag Key: Name Value-optional: WebApp
Review and Create Auto Scaling group

Verify autoscaling

Select instances and you see there are 2 WebApp named instances are automatically created

Select Target Groups and select that you created above and observe health status -> healthy

Test auto-scaling configuration

When the Load of CPU utilization reaches 50%+ after a few minutes you should see your auto-scaling group add a new instance. This occurs because Amazon CloudWatch detected that the average CPU utilization of your Auto Scaling group exceeds 50% and your scale-up policy has been invoked in response. The maximum of 4 instances of name WebApp created according to policy. You can add more if needed.

EC2 instance Autoscaling

Comments

More from this blog

Restore — What Happens After ddrescue Saves Your Data

ddrescue — Your Data's Last Lifeline

Mastering SELinux: The Complete Guide for DevOps Engineers

Application load balancer Demonstration

You need to first create these for this lab:

Let's begin:

Have a great day!!!

Command Palette

Comments

More from this blog

You need to first create these for this lab:

Let's begin:

Have a great day!!!