Exclusive management of inline & managed policies for IAM groups

[YakDriver]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Descends from #4426

Description

Add feature to revert out-of-band changes to attached (managed) and inline policies associated with an IAM group.

New or Affected Resource(s)

• aws_iam_group

Potential Terraform Configuration

resource "aws_iam_group" "example" {
  name          = "yak_group"
  inline_policy = []
}

resource "aws_iam_group" "example" {
  name               = "yak_group"

  inline_policy {
    name = "my_inline_policy"

    policy = <<EOF
{
  "Statement": [
    {
      "Action": [
        "ec2:Describe*"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ],
  "Version": "2012-10-17"
}
EOF
  }

  inline_policy {
    name   = "policy-8675309"
    policy = data.aws_iam_policy_document.inline_policy.json
  }
}

resource "aws_iam_group" "example" {
  name                = "yak_group"
  managed_policy_arns = [aws_iam_policy.policy_one.arn, aws_iam_policy.policy_two.arn]
}

References

• Feature request: Exclusive policy attachment list for users, groups, and roles #4426
• resource/aws_iam_role: Add exclusive list support for a role's inline and managed policies #5904
• Exclusive management of inline & managed policies for IAM roles #17510
• Exclusive management of inline & managed policies for IAM users #17512

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[jbscare]

This is an important security-related feature. Please don't close it.