1 Answer
- Newest
- Most votes
- Most comments
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.
answered 2 years ago
Relevant content
- Accepted Answerasked 6 months ago
- Accepted Answerasked 2 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago