1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 10 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 6 mesi fa
- AWS UFFICIALEAggiornata 3 anni fa