Sure Marcelo,
We change our settings with each release as that’s where we store our version number. In Waves if you change your settings your machine will restart. We created an EB extensions which reads the settings from our settings file when the machine starts and sets the environment with this. Otherwise you’d have to find another way of setting the version.
If you want to know about the memory usage of your instances it’s a bit of a pain, although this is down to how EC2 works. By default there is no metric for measuring RAM so you have to install a package that then reports it to cloudwatch. Again, this is done via the EB extensions. If you need more details we can post our config here. It was a royal PITA.
To create a dashboard in cloudwatch that updates itself after a new deploy requires a little lambda script to poll every so often to see if the metrics running are still valid, and if not try and update them. This is also a bit annoying and I’ve not got round to actually finishing this, so hopefully Waves can figure out a way to automate it.
Also, if you use cloudflare, you’ll need to find the right moment to reset the cache. What we did was poll our server from our CI script (we use codeship) after deploy. As soon as the version we just deployed is responding we then ask cloudflare to clear it.
Hope that helps
