Edit me

Configuring ASGs by Tag to use the Compute Co-Pilot ASG


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.


  1. You must have already configured the appropriate Lambda roles for Copilot as per these instructions

Integrate nOps Compute Copilot with your ASGs by adding the following Tags:

Tag Key Tag Value Required
nops_copilot_enabled true
nops_copilot_launch_template_name Name of the Launch Template you created in the Compute Copilot ASG Dashboard
nops_copilot_max_spot_instances Integer (0-N)
nops_copilot_max_spot_percentage Integer (0-100)
nops_copilot_replace_protected_instances True
nops_copilot_min_ondemand_number Integer (0-N)

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.

nops_copilot_replace_protected_instances: This tag allows ASG Lambda to replace the instances that have Scale-in protection or its instances are protected from Scale-in.

nops_copilot_min_ondemand_number: This tag sets the minimum number of On-Demand instances that should be left in the ASG. ASG Lambda won’t do any replacements (On-Demand to Spot) if it has less number of On-Demand instances than specified in the Tag value.

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.

Step-by-Step guide to Configure by Tag:

  1. Navigate to Compute Copilot -> Auto Scaling Groups -> Manage ASG Templates

  2. Create ASG Template

  1. Give the ASG template a unique name

  2. Select the CPU architecture based on the AMIs of the ASG you are going to attach the template to

  3. By default “Dynamic min VCpuCount & MemoryMiB” is checked, setting minimum vCPU and RAM requirements based on the size of the On-Demand EC2 instance being replaced. You can disable this option and set CPU or Memory suitable for your workload from the Instance Requirements list.

  4. (Optional) When selecting instance requirements, eligible instance families will be highlighted based on your criteria. To simplify the selection process, you can choose all highlighted options by clicking on the “Select All Eligible Instance Families” link.

  5. You can also directly choose the instance families. Compute Copilot will select the most optimal choice for price and stability out of the provided options.

  6. Create and Copy the name of the template

  7. Attach “nops_copilot_enabled = true” and “nops_copilot_launch_template_name = *name you have copied from above*” tags to your ASG 

  8. Optional tags are “nops_copilot_max_spot_instances” and “nops_copilot_max_spot_percentage”

  9. 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 instances

5. What happens if I don’t use the tag “nops_copilot_replace_protected_instances” on my ASG protected with Scale-In protection?

If you don’t use the tag, by default it is set to FALSE, so Compute Copilot will not replace protected instances due to Scale-In protection.

Managing Karpenter Configurations With nOps GitOps support
Managing Resources With Karpenter GitOps Support
Compute Copilot For ASG Support Matrix
Onboarding your Autoscaling Groups to nOps Compute Copilot
Onboarding your Autoscaling Groups to nOps Compute Copilot via Stackset
Configure Commitment Management
Compute Copilot for ECS
Onboarding your EKS clusters to Copilot for EKS Cluster Autoscaler
EKS Provisioner Examples
Compute Copilot for EKS - Karpenter Beta Support
Onboarding your EKS clusters to Compute Copilot for EKS Karpenter
Our Approach to Optimizing Commitment Utilization
Compute Copilot Spot Instance Reliability SLA
YAML file for nOps Commitment Management
Minimum IAM permissions for the nOps platform
IAM permissions for the nOps platform
IAM permissions for Essentials
Onboarding AWS Linked Accounts
Onboarding Multiple AWS Linked Accounts with CloudFormation
Onboarding AWS with Manual Setup-Contact Us
Service Control Policies
Onboarding AWS with Automatic Setup
Onboarding AWS with 1-click CloudFormation
AWS SSO Integration
Azure SSO Integration
SSO Integration
Okta SSO Integration
OneLogin SSO Integration
Back to top       Home
Tags: copilot