Fix : AWS ElasticBean Deployment fails for Rails Application

There is always an issue with Amazon Web Services ElasticBean while deploying applications and always a scary part. It was a cakewalk on Heroku hosting platform but it's nightmare here and wastes days 

TheRails Application  use Puma as default server, recently it has updated to 5.2.2 at the time of writing this post.

During the recent deployments to AWS elasticbean all have been failing, The main reason is the Gem File isn't being obeyed. 

The specified version of the Puma isn't being instaled by the AWS serves when  A revolution for server

I decided to go back to Django again. You can read this post to encounter what all I encountered duint the deployments of Django Application.

So going back to Rails. Everything has been installed properly except the Puma server. 

I specified 4.3.2 in my Gem File but AWS was installing the 5.2.2. And all the Load Balancers have been showing the status of 502 or 400. The Server health is shown as degraded or severe.

Here are the steps to overcome this issue.

1. In you Gem file, delete the line gem 'puma'.

2. Put this code gem 'passenger'.

3. Run bundle install.

Push it to your AWS Code Commit and run eb deploy