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

Managing IAM policies on the module exclusively #534

Open
GedriteA opened this issue Oct 25, 2024 · 1 comment
Open

Managing IAM policies on the module exclusively #534

GedriteA opened this issue Oct 25, 2024 · 1 comment

Comments

@GedriteA
Copy link

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

  • Yes ✅: 5.72.0

Is your request related to a problem? Please describe.

I want to be able to prevent manually made changes to persist between terraform runs. I.e, someone attaches a policy to the terraformed role via the console - that gets reverted when terraform is applied again. This is not how the module handles it currently given the use of aws_iam_role_policy_attachment.

Describe the solution you'd like.

Provider version 5.72.0 introduced https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role_policy_attachments_exclusive.

A flag/variable that switches between the use of iam_role_policy_attachments and iam_role_policy_attachments_exclusive.

Describe alternatives you've considered.

  1. Managed policy arns (feat: Enables exclusive IAM policy management of IAM role with managed_policy_arns option #526)
  • managed policy arns are deprecated so I don't think this is a good path forward.

Additional context

Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

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

No branches or pull requests

2 participants