:cleaning::cleaning::cleaning::cleaning:Cloud Conformity detect:
Please refer to this sheet for list of Launch Configurations identified by Cloud Conformity : https://docs.google.com/spreadsheets/d/1s4cWdFz5Xo8FAH0Anwp_mVXh-D3jpwyL3hwik31AaIQ/edit#gid=1199657000
When your ASGs fail to launch new EC2 instances due to invalid (removed) AMIs, the scaling mechanism is unable to add compute resources to handle the load and this will cause a significant negative impact on your application performance. (See https://www.cloudconformity.com/knowledge-base/aws/AutoScaling/launch-configuration-referencing-missing-ami.html)
When your ASGs fail to launch new EC2 instances due to inactive (deleted) Security Groups, the scaling mechanism is unable to add compute resources to handle the traffic load and this will cause a significant negative impact on your application performance and can lead to downtime. (See https://www.cloudconformity.com/knowledge-base/aws/AutoScaling/launch-configuration-referencing-missing-security-group.html)
As a good practice, every orphaned Launch Configuration template should be removed for better management of your AWS Auto Scaling components. There are also multiple occasions where we hit launch configuration resource limit in tvlk-prod that block product team release. (see https://www.cloudconformity.com/knowledge-base/aws/AutoScaling/unused-launch-configuration.html)
Thank you.