Make it easier to incorporate new projects to operation code

Right now adding to our current infrastructure is not very easy or new user friendly.

Pain points:

1. Individuals have to get AWS credentials which can take a long time
2. Providing individuals the ability to create their own assets while they are learning can cause them to make big mistakes like provision too many.
3. Have to write their own infrastructure scripts
4. We lost the dockerhub password, so users need to figure it out on their own
5. If they decide to use our current infrastructure we have to learn kubernetes, and then we have to trust them they won't break non-related projects.

An example was, in my case I setup a pythonanywhere account and paid for a server and postgres, then when it started being slow we migrated to ECS. Currently it's on ECS, but the rest of operation code doesn't use ECS.

An example of one solution could be:

1. User requests EC2 and RDS instances.
2. Some authority provides authentication credentials for these assets.
3. User doesn't have to know how to write scripts to upload container as someone in leadership provides a standardized upload to ECR/ dockerhub script.
4. If user wants to troubleshoot production logs, user doesn't need to have full production kubernetes access, which provides ability to break others.

Không có tệp, bài kiểm thử hoặc điểm vào nào được nêu. Hãy bắt đầu bằng cách lập bản đồ cơ sở hạ tầng hiện tại và cách các dự án sử dụng ECS, Kubernetes, EC2, RDS, ECR và Docker Hub; công việc chỉ được xem là hoàn tất khi có thiết kế đã thống nhất và kế hoạch triển khai được tài liệu hóa cho việc provisioning, thông tin xác thực, tải lên và quyền truy cập bị hạn chế vào môi trường production.