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年前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 2ヶ月前
- AWS公式更新しました 3年前