(aws-ecs): autoScaleTaskCount and scaleOnCpuUtilization don't add scaling policies to ECS service

I’m trying to set up target scaling for an ECS service following the documentation, but it doesn’t seem to be doing anything.

Reproduction Steps

        service.autoScaleTaskCount(
            EnableScalingProps.builder()
                .minCapacity(app.minInstanceCount)
                .maxCapacity(app.maxInstanceCount)
                .build()
        ).scaleOnCpuUtilization(
            "cpuScaling",
            CpuUtilizationScalingProps.builder()
                .scaleInCooldown(app.scaleInCooldown)
                .scaleOutCooldown(app.scaleOutCooldown)
                .targetUtilizationPercent(app.targetCpuUtilizationPercent)
                .build()
        )

What did you expect to happen?

I expect to see something like this:

What actually happened?

Instead I see:

Environment

• CDK CLI Version : 1.99.0
• Framework Version: 1.99.0
• Node.js Version: v14.15.0
• OS : MacOs BigSur
• Language (Version): Kotlin (Java 11)

Other

What this looks like in CloudFormation:

---

This is 🐛 Bug Report

[FelixRelli]

Probably related: For scheduledTasks (scaleOnSchedule) the scaling is working, but they do not show under Scheduled Tasks in the UI.

    const scaling = ecsService.autoScaleTaskCount({ maxCapacity: 1 });
    scaling.scaleOnSchedule('StartVectorizationTask', {
      schedule: Schedule.cron({ minute: '10' }),
      maxCapacity: 1,
      minCapacity: 1,
    });
    scaling.scaleOnSchedule('StopVectorizationTask', {
      schedule: Schedule.cron({ minute: '20' }),
      maxCapacity: 0,
      minCapacity: 0,
    });

cdk v. 1.129.0

[awsiv]

This is because the ClusterName now contains ARN, but Cloudwatch alarm (for autoscaling) doesn’t like it.

If you change to using cluster name, it should be fine - however this requires an additional step to change the cluster name. CDK should handle it properly