badjware
This project's owner seems to have lost interest; their last activity was on 2020-06-30; this issue proposes a fork to continue the project
@KetchupBomb, yours seems to be the the most developed fork since then (in terms of number of commits and most recently updated, see https://useful-forks.github.io/?repo=badjware/aws-cloud-gaming). This issue could serve as the primary discoverability mechanism. Are you interested in maintaining your fork for other users? If so, consider responding positively here and opening up the issues section on your fork.
I have some interest in helping progress it further, and address some bugs, but I am fairly opinionated about some aspects. There is a bunch of low-quality code in a handful of spots that I'd nearly unilaterally address in a way of my choosing. (For example, in looking to fix the driver install process for g4dn.xlarge, I'd probably drop all code for other clouds and instance types. Potentially building back up afterwards.)
Alternatively, I don't mind if you file some issues on my fork if you trust my ability to fix and are willing for me to say "No" to non-AWS clouds for the time being.
@KetchupBomb I would be interested in using your fork under those conditions.
For many, not being able to choose machine type or cloud provider are minor annoyances, I think.
@KetchupBomb BTW if you haven't seen https://github.com/gcloudrig/gcloudrig yet, it seems to be a similar and more active project. However, it uses only GCP and does not use terraform, among other differences. Even so, it might be worth taking some inspiration from (it is MIT licensed), especially if/when you decide to support GCP.
Also, it has a benchmark which might be worth looking at for comparison.
@hab25, if you have specific deficiencies you want discussed, feel free to create them in https://github.com/KetchupBomb/aws-cloud-gaming.