Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EPIC] DevOps Migrate infra to shared H4LA AWS account (H1 2023) #1367

Closed
7 tasks
nichhk opened this issue Sep 21, 2022 · 2 comments
Closed
7 tasks

[EPIC] DevOps Migrate infra to shared H4LA AWS account (H1 2023) #1367

nichhk opened this issue Sep 21, 2022 · 2 comments
Assignees
Labels
Feature: Missing Role: DevOps infrastructure, CI or related work size: epic

Comments

@nichhk
Copy link
Member

nichhk commented Sep 21, 2022

Summary

We want to move our infra off our private AWS account onto the shared H4LA AWS account. This will help us to be aligned with H4LA best practices. Additionally, we cannot modify our existing infra because SSH keys and configs to the private AWS account have been lost.

Required Issues

  • Get AWS secrets host and key access from Chelsey
  • Add AWS secrets host and key to GitHub repo
  • Determine how to structure new AWS (sub)account for 311 Data within H4LA's greater AWS setup (TODO: Bonnie)
  • Test existing Terraform config using new AWS account. This will bring up the backend infra components only; frontend components are individually and manually configured on AWS.
  • Make any simplifications to the infra, if possible
  • Bring up frontend components
  • Point prod and dev 311 Data sites to new AWS services

Resources/Instructions

system design

@EchoProject EchoProject added Role: DevOps infrastructure, CI or related work Feature: Missing size: epic labels Sep 21, 2022
@EchoProject EchoProject changed the title [EPIC] Migrate infra to shared H4LA AWS account [EPIC] DevOps Migrate infra to shared H4LA AWS account Sep 21, 2022
@EchoProject
Copy link
Contributor

EchoProject commented Oct 7, 2022

I have a meeting with Bonnie and Jason this Sunday (10/9/2022). I'll leave notes from the meeting here.

This meeting was rescheduled to accommodate having 311-Data engineers in attendance.

@EchoProject
Copy link
Contributor

Some notes from my conversation with Jason:

  • Hack for LA currently has 3 AWS accounts. Jason owns and manages 1 AWS account that hosts 9 projects.
  • He doesn't know who the other owners are, and it's possible that 311-Data's current instance is one of the accounts.
  • 311-Data has outgrown (traffic and underlying AWS infra) participation in being hosted with Jason's AWS account.
  • The major challenge with the migration is updating 311-Data's infrastructure to meet the needs of AWS' newer hardware.
  • The estimated lift is 6+ months of engineering work.
  • The suggested route is to create an instance to build and test infra migration and then merge it into a paid instance.
  • Bonnie currently pays out-of-pocket for all AWS accounts. Minimizing this spend is a priority. Having two active accounts should be avoided.
  • While Jason won't have the bandwidth to make the changes, he's open to assisting with questions regarding AWS.

@joshuayhwu joshuayhwu self-assigned this Nov 5, 2022
@mc759 mc759 changed the title [EPIC] DevOps Migrate infra to shared H4LA AWS account [EPIC] DevOps Migrate infra to shared H4LA AWS account (H1 2023) Dec 15, 2022
@EchoProject EchoProject added this to the H123 OPS Migration milestone Jan 11, 2023
@cherriehung cherriehung self-assigned this Feb 9, 2023
@SophAm1 SophAm1 closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2023
@ExperimentsInHonesty ExperimentsInHonesty moved this to Done (without merge) in P: 311: Project Board Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Missing Role: DevOps infrastructure, CI or related work size: epic
Projects
Status: Done (without merge)
Development

No branches or pull requests

6 participants