Implement ingress_with_prefix_list_ids and egress_with_prefix_list_ids

[arielsalvo]

Is your request related to a new offering from AWS?

This would be a missing use case related to the already implemented ingress_prefix_list_ids and egress_prefix_list_ids

Is your request related to a problem? Please describe.

In order to create rules with different combinations of prefix_lists and ports in the same SG, I had to create rule-only modules and I even had to use ingress_with_self to create a rule for a custom port.

Describe the solution you'd like.

The solution would be to implement something very similar to what is already implemented for other types of rules (e.g. ingress_with_cidr_blocks or ingress_with_source_security_group_id

Describe alternatives you've considered.

As stated before, I created rule-only instances of the module to group by ports and prefix lists so that each prefix list can be granted access to the appropriate ports. i.e. list_A would have access to ports 443 and 22, and list_B only to port 443.

Additional context

This is probably related to Issues #131 and #158 .

[github-actions]

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

[github-actions]

This issue was automatically closed because of stale in 10 days

[arielsalvo]

This is still missing and shouldn't be closed

[simoferr98]

I find myself in the same situation.

[michaelallcloud]

Same here

[davcen]

Same problem here

[github-actions]

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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.