Cookiecutter-django: Support AWS Deployment

[steverecio]

Description

There is heavy AWS support in the project but deployment isn't strongly documented. For instance, I need to create a dockerrun.aws.json file in order to launch the services on elastic beanstalk (I'm still struggling to configure this properly). Would be great to have an option that injects some packaging scripts for deploying to AWS.

Make the project ready to be zip'd and uploaded directly into AWS ELB.

Rationale

This should be implemented because of AWS' popularity. Should be much simpler to deploy to the cloud right out the gate (although I understand this adds the dependency of keeping up with any AWS deployment config changes).

[sfdye]

ELB is no longer supported in this project, see 793a46ba452

[steverecio]

Is there another thread that discusses the rationale for removing support?

[sfdye]

1417

[steverecio]

Would still be great to add built-in ECS support in lieu of ELB (sounds like @pydanny is using it for his apps). I'm having trouble figuring out how to set up all the containers in the Task Definition for the default configuration with celery and redis.

[steverecio]

Ended up cloning this rails terraform setup and customizing it to my project for anyone interested: https://github.com/duduribeiro/terraform_ecs_fargate_example

[Andrew-Chen-Wang]

I'm trying to set up ECS @steverecio with AWS GitHub Actions so that you only need to git push. My only problem is 1. I don't want to go serverless and 2. Blue/Green deployment plus ECR means using ONE Dockerfile. Have you got any luck? I'm documenting my finds here: https://github.com/Andrew-Chen-Wang/cookiecutter-django-ecs-github

The only progress as an AWS newbie is mangling through the ECS cluster configuration. It seems like you can add volumes there instead of having volumes in the Dockerfile themselves so that the volumes can persist between builds.

Not to mention the huge inefficiencies of this one dockerfile...