You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our pipelines have been working for months, but suddenly stopped with the message "Environment is red". However, the logs for that environment in AWS show that everything deployed properly, with no warnings, much less errors. What is the pipeline checking here?
INFO: Checking deployment status in Elastic Beanstalk...
✖ Deployment failed. Environment "XXX" is Red.
G'day, @Kevin Fink
As outlined in our pipe script, we initiate a deployment check through AWS Elastic Beanstalk and determine the deployment status based on the response we receive.
In this specific instance, the information from your environment health indicates that the current status is 'Red,' which leads us to consider the deployment failed.
I suggest increasing the "WAIT_INTERVAL" so that the pipe can wait for a few more seconds than the default 10s to ensure your environment is ready.
Let me know how it goes.