Persistent Data Through ASG scaling out and in

Question

Hello,  
I'm fairly new to AWS architecture and I have an issue. The issue is this. We are hosting our website on Wordpress using Elastic Beanstalk for deployment. We change the language code on our site fairly often and we just do this by pushing changes through code commit. However when one of our instances goes down for whatever reason it loses all the changes we made and thus we have to manually push the updates again. What I'm looking for is best practice methods to maintain these code updates through a reboot. We don't want to use EFS or update the ami every time. I am thinking this can be done via a script but I dont' see where to enter USERDATA in the Beanstalk environment. ANy help with this would be greatly appreciated.  
  
Thanks  
  
Edited by: medwards on May 8, 2020 12:41 PM

Answer

First off, this really is an excellent use case for EFS.  
However, if you don't want to use it, and you want to stick with beanstalk, see:  
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/ebextensions.html

Persistent Data Through ASG scaling out and in

Relevant content