[ecs] Step Scaling policy does not create all steps

I’m using the scaleOnMetric method of the FargateService construct. My requirements need 2 policies.

construct.scaling.scaleOnMetric('scale-up-policy', {
  scalingSteps: [
    {
      lower: 65,
      change: +2,
    },
    {
      lower: 85,
      change: +3,
    },
  ],
  metric: construct.service.metricCpuUtilization({
    statistic: 'Maximum',
    period: cdk.Duration.minutes(1),
  }),
  cooldown: cdk.Duration.minutes(2),
});

construct.scaling.scaleOnMetric('scale-down-policy', {
  scalingSteps: [
    {
      upper: 50,
      change: -1,
    },
    {
      upper: 40,
      change: -2,
    },
  ],
  metric: construct.service.metricCpuUtilization({
    statistic: 'Average',
  }),
});

However it never creates the 65 step. It only creates >85 step.

Reproduction Steps

• Create a FargateService
• Add autoscaling
• Make step scaling policies as outlined above

What did you expect to happen?

I should have 2 alarms created with the actions:

• low alarm

  • remove 1 task < 50% CPU
  • remove 2 tasks < 40 % CPU

• high alarm

  • add 2 tasks > 65% CPU
  • add 3 tasks > 85% CPU

What actually happened?

Environment

• CLI Version : 1.61.1
• Framework Version: 1.61.1
• Node.js Version: v14.8.0
• OS : mac os
• Language (Version): typescript

Other

---

This is 🐛 Bug Report

[kyler-hyuna]

Thanks for fixing this @ruancomelli 🎉

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.