I propose that we make the language stronger outlining the consequences of changing min vCPU. If a user changes that value, it will leave expensive instances running, accruing costs in their AWS accounts.
We could use language similar to what the Batch console states:
By keeping this set to 0 you will not have instance time wasted when there is no work to be run. If you set this above zero you will maintain that number of vCPUs at all times.
The place for this change would be in the CloudFormation template description of the minvCPU parameter so that it appears in the console when a user is deploying the solution.
I propose that we make the language stronger outlining the consequences of changing min vCPU. If a user changes that value, it will leave expensive instances running, accruing costs in their AWS accounts.
We could use language similar to what the Batch console states:
By keeping this set to 0 you will not have instance time wasted when there is no work to be run. If you set this above zero you will maintain that number of vCPUs at all times.The place for this change would be in the CloudFormation template description of the minvCPU parameter so that it appears in the console when a user is deploying the solution.