2 Answers
- Newest
- Most votes
- Most comments
1
Have you got any error in Beanstalk logs ?
Try adding the variables with eb setenv VAR1=value1 VAR2=value2 so you can see what triggers errors.
Anyway if it's a Bug, AWS Support can help you with this.
0
I have resolved it for now by moving some not-so-secret environment variables into my codebase. By doing so I probably got under the 4kb limit and afterwards I could add the new environment variables.
So for me the case is solved. Nonetheless I think it is a UI bug that might impact others: if the variables are not going to be persisted due to a 4kb limit, it should error instead of showing the new environment variables in the UI as if persisting them succeeded.
answered 2 years ago
Relevant content
asked 2 years ago
