Migrating to Terraform

[fargate-auto-process](https://github.com/developmentseed/fargate-auto-process) is a tool that data-team use to process data in the cloud, which in many times in our local machines can not process because of the data size, or the internet network is not enough to download huge files.

Data-team we manage all our scripts to process data in Docker containers, so what we need is infrastructures that support containers in the cloud

I've worked on this infrastructure that allows us to start AWS Fargate with a few command lines and deploy our containers. It works fine for AWS. But sometimes we also need to use EC2 instances with all the software installed (docker, docker-compose, git, etc).We already have one cloudformation template, but need to fix disk issues, https://github.com/developmentseed/fargate-auto-process/issues/7

Besides, in some projects We use different cloud providers, which our current repo does not support, ge. Google-Cloud or Azure, AWS. That is why I see it convenient to migrate the Cloudformation to Terraform in order to support multi-provider.

Start by reviewing the existing CloudFormation template and the related disk issue, #7, to understand the current AWS infrastructure and its unresolved problems. Then determine the Terraform scope for AWS, Google Cloud, and Azure support, including EC2 instances and container workloads. Done means the required multi-provider infrastructure is represented and the disk issues are addressed.

由索引模型根据 Issue 内容生成。