AWS Beanstalk Restarts Instance

1
votes

I have created a pipeline using AWS Codepipeline, Github, Jenkins and AWS Elastic Beanstalk (Docker) running a nodejs application. Everytime a build is triggered in AWS Codepipeline and deployment done on the Elastic Beanstalk instance, it's corresponding EC2 instance is terminated and another one created afresh and we only want the app to be deployed without termination of EC2 instance. What could be the cause for termination on every build/deployed?

2
amazon-web-servicesamazon-ec2amazon-elastic-beanstalkaws-codepipeline
Do the deployment of your new version cause a huge CPU peak? It can be a reason why Beanstalk terminate your instances (it consider them as not healthy) – Xavier
@Xavier I will try and post if it works, thanks – ted

2 Answers

0
votes

how many instances do you have in your beanstalk and what deployment method are you using: All at Once, Rolling, Rolling with an Additional Batch or Immutable?

With these responses, we can continue the research.

0
votes

I switched to Immutable deployment and stopped experiencing the issue as explained here: Difference between rolling, rolling with additional batch and immutable deployments in AWS?

Turns out that Rolling deployments can cause the timeouts especially that I had a single instance needed