I have a few config files that I changed on my EMR cluster such as the zeppelin-env.sh, zeppelin-site.xml or tmux.conf.
In each file I do minor changes such as add a few export lines. I', happy with those confs and now I want them all to be there on start up.
I can save those conf files on my S3 and aws cp them with a bootstrap action but this feels like an overkill for a few line changes.
What is the best practice to change conf files on cluster creation?
Apparently zeppelin-site.xml is unneeded as everything can be overridden using the zeppelin-env.sh, which in turn can be configured with the configurations API.
For application that I install using a BA, I will aws s3 cp per Henry's advice.