Refactor Civic Tech Jobs code to Terraform - Discovery

[robinglov]

Overview

Civic tech jobs has outdated code that is buggy and utilizes the AWS console. To modernize the code, it should be refactored to provision resources in Terraform.

Action Items

• Meet with Civic Tech Lead to outline next steps
• Create list of resources needed
• Destroy current configuration
• Rebuild with Terraform

Resources/Instructions

• https://github.com/hackforla/ops/wiki
• Civic Tech Jobs
• Civic Tech Jobs repository
• ECR - Read/Write Docker Containers for our Application

[ExperimentsInHonesty]

Content from issue hackforla/ops#65 which ended up being a duplicate of this issue but not formatted correctly.

Account Name

JimmyJuarez10

Project(s) Name

CivicTechJobs

Action Items

• Create list of resources needed
• Destroy current configuration
• Rebuild with Terraform

Resources for

1. ECR - Read/Write Docker Containers for our Application

[sudhara]

@JimmyJuarez10 @robinglov We would like to talk about civitechjobs status on the incubator Terraform migration?
We have the following questions from @RSkuma DevOps CoP lead -

I was at the CivicTechJobs meeting to help with their deployment, but I wasn't able to get a complete picture of where they are at and was hoping you could help
CivicTechJobs currently has some assets on the Incubator AWS account, but at the meeting they said they are planning to migrate to Incubator in the near future. If that's true, where are the AWS resources currently on Incubator from? Are they already on Incubator? Is it an older version? Or a partial deployment?
2. Will CivicTechJobs be deployed on Incubator permanently? Or is it temporary with the intent to grant them their own AWS account later?
3. Does CivicTechJobs already have their own AWS account? Somebody on the CivicTechJobs team said they did, and that their account is being charged $200 a month. I'm thinking they were logged into Incubator when they saw that number but I would like to confirm