Paperclip config conflicting with AWS Elastic Beanstalk - ruby-on-rails

Question

I am using Paperclip in my Rails 5.1 app and have the standard config in my development.rb and production.rb:
config.paperclip_defaults = {
storage: :s3,
s3_credentials: {
bucket: ENV.fetch('S3_BUCKET'),
access_key_id: ENV.fetch('AWS_ACCESS_KEY_ID'),
secret_access_key: ENV.fetch('AWS_SECRET_ACCESS_KEY'),
s3_region: ENV.fetch('AWS_REGION'),
}
}
I'm storing the ENV variables in application.yml via Figaro gem.
This is fine, but I'm now trying to upload my app to a new AWS Elastic Beanstalk app and I'm having the build fail. Having spent the last 3 or so hours looking through all the logs and trying various changes, I've narrowed the failure down to the fact I think Beanstalk is reading the Paperclip ENVs and is getting confused.
From the logs:
rake aborted!
<<<
/var/app/ondeck/config/environments/production.rb:97:in `fetch'
/var/app/ondeck/config/environments/production.rb:97:in `block in <top (required)>'
/var/app/ondeck/config/environments/production.rb:1:in `<top (required)>'
/var/app/ondeck/config/environment.rb:5:in `<top (required)>'
/opt/rubies/ruby-2.4.3/bin/bundle:23:in `load'
/opt/rubies/ruby-2.4.3/bin/bundle:23:in `<main>'
Tasks: TOP => environment
and config/environments/production.rb:97 equates the below value from my Paperclip config:
access_key_id: ENV.fetch('AWS_ACCESS_KEY_ID')
I can't seem to find any items online that would help resolve this.
Any ideas?
Could I use the same IAM user for both so the ENV values match?

Answer 1

Add the paperclip S3 environment variables to your Elastic Beanstalk Environment
How?
Head over to your specific Environment
Select Configuration
In Configuration overview select Software tile
At the very bottom you'll see a form section Environment properties
Add key and value data for your variables
Save and wait for your environment to update.
Read more: Elastic Beanstalk Docs