Not everyone wants to run recipes and have caches/outputs in the same bucket for a given AWS account
Solution
To accommodate this we'll have to have some TF in this repository (or another one) where folks can create IAM Assume Roles and S3 buckets that the cross AWS account GH Actions user can assume and create temp credentials for while jobs run on the same cluster
AC:
TF for IAM Assume Roles and S3 buckets
Documentation on how this works
Each new AWS account will have to be listed as a potential choice in the GH Actions input
Problem
Not everyone wants to run recipes and have caches/outputs in the same bucket for a given AWS account
Solution
To accommodate this we'll have to have some TF in this repository (or another one) where folks can create IAM Assume Roles and S3 buckets that the cross AWS account GH Actions user can assume and create temp credentials for while jobs run on the same cluster
AC: