AWS Resource Migration
Migrate AWS resources from current single unmanaged account to new account structure (prod/nonprod/tooling) managed via Infrastructure as Code.
Scope:
- Transfer all S3 buckets to appropriate accounts
- Transfer RDS databases to appropriate accounts
- Move OCR and emailer Lambdas to new account (remain as Lambda)
- Transfer Event Manager to new account on ECS EC2
- Migrate Portal to ECS EC2
- Migrate Astrata to ECS EC2
- Implement consistent infrastructure tagging
Implementation Notes
New account structure separates production, non-production, and tooling resources. All infrastructure will be managed via IaC. Applications will run on ECS with EC2 launch type.
Tasks
| Task | Description |
|---|---|
| Transfer S3 Buckets to New Accounts | Move all S3 buckets from current account to new prod/nonprod accounts. |
| Transfer RDS Databases to New Accounts | Move RDS database instances from current account to new prod/nonprod accounts. |
| Move Lambdas to New Account | Transfer OCR and emailer Lambda functions to new AWS account (remain as Lambda). |
| Transfer Event Manager to New Account | Migrate Event Manager from current Podman-on-EC2 deployment to ECS on EC2 in new... |
| Migrate Portal to ECS | Deploy Portal application to ECS on EC2 in new account structure. |
| Migrate Astrata to ECS | Deploy Astrata application to ECS on EC2 in new account structure. |
| Implement Infrastructure Tagging | Apply consistent resource tagging across all infrastructure in new accounts. |