1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
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.
respondido há 2 anos
Conteúdo relevante
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há 10 meses
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há 2 anos