- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello there,
Looking into the error message, it seems like the command execution on the instances have failed. This can happen due to multiple reasons. At the end, it is mentioned that command hooks failed. If you are using hooks with the Elastic Beanstalk environment they might be failing too.
The best way to identify the reason behind the error is to fetch the logs of the environment or RDP into the instance. You need to look at the log locations to find the reason behind it. You can use this document to fetch the logs - https://repost.aws/knowledge-center/elastic-beanstalk-windows-instance-logs
If you are still not able to find the cause behind the issue, I request you to reach out to the Technical Support team with the environment ID and region for further investigation of the issue.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
Thanks for your support.
Did you ever find out how to overcome this issue? We're having the same issue and are looking for a solution. Please let us know if you found one. Thank you!