3 Answers
- Newest
- Most votes
- Most comments
1
it worked with a security group with tighter restrictions. Idk why.
answered 10 months ago
0
Hi, this link shows an example on how to understand and analyze an ENI_SG_RULES_MISMATCH error: https://docs.aws.amazon.com/vpc/latest/reachability/getting-started-cli.html#view-results-cli
It may help you in the error diagnosis.
As a starting point of your diagnosis, you may change your sec groups definition by removing all denies and allow any kind of trafic of any protocol to see if your error disappear. Then you tighten up again incrementally by restricting the allowed protocols until the error message appears again.
0
It pains me to say it, but changing it from all access across all ports to only 6379 worked for me also. This seems like a bug Amazon should address
answered 8 months ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Hi and thanks for the answer. My security group rule allow every traffic and there is no entry that disallows traffic. My network ACL has an Entry that allows traffic and an * entry that denies traffic. I can not delete the * entry. I dont know why it is not working. the rules are already loose.