1 個回答
- 最新
- 最多得票
- 最多評論
0
Hi there,
This most likely indicates that the underlying cloudformation stack for your Elastic Beanstalk environment is currently in a non-updatable state such as UPDATE_ROLLBACK_FAILED due to some previous failed update or rollback operation on the environment.
You can verify this by going to the AWS Cloudformation console and checking the status of the cloudformation stack corresponding to the beanstalk environment. (The stack name would have the beanstalk environment ID).
If this is indeed the case, then you need to follow the below steps to fix the environment state,
- Manually perform a continue update rollback operation on the cloudformation stack by skipping the failed resource. More details in our documentation here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-continueupdaterollback.html
- Once Step 1 is complete, open a technical support case with AWS under the Elastic Beanstalk service in order to get the environment status updated. More details here: https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Hope this helps. Please feel free to reply if you have any further questions/concerns.
已回答 1 年前
相關內容
- AWS 官方已更新 7 個月前
- AWS 官方已更新 1 年前
Thanks for the follow up. What is the turn around time range on step 2? In the case of my issue, I was unable to deploy or modify my website so I didn't have the luxury of time, so I ended up just creating a whole new environment from scratch and switching over the DNS.