-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
New Resource: data aws_ec2_managed_prefix_lists #17119
Comments
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! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
Currently, the data resource
aws_ec2_managed_prefix_list
exists and refers to a single managed prefix list which you can select by filtering byprefix-list-id
orprefix-list-name
. I propose a new data resource be created that can select a list of managed prefix lists byowner-id
,prefix-list-name
with if there is a naming pattern that is already in place that would return multiple managed prefix lists, or by tag.AWS CLI already supports getting a list of managed prefix lists with the the following command:
aws ec2 describe-managed-prefix-lists --filter Name=tag:Name,Values=values
The contents of which would be helpful in my specific use case of having existing managed prefix list already created, adding the new data resource to select several managed prefix lists based on name or tag, and then creating an
aws_ram_principal_association
with a for_each loop to iterate through the list to share the lists with AWS Resource Access Manager instead of having to create separateaws_ram_principal_association
blocks for each.New or Affected Resource(s)
References
AWS CLI v2 documentation:
The text was updated successfully, but these errors were encountered: