AWS deployment scripting

Hi! I am a programmer who is sick of doing DevOps stuff (though I have lots of experience with it). I would like someone who can create a sensible, best practices system in AWS from a clean slate for my next project. Specifically, I would like the following 4 scripts (either in Python or bash): install_tools: Install any dev tools, packages, AWS CLI, etc and set up the user environment on the local machine. Will just be run once on a clean Ubuntu install to ensure that we have the same software (anything required for the next 3 scripts). setup_account: Create users and roles on AWS. create security groups, etc (everything required by the below 2 scripts). This script will be run once to do all of the one-time, global configuration of the AWS account. create_environment: Create a named environment (ex: "production", "staging", "john", whatever.) This is meant to create an entire set of resources that can run the web code (Django on Apache) via Elastic BeanStalk. The web server also requires an RDS instance. These resources should all be unique per name. So if I run the script once for "production", and then again for "john", no resources should overlap or conflict. There should also be a worker tier group and SQS queue created for the environment so that asynchronous tasks can be completed. I will provide the code to run (for both the web and worker examples), but they will be super simple "hello world" type applications (with a dependency or two to check that those are installed as well). This script is meant to be run once per environment. update_environment: Takes name of environment (from the previous script) and the github URL of new code to deploy, and deploys it to that environment. Should run any new migrations for Django if the models have changed, restart the worker and web groups with the new code, install any new dependencies, update any changed configurations, etc. I will provide significantly more detail for each script upon request / once you begin. This project is hourly for a few reasons: - There are lots of other features I would like to add. If I'm happy with your work, I'll have you continue to do those (ex: setting up log ingestion to elastic search, using route 53 to control the domains for each environment, etc) - If there is any piece that you are not sure how to do, I can take care of it. Ideally you would be more experienced at most of this than me though, and so it would not take you very long. - I'd like to start with a very minimal subset of the features to ensure that we enjoy working together, and grow from there. Ideally you would have time in the very near future to do a good portion of this. How to apply: Please include a short script that creates a user in AWS using the CLI and gives it permission to launch instances via Elastic BeanStalk, and permission to create new RDS instances. Send it along with any other relevant information about why you think you would be a good fit for this job. Thanks!