Skip to content
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

Merged
merged 5 commits into from
May 18, 2024

Conversation

velotioaastha
Copy link
Contributor

#179

Connect to AWS S3 and KMS using IAM role for EKS service account

@velotioaastha velotioaastha requested a review from gls4 as a code owner March 5, 2024 08:49
@velotioaastha velotioaastha requested a review from a team March 5, 2024 08:49
@velotioaastha velotioaastha changed the title #179 Connect to AWS S3 and KMS using IAM role for EKS service account feat: Connect to AWS S3 and KMS using IAM role for EKS service account Mar 5, 2024
@velotioaastha velotioaastha changed the title feat: Connect to AWS S3 and KMS using IAM role for EKS service account feat: Added changes to Connect to AWS S3 and KMS using IAM role for EKS service account Mar 5, 2024
@velotioaastha velotioaastha changed the title feat: Added changes to Connect to AWS S3 and KMS using IAM role for EKS service account feat: Changes to Connect to AWS S3 and KMS using IAM role for EKS service account Mar 5, 2024
Copy link
Contributor

@gls4 gls4 left a 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.

@velotioaastha velotioaastha requested a review from gls4 March 6, 2024 09:24
Copy link
Contributor

@gls4 gls4 left a 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.

@jsbroks jsbroks linked an issue Apr 30, 2024 that may be closed by this pull request
Copy link
Member

@jsbroks jsbroks left a 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)

@velotioaastha velotioaastha requested a review from jsbroks May 15, 2024 12:56
@velotioaastha velotioaastha merged commit a07a45e into main May 18, 2024
4 checks passed
@velotioaastha velotioaastha deleted the aastha/irsa branch May 18, 2024 04:31
jsbroks pushed a commit that referenced this pull request May 18, 2024
## [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))
@jsbroks
Copy link
Member

jsbroks commented May 18, 2024

This PR is included in version 4.11.0 🎉

@velotioaastha velotioaastha restored the aastha/irsa branch May 18, 2024 04:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Connect to AWS S3 and KMS using IAM role for EKS service account
3 participants