You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried to use prefix list as part of the module, but getting the below error:
A duplicate Security Group rule was found on (sg-XXXXXXXXXXXX).
Seems like this issue occurs only when there are few rules with the same port number, as mentioned in the doc ingress_prefix_list_ids get all the ports from rules, so the error makes sense.
But there is no way to add a prefix-list rule without depending on the other rules.
Versions
Module version [Required]:4.4.0
Expected behavior
Create only one rule with the prefix-list as the source with the appropriate ports
Actual behavior
Getting error with no way to solve, cause lack of option to add prefix rule
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
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.
Description
Tried to use prefix list as part of the module, but getting the below error:
A duplicate Security Group rule was found on (sg-XXXXXXXXXXXX).
Seems like this issue occurs only when there are few rules with the same port number, as mentioned in the doc ingress_prefix_list_ids get all the ports from rules, so the error makes sense.
But there is no way to add a prefix-list rule without depending on the other rules.
Versions
Expected behavior
Create only one rule with the prefix-list as the source with the appropriate ports
Actual behavior
Getting error with no way to solve, cause lack of option to add prefix rule
Additional context
This is probably related to Issues #131 #224
The text was updated successfully, but these errors were encountered: