-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Changes to Connect to AWS S3 and KMS using IAM role for EKS service account #186
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the IAM policies related to EKS are located in the iam*.tf
files in the root of the app_eks
module. I do not want a submodule created for these, as it adds additional complexity without clear benefit. Please integrate the changes following the pattern used for the existing IAM policies applied to the EKS cluster, without the use of additional third-party modules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Tested locall and against QA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://www.terraform-best-practices.com/naming#resource-and-data-source-arguments
Do not repeat resource type in resource name (not partially, nor completely)
## [4.11.0](v4.10.2...v4.11.0) (2024-05-18) ### Features * Changes to Connect to AWS S3 and KMS using IAM role for EKS service account ([#186](#186)) ([a07a45e](a07a45e))
This PR is included in version 4.11.0 🎉 |
#179
Connect to AWS S3 and KMS using IAM role for EKS service account