By using AWS re:Post, you agree to the Terms of Use

Environment named xxxxxx is in an invalid state for this operation.

0

I try to update an Elastic Beanstalk environment which currently is OK but each time I try to update any configuration I get the following error:
Environment named xxxxxx is in an invalid state for this operation. Must be Ready.
Today Elastic Beanstalk has a very bad performance in everything.

asked 4 years ago331 views
1 Answer
0

I have found this issue is because some Elastic Beanstalk scheduled actions: A scheduled action set the environment without instances. This is ok. The second one scheduled action set the environment with the default autoscaling policy (1 instance running, 1-4 required instances). This last one has been failing on rebuild environment or update environment.

If I configure it into the autoscaling group, will work all except rebuild environment where I have to delete the scheduled actions in order to rebuild the environment.

Shouldn't EB allow or recreate the scheduled actions on rebuild environment?

answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions