General answer: Caching is mandatory for performance.

• Particular answer to proxy cache:
  • I've configured nginx proxycache on /dev/shm for performance (on ram cache). 1 minute for proxycache should be fine if the content is changing constantly, cause nginx will “rebuild/compile” the cache after 1 minute but inside that minute, it will use the already compiled version of the file.
• Particular answer to static content:
  • Static content to 1 hour maybe is aggressive, normally I set it up to 1day or more, also depends on the type of application.
• Particular answer to proxied content:
  • I Think we must include a header like “If-Modified-Since” to invalidate local cache if the file has been changed on the server.

I did some mistakes, so I create some versions of it:

• name : dodgermarfeeltest_003
• id : ami-0bc1be25784321fc1

#cloud-config

runcmd:
  - [ mkdir, -p, /opt/test ]
  - [ wget, -O/opt/test/master.tar.gz, "https://bitbucket.org/Marfeel/appserverpythontestapp/get/master.tar.gz" ]
  - [ tar, xzfv, /opt/test/master.tar.gz, -C, /opt/test/ ]
  - [ systemctl, start, marfeel_test ]
  - [ systemctl, restart, nginx ]

I create the 001 group with https, then I remove it in the 2nd version:

• name: dodgerlaunch002

* name: ''marfeel_scalinggroup_001''

Done as required with a very simple bash script.
Dependencies for running the script:

• aws-cli
• jq

This script should be run by root.

Code: <file bash makeitcool.sh>