Choose the orientation the Spotinst’s algorithm will lean towards.
Balanced - (Default) Optimize towards both continuity and cost-effective infrastructure - We highly recommend using this orientation
Availability - Optimize towards the continuity of your instances. Please note: no instance replacement will take place - not while replacing On-demand instances nor replacement of expensive Spot instances.
Cost - Optimized towards the most cost-effective infrastructure
Spot percentage - What % of instances of your target instance count should be launched as spot instances.
On Demand count - Out of your target instance count, how many instances should be launched as On-Demand/Reserved
Utilize Reserved Instances - If you own any reserved instances that are not utilized and matches the groups On-Demand or Spot instance type selected, our algorithm will prioritize their usage prior to launching spot instances.
Fallback to On-Demand - In the case of no available spot instances, this will enable the fallback to On-Demand instances.
Unit - Instance (default) or vCPU. Target, min, and max will represent the number of servers required or the number of vCPUs required. For example, if only one additional vCPU is required, a smaller instance size will be used to fulfill the requirement.
Draining Timeout - (Seconds) The time you would like to allocate for existing sessions to drain before spot termination or scaling.
Scheduling allows you to create time-based activities, using Cron Expressions in UTC time zone. For example; Cron Expression: 55 3 * * 1-5 Means: “At 03:55 on every day-of-week from Monday through Friday.”
You can verify your Cron expression via crontab.guru