Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Bitbucket pipeline deploy failing with "Environment is red" but AWS logs do not agree.

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.

1 answer

0 votes
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 22, 2023

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.

Regards,
Syahrul

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events