Working with AWS EC2 Autoscaling Group and AWS Codedeploy

PublishedSeptember 10, 2020

•2 min read•View as Markdown

Working with AWS EC2 Autoscaling Group and AWS Codedeploy

Ujang Mumu

Infrastructure Developer

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Preserving Client IP in Nginx Ingress Controller with AWS NLB

Prerequisite Install AWS Load Balancer Controller: This controller is essential for managing AWS load balancers in a Kubernetes environment. Step 1: Enable Proxy Protocol in NLB Target Group Add the following annotation to your NLB Target Group to...

Nov 12, 20231 min read408

Preserving Client IP in Nginx Ingress Controller with AWS NLB

Reduce Your AWS NAT Gateway Costs with alterNAT

AWS Managed NAT Gateway is a widely-used service that provides seamless internet access for resources within a private VPC subnet. However, its cost structure has been a pain point for many AWS users, with high fees for both hourly usage and data pro...

May 7, 20233 min read659

How to Set Up NTP on Ubuntu in AWS

Configure NTP in timesyncd.conf echo "NTP=169.254.169.123" | sudo tee -a /etc/systemd/timesyncd.conf cat /etc/systemd/timesyncd.conf Enable the timesyncd.service sudo systemctl unmask systemd-timesyncd.service sudo apt install systemd-timesyncd ...

Feb 20, 20231 min read74

Fix Terraform error "Required 'compute.subnetworks.use'" on Creating Vertex AI Workbench / Notebook

Error waiting to create Instance: Error waiting for Creating Instance: Error code 7, message: Required 'compute.subnetworks.use' permission for

Jan 17, 20231 min read438

Fix Terraform error "Required 'compute.subnetworks.use'" on Creating Vertex AI Workbench / Notebook

Clockify API to Automate Tasks Tracking

automating time tracking for a more accurate record of time spent on projects

Jan 14, 20232 min read208

My Notes

12 posts

AWS Autoscaling Group

This thing started when we have some user-data that do and install a lot of things, especially on Windows, the booting alone could take up to 6 minutes. Often the instance couldn't catch up with the ELB health check and causing the instance stuck in the termination loop.

To overcome the issue, I decided to use the lifecycle hook at instance launch. I was adding these commands to my user-data to extend the time-out and signal the hook of the task completion.

record-lifecycle-action-heartbeat Docs

complete-lifecycle-action Docs

AWS Codedeploy

The new instance launch issue was solved then, but we found another issue when our CI/CD tool agent deploying a new application version to the Autoscaling group would make the instance unhealthy from the ELB health check. We didn't want to modify the health check threshold or the interval since it'd make the infrastructure not elastic enough and not scalable enough. We decided to go with AWS Codedeploy as our CD tool that has integration with ELB and Autoscaling Group.

AWS Codedeploy integrates with ELB to manage traffic control before and after installation.

AWS CodeDeploy integrates with EC2 Auto Scaling, which can deploy our revisions to the new instances automatically. So every new instance launch will be updated with the application revision that was most recently deployed.

So now we end up with two hooks since, under the hood, Codedeploy is using a lifecycle hook too to integrate with EC2 Auto Scaling

I found out that If hook 1 is executed firstly and takes default action CONTINUE, then hook 2 will kick in. If custom action is completed and continues the launch process bypassing the default action ABANDON, the instance will be launched, but if custom action is not successful, then it will terminate. So CONTINUE allows any other lifecycle hooks to complete.

Finally, we removed the initial hook and its related commands in user-data

Below is an excellent flow chart from the AWS blog that explains what happens with EC2 Auto Scaling with Codedeploy.

Thanks for visiting the blog.

See you in the next post.

Command Palette