Description
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.