Migrating to Terraform

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, azure, docker, docker-compose, gcp, terraform
Domain
cloud, devops, infrastructure

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Shell
Stars
1
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/boot-data-instance

All issues in developmentseed/boot-data-instance

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.