modernisation-platform
modernisation-platform copied to clipboard
SPIKE: Closing down performance hub legacy AWS accounts
Jeremy Collins from PH mentioned that there are some legacy aws account for PH that will need to be closed down.
Details in this thread: https://mojdt.slack.com/archives/C013RM6MFFW/p1648115926659709
This one depends on aligning with Jeremy on PH so that he can complete any outstanding migrations before we close the accounts down.
Hi - it's our dev RDS database, plus one or two S3 buckets. The only blocker I can see to moving RDS to mod platform is the ability to sustain a stable SSH connection for dev. The Bastions work well, but the connection often drops (connection corrupted, bad packet length) so running a local app against it could get frustrating... If we could solve this then we could most likely migrate.
This story is to research any things we can do to assist Jeremy in migrating resources out of the legacy Performance Hub accounts so that we can close them down afterwards as a separate story.
This issue is stale because it has been open 90 days with no activity.
This issue is stale because it has been open 90 days with no activity.
To close down performance hub legacy account, we will need to get the development account on mod platform working. Creating a cards for the stages of this.
It'll be a database migration, but I think I have helped solve the issue. Waiting 2-3 days to polish out a plan and create a card for it, then close this one.
https://github.com/ministryofjustice/modernisation-platform/issues/5214
Created from Spike.