Configuring ASGs by Tag to use the Compute Co-Pilot ASG
- You must have already configured the appropriate Lambda roles for Copilot as per these instructions
The new nOps feature Configure By Tag offers increased ease-of-use to users of Compute Copilot. Onboard your ASG to Copilot with Configure By Tag for the following benefits:
Integration with any IaC tool, such as Terraform.
Multi-configuration capabilities: Configure multiple ASGs at the same time with just a couple of clicks, for quick and easy onboarding.
Effortless Configuration: Configure by Tag feature helps clients who frequently modify Auto Scaling Groups (ASGs) save significant time. It eliminates the need to manually go to the nOps dashboard and reconfigure ASGs each time they create, destroy, or recreate ASGs. Tags are automatically managed, for a seamless and time-efficient process.
|Name of the Launch Template you created in the Compute Copilot ASG Dashboard
nops_copilot_max_spot_instances - Maximum number of Spot instances that Compute Copilot will place as part of your Auto Scaling Group
nops_copilot_max_spot_percentage - Maximum percentage of Spot instances that Compute Copilot will place as part of your Auto Scaling Group.
Note: if you delete the Compute Copilot Launch Template used in one or more ASGs, these ASGs will no longer be processed by nOps Compute Copilot.
Navigate to Compute Copilot -> Auto Scaling Groups -> Manage ASG Templates
Create ASG Template
Give the ASG template a unique name
Select the CPU architecture based on the AMIs of the ASG you are going to attach this template with
(Optional) Exclude unsupported instances for ENI Trunking
Choose the instance families, vCPU, and Memory suitable for your workload. From this pool, Compute Copilot will select the most optimal choice for price and stability.
Create and Copy the name of the template
Attach “nops_copilot_enabled = true” and “nops_copilot_launch_template_name = *name you have copied from above*” tags to your ASG
Optional tags are “nops_copilot_max_spot_instances” and “nops_copilot_max_spot_percentage”
After creating the ASG using IaC with the tags specified, within a few minutes the ASG will reflect a “connected” status with the all the appropriate information (template name, Spot percentage / number of Spot instances)
1. What happens to my ASGs if I delete the Launch Template in nOps Compute Copilot?
If you delete the Compute Copilot Launch Template used in one or more ASGs, these ASGs will no longer be processed by nOps Compute Copilot.
2. Why don’t I see Spot instances as soon as I create the ASG using IAC while leveraging Configure by Tag?
If a reliable and cheaper Spot is available in the Spot market and in the same AZ, it will take up to 30 minutes to see a Spot instance as part of your ASG.
3. Can I use both “nops_copilot_max_spot_percentage” and “nops_copilot_max_spot_instances” tags on the same ASG?
Yes, you can use both tags.
4. What happens if I don’t use either of the tags “nops_copilot_max_spot_percentage” and “nops_copilot_max_spot_instances” on my ASG?
If you don’t use either tag, by default, Compute Copilot will try to replace all your On-Demand instances as part of ASG to the Spot instancesBack to top Home