With this release, ELBAS will rely on launch templates instead of launch configurations. AWS has been pushing launch templates for awhile now, and they are perfect for this project.
We no longer need to update the ASG resource with the newly created launch configuration. We only need to create a new launch template version, then the ASG can simply be set to use the "$Latest" version and the new one will be automatically used.
We also don't need to concern ourselves with all of the different settings people use in their setups, such as instance sizing, public IP, monitoring, etc. All of that is now confined within each user's AWS account, we simply override the AMI ID on each deployment.
In addition, we now only rely on the aws-sdk-autoscaling and aws-sdk-ec2 gems, since version 3 of the SDK has modularized each AWS service. Less dependencies 👍
With this release, ELBAS will rely on launch templates instead of launch configurations. AWS has been pushing launch templates for awhile now, and they are perfect for this project.
We no longer need to update the ASG resource with the newly created launch configuration. We only need to create a new launch template version, then the ASG can simply be set to use the "$Latest" version and the new one will be automatically used.
We also don't need to concern ourselves with all of the different settings people use in their setups, such as instance sizing, public IP, monitoring, etc. All of that is now confined within each user's AWS account, we simply override the AMI ID on each deployment.
In addition, we now only rely on the
aws-sdk-autoscalingandaws-sdk-ec2gems, since version 3 of the SDK has modularized each AWS service. Less dependencies 👍