Comment éliminer l'erreur « Custom Named Resource already exists in stack » (La ressource nommée personnalisée existe déjà dans la pile) dans AWS CloudFormation ?

Comment m'assurer que l'agent CodeDeploy est déployé lorsque j'utilise CloudFormation pour allouer des instances Amazon EC2 ?

Pourquoi mon pipeline de génération d'image échoue-t-il avec l'erreur « Step timed out while step is verifying the Systems Manager Agent availability on the target instance(s) » dans Image Builder ?

Comment résoudre les erreurs « EC2 is out of capacity » (Capacité EC2 insuffisante) ou « The requested number of instances exceeds your EC2 quota » (Le nombre d'instances demandé dépasse votre quota EC2) dans Amazon EMR ?

As already pointed out in the old [Developer Forum](https://forums.aws.amazon.com/thread.jspa?messageID=812431&tstart=0#812431) CodeDeploy B/G deploy is failing if the AutoScalingGroup has some AutoScalingPolicy attached because it looses the attachment to the original TargetGroup.

Has anybody found a better solution than [manually re-attaching it](https://dev.to/cvortmann/fixing-aws-codedeploy-issue-where-auto-scaling-group-is-not-attached-to-target-group-47ac)?
Attaching the policies instead of the target is also a possibility, but it makes the management of the policies not in CloudFormation. BTW, the old workaround only worked with "classic LB", it can't be implemented with current ALBs.


It is "funny" that AWS is aware of this severe bug but did not fixed it yet, after 5 years ;(

EC2 blue/green deploy with AutoScalingGroup fails

Contenus pertinents