You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using AWS IAM Identity Center is best practice according to AWS for assigning out permissions. However, it creates roles with unique names. To avoid having to hardcode unique names everywhere, AWS says you can use a condition with a wildcard in your trust policy. However, terraform-aws-eks-blueprints-teams does not support that currently.
If this repo added support that would make our code a lot cleaner and more maintainable, as we wouldn't have to have hardcoded AWS role names for each AWS account.
Using AWS IAM Identity Center is best practice according to AWS for assigning out permissions. However, it creates roles with unique names. To avoid having to hardcode unique names everywhere, AWS says you can use a condition with a wildcard in your trust policy. However, terraform-aws-eks-blueprints-teams does not support that currently.
If this repo added support that would make our code a lot cleaner and more maintainable, as we wouldn't have to have hardcoded AWS role names for each AWS account.
For reference see bottom of https://docs.aws.amazon.com/singlesignon/latest/userguide/referencingpermissionsets.html
The text was updated successfully, but these errors were encountered: