Rails 6 on Elastic Beanstalk

This article is designed to cover & fix some of the issues when attempting to run a Ruby on Rails 6 on AWS Elastic Beanstalk.

The Quick Version (TLDR)

  • Create directory .ebextensions in the top level of your application
  • Create .config file which contains the commands to fix deployments (script here)
    • Add commands for upgrading nodejs to >=6.14.4
    • Add container commands to install webpack & precompile assets
  • Disable asset building through elastic beanstalk
  • Deploy (wait 5 – 7 min for steps above to complete)

The Detailed Version


First the setup:

  • I was upgrading from Rails 5.2 to Rails 6
  • ElasticBeanstalk Platform: Puma with Ruby 2.5 running on 64bit Amazon Linux/2.11.0
  • This was for: demo.InsiderOpinion.com

Rails 6 on Elastic Beanstalk – Nodejs Issue

The primary issue was that when upgrading I did my standard deployment “eb deploy” — unfortunately, on this deployment I got “502 Bad Gateway Error” when I visited the page.

Quickly I try to grab some logs… and it bugs out, no logs. Usually, this means the server never launched and had an error some where on deployment. Luckily, I have Elastic Beanstalk configured such that I can SSH into the machine. After accessing the machine I ran cat /var/log/eb-activity.log and it shows me everything I need.

Turns out I’m experiencing issues from the new Webpacker default for Javascript compilation:

Webpacker requires Node.js >= 6.14.4 and you are using 4.6.0
Please upgrade Node.js https://nodejs.org/en/download/ (Executor::NonZeroExitStatus)

Cool AWS, using NodeJS from 2016:

To upgrade I found a StackOverflow discussion, creating a .ebextensions/ directory in the top level of the project and adding the following file to said .ebextensions/ directory:

Note, we are installing yarn & nodejs on the instance itself via the commands. This will deploy along with my application and be executed on the instance.

Rails 6 on Elastic Beanstalk – Asset Compiling Issue

Once I added it, I Tried to deploy again and again:

Well, that’s frustrating – lets look at the logs again:

[Application deployment StartupStage0/AppDeployPreHook/11_asset_compilation.sh] : Activity execution failed, because: ++ /opt/elasticbeanstalk/bin/get-config container -k script_dir


[Application deployment] : Completed activity. Result: Application deployment – Command CMD-SelfStartup failed

Not much explanation there, but I’m suspecting it’s still related to the Webpacker. After from more DuckDuckGo-ing, I found this Reddit discussion, recommending disabling asset building (set RAILS_SKIP_ASSET_COMPILATION to True) and adding it to the .ebextensions/ directory (again):

Added and redeployed! Progress was definitely made (confirming it was the Wepacker changes), but now assets don’t appear built at all:

Woah – that’s not right! It appears as if the assets aren’t being compiled.

Rails 6 on Elastic Beanstalk – Webpack not found

Huh… SSHing back in I find:

error Command “webpack” not found.

At this point, my mental state can be summed up best by a meme:

Webpacker was already present in my Gemfile (version 4.0.7), apparently it also needs to be installed on the container. This simply means adding a single line to install webpack on the container, bringing our container_commands in our ebextensions/ config to two lines:

Moment of truth, deploy again & wait:

Finally! It appears to function as intended, what a glorious sight. It’s important to keep in mind, all of these steps are outside the normal process and it takes quite a bit of time to install (on the order of 5 – 7 min). The whole configuration script is as follows:

Rails 6 on Elastic Beanstalk – Closing Thoughts

I just want to place emphasis – I would not recommend using Elastic Beanstalk. Having said that, clearly I use it. The main issue I have is how “janky” the system is. For my development it helps me scale well, as I have between five to seven microservices running at any given time. However, if possible, avoid Elastic Beanstalk – I’m sure you can see why.

Some of these issues can be mitigated by creating docker containers and deploying them. Admittedly, that would be easier, but this is my current set up.

Anyway, hope this helps!

Related Articles

Leave a Reply

Your email address will not be published.

 characters available

Time limit is exhausted. Please reload the CAPTCHA.