Skip to content

Conversation

@hoangminhtu-dh
Copy link
Contributor

The additional IAM permission was first discussed in this Github issue: kubernetes-sigs/external-dns#1019, which was implemented and the external-dns documentation was updated: https://github.com/tico24/external-dns/blob/master/docs/tutorials/aws.md

I left the earlier ListTagsForResource as-is since I think earlier versions of external-dns might still need it.

Description

Motivation and Context

Breaking Changes

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

The additional IAM permission was first discussed in this Github issue: kubernetes-sigs/external-dns#1019, which was implemented and the `external-dns` documentation was updated: https://github.com/tico24/external-dns/blob/master/docs/tutorials/aws.md

I left the earlier `ListTagsForResource` as-is since I think earlier versions of `external-dns` might still need it.
@hoangminhtu-dh hoangminhtu-dh changed the title fix: external-dns 1.19 requires ListTagsForResources fix: Update IAM: external-dns 1.19 requires ListTagsForResources Nov 25, 2025
@bryantbiggs bryantbiggs changed the title fix: Update IAM: external-dns 1.19 requires ListTagsForResources feat: Add ListTagsForResource to external-dns policy Nov 25, 2025
@bryantbiggs bryantbiggs merged commit fc63f9f into terraform-aws-modules:master Nov 25, 2025
7 of 8 checks passed
antonbabenko pushed a commit that referenced this pull request Nov 25, 2025
## [2.5.0](v2.4.2...v2.5.0) (2025-11-25)

### Features

* Add `ListTagsForResource` to `external-dns` policy ([#53](#53)) ([fc63f9f](fc63f9f))
@antonbabenko
Copy link
Member

This PR is included in version 2.5.0 🎉

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.

3 participants