1 回答
- 最新
- 投票最多
- 评论最多
0
For some reason, QueueProcessingFargateService sets CPU scaling targets as well as queue processing targets.
I had the same situation and the solution was to delete the corresponding alarms in CloudWatch manually. Go to CloudWatch -> All Alarms and find the one for your service.
There is a bug report for this in GitHub: https://github.com/aws/aws-cdk/issues/20706 so this will hopefully be fixed soon.
已回答 2 年前
相关内容
- AWS 官方已更新 2 个月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前