Score:0

Elastic BeanStalk environment variable update fails

cn flag

When I try to update the environment variables of my Elastic BeanStalk environment via the software configuration, the update fails and the environment is rolled back to the previous configuration (see image).

events

Does anyone know why this might happen? The strange thing is that whenever I deploy the full CodePipeline (GitHub -> build files on build server -> deploy to Elastic BeanStalk) the whole process succeeds. Only whenever I try to change the software configuration, the process fails.

It seems to go wrong somewhere in the CloudFormation stack:

enter image description here

I have never manually changed the stack, it was entirely constructed via a CodePipeline configuration.

cn flag
That error in the second screenshot looks like the culprit - when you edit it manually are you missing out some variable that needs setting?
Thijmen avatar
cn flag
I will look into that. But what's weird is that I have never manually changed the stack, so I figured a syntax error of some sort would be unlikely. Thanks for thinking along.
Thijmen avatar
cn flag
I must say though that I am rather inexperienced with CloudFormation, especially since the whole deployment was setup via Elastic BeanStalk. Do you have any suggestions on how to approach the issue?
Thijmen avatar
cn flag
Might manually changing the name tag of an EC2 (which I did) have caused this issue?
cn flag
It shouldn't do, as tags are only tags - normally easily reverted back by CloudFormation. If you go to the CloudFormation console itself, is there more info on the error? Under the Stack -> Events?
Thijmen avatar
cn flag
The error I posted (the `Fn::join` error) is everything I can see under Stack -> Events. Also, when I go to the stack template editor and validate the template, the validation succeeds. Which shouldn't happen if there is a syntax error, right?
cn flag
It may not be a syntax error but something that is omitted when you run it manually. As in, a variable or parameter that is not being passed in, so is empty, so the join fails.
Thijmen avatar
cn flag
Okay so what I tried to do is create a Elastic BeanStalk environment completely from scratch. But as soon as I try to add a RDS database, I get this error: `Service:AmazonCloudFormation, Message:Stack named 'awseb-e-4p3iiqmssm-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS' Reason: null`. Can't help but feel they are related... Also, reason null?
Thijmen avatar
cn flag
I have created a different thread for this issue: https://serverfault.com/questions/1093976/attaching-rds-database-to-elastic-beanstalk-fails-with-reason-null
Score:0
cn flag

The issue has resolved overnight, just like how it appeared. Was thus likely on the side of AWS.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.