chore(deps): update terraform terraform-aws-modules/iam/aws to v5.44.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
terraform-aws-modules/iam/aws (source)	module	minor	5.43.0 -> 5.44.0

---

Release Notes

terraform-aws-modules/terraform-aws-iam (terraform-aws-modules/iam/aws)

v5.44.0

Compare Source

Features

• Add support for OIDC policy conditions (#​480) (02a5b7f)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Use a variable for the module version to simplify future updates Consider using a variable for the version number instead of hardcoding it in multiple places. This approach will make future updates easier and reduce the risk of inconsistencies. terraform/eks/irsa.tf [4] -version = "5.44.0" +version = var.module_version Suggestion importance[1-10]: 9 Why: Using a variable for the version number improves maintainability by making future updates easier and reducing the risk of inconsistencies across the codebase.	9
Best practice	Document the reason for the version update in the code Add a comment explaining why the version was updated, especially if it includes critical fixes or features needed by the infrastructure. terraform/eks/irsa.tf [4] -version = "5.44.0" +version = "5.44.0" # Updated to include fixes for XYZ issue Suggestion importance[1-10]: 7 Why: Adding a comment explaining the reason for the version update can be helpful for future maintainers to understand the context of the change, but it is not critical.	7
	Test new versions in a staging environment first Review and test the new version in a controlled environment before deploying to production to ensure it does not introduce any regressions or issues. terraform/eks/irsa.tf [4] -version = "5.44.0" +version = "5.44.0" # Ensure testing in staging before production deployment Suggestion importance[1-10]: 6 Why: Testing new versions in a staging environment is a good practice to prevent potential issues in production, but the suggestion is more of a procedural reminder than a direct code improvement.	6
Possible issue	Verify module version compatibility with the infrastructure Ensure that the version specified is compatible with other modules or the overall infrastructure requirements to avoid potential conflicts or unsupported features. terraform/eks/irsa.tf [4] -version = "5.44.0" +version = "5.44.0" # Ensure compatibility with other infrastructure components Suggestion importance[1-10]: 5 Why: While ensuring compatibility is important, the suggestion does not provide a concrete improvement to the code itself. It serves more as a reminder than a code change.	5