LeanerCloud / AutoSpotting

Saves up to 90% of AWS EC2 costs by automating the use of spot instances on existing AutoScaling groups. Installs in minutes using CloudFormation or Terraform. Convenient to deploy at scale using StackSets. Uses tagging to avoid launch configuration changes. Automated spot termination handling. Reliable fallback to on-demand instances.

Home Page:https://autospotting.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Does Autospotting support Graviton2 and Mixed Instance Policy?

bilalmughal opened this issue · comments

I don't know if it's the right place to ask this question but I feel this feature will not only takes the "AutoSpotting" a level above. And will help many others as well.
We can have multiple launch templates to allow instances with different CPU architectures (Arm and x86) to launch in the same Auto Scaling group.
We can achieve this with following cloudformation template snippet

MixedInstancesPolicy:
        LaunchTemplate:
          LaunchTemplateSpecification:
              LaunchTemplateId: !Ref LaunchTemplate
              Version: !GetAtt "LaunchTemplate.LatestVersionNumber"
          Overrides:
            - InstanceType: t4g.small
              LaunchTemplateSpecification:
                # Override template for Arm based CPU t4g.small
                LaunchTemplateId: !Ref LaunchTemplateArm
                Version: !GetAtt "LaunchTemplateArm.LatestVersionNumber"
            - InstanceType: t3a.small
            - InstanceType: t3.small

Since the mixed instance policy does not support LaunchConfiguration, so we are forced to use launch template here. And I was never able to make AutoSpotting work with the launch template anyways.

To sum up everything

  • Does Autospotting support Arm Based CPUs?
  • Does Autospotting fully support launch templates?
  • Does Autospotting work with MixedInstancesPolicy?