1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
0
Okay, so this place is absolutely dead.
I ended up taking a chance and deleted the Beanstalk environment within the AWS Console. I had to do that since CloudFormation never tried to delete the environment again after the initial attempt. I am disappointed that there is no retry mechanism when the solution is so obvious, but I guess that's just one of the many quirks of CloudFormation. Yes, it was my own mistake that caused me to end up in that situation, but I hoped and expected CFM to handle it a bit more gracefully instead of just getting stuck indefinitely. Disappointing!
So delete the environment manually and CFM will "understand" this and proceed with the stack update afterwards. At least that's what happened for me.
respondido há 2 anos
Conteúdo relevante
- AWS OFICIALAtualizada há 4 anos
- Como personalizo a configuração do nginx para modificar “client_max_body_size” no Elastic Beanstalk?AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 3 meses