dms1981

Moved to blocked as this is dependent on #1844

[AWS Health Aware – Customize AWS Health Alerts for Organizational and Personal AWS Accounts ](https://aws.amazon.com/blogs/mt/aws-health-aware-customize-aws-health-alerts-for-organizational-and-personal-aws-accounts/) - relevant AWS blogpost. Looks like there's a terraform option available [here](https://github.com/aws-samples/aws-health-aware#terraform) that could be...

Seems like a data call would be ideal here? https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/ami - could be used to return the most recent ami based on a few filters.

I understand this a bit better now; in short, this is to find a way to flag the autoscaling / launch group to use the latest version of the AMI...

The terraform guidance is here - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#with-latest-version-of-launch-template However, what that looks like in practice (eg, does it update to a more recent version without a terraform run), I don't know.

Having done a little more thinking on this, I think that the `bastion_linux_template` needs to be decoupled from the code in `main.tf` and then run via github actions on a...

Moving this one out of sprint until such time as the user research is done.

Added #1922 as a first step

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...