Setup a scalable backend system with Docker and with logging for my python script farm on AWS

BUDGET: $100 MAX, can be only increased if you prove that you are competent enough. I am an AWS architect but need help for the implementation phase of the improvement of my functioning script farm since I am already overloaded by other projects. I have python scripts already working fine on AWS EC2 instance setup by me, on which instance there is also a wordpress multisite instance is running. What I want from you is to design the system which will: 1-)Spawn/kill a new Docker instance for the python script as soon as the appropriate command will come from the frontend (e.g. through API gateway via a lambda function), front and will be all website, an app or chrome extension. the incoming commands will be parametric and will have an impact on the python script. The docker instance shall also include a simple bash/python script for tracing some specific output prints and inform frontend appropriately (details will be provided). So the data transfer between frontend and backend will be in both ways 2-) Setup the auto-scale group so that will scale up/down depending on the network/CPU usage, making sure that it is compatible with my load-balancer setup for the Wordpress Multisite which is on the same instance! (details will be provided) 3-) Create a RDS instance (better in another VPC since it will be internally used only) and the tables which will be accessed by the EC2 instance (details will be provided) 4-) Make sure the setup will be working smoothly along with manual interruption as well, e.g. if I want to build 20 dockers I will be able to do that or if I remove a record from RDS and/or stop a Docker instance. 5-) A simple bash/python script which will regularly check if there is a new merge/version of the python script and if there is at a decided hour will terminate all the dockers and restart them with the new version. 6-) Cloudwatch setup which will report CPU/network metrics, errors and occurrences of some specific outputs from the Docker instances 7-) Most importantly, DOCUMENTATION! Everything you have setup should be carefully documented, This is as important as the success of the project! The documentation shall include the commands used and the purpose of running them, all the scripts created, all the created/used AWS services in the project as well as and a full architectural depiction of the backend. In your bid, please include your opinions about the items 1,2,3 to be considered. Otherwise you will NOT be considered. If you have better ideas for implementing, you may propose them, if your ideas overcome mine for backend, I can even increase the budget!