1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren