I am not having access to AWS Fargate, so testing is not going to be easy.

If you say it helps, we can extend the use tcp_connection_match to have different layers of matching, but considering its value as flags.

So tcp_connection_match=1 does like now (which is the first flag 1<<0), then for matching the port along with connection id, the 2nd flag 1<<1 has to be set, tcp_connection_match=3.

The idea is to be able to set the behaviour via parameters, so what fixes in this case is not breaking for others not using same infrastructure.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.