I got a following deployment error in Elastic BeansTalk.
ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version. ERROR Failed to deploy application. ERROR Unsuccessful command execution on instance id(s) 'i-xxxxxxxxxxxxxxxxx'. Aborting the operation. INFO Command execution completed on all instances. Summary: [Successful: 0, TimedOut: 1]. WARN The following instances have not responded in the allowed command timeout time (they might still finish eventually on their own): [i-xxxxxxxxxxxxxxxxx]. INFO Environment health has transitioned from Ok to Info. Application update in progress on 1 instance. 0 out of 1 instance completed (running for 16 seconds). INFO Deploying new version to instance(s). INFO Environment update is starting.
I tryed again, but I got same error message.
So I googled it, I found that the EC2 instance which Elastic BeansTalk tryied to launch was the cause of deployment error.
How to Solve
AWS said that it was “Bugs in EC2 instance”.
So all you need is only terminating EC2 instance manually of which instance-id was shown in the error messages.
Then deploy again and you will get the successful message.
Environment update completed successfully!!!