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
HIGH: IAM policy document uses sensitive action 'secretsmanager:GetSecretValue' on wildcarded resource '*'
════════════════════════════════════════
You should use the principle of least privilege when defining your IAM policies. This means you should specify each exact permission required without using wildcards, as this could cause the granting of access to certain undesired actions, resources and principals.
See https://avd.aquasec.com/misconfig/avd-aws-0057
────────────────────────────────────────
oidc.tf:47
via oidc.tf:47 (aws_iam_role_policy.organizations_role_policy.policy)
via oidc.tf:46-98 (aws_iam_role_policy.organizations_role_policy.policy)
via oidc.tf:42-99 (aws_iam_role_policy.organizations_role_policy)
────────────────────────────────────────
42 resource "aws_iam_role_policy" "organizations_role_policy" {
..
47 [ Version = "2012-10-17"
..
99 }
────────────────────────────────────────
In order to avoid the error, for now, we have ignored it. We wish the user to be able to set any secret name they choose.
In order to satisfy both conditions, we should make the secret names a variable that the user must supply.
The text was updated successfully, but these errors were encountered:
ISSUE
With the current code, we are getting
trivy
errors for thegithub-aws-oidc
module:Resulting in:
In order to avoid the error, for now, we have ignored it. We wish the user to be able to set any secret name they choose.
In order to satisfy both conditions, we should make the secret names a variable that the user must supply.
The text was updated successfully, but these errors were encountered: