A
on AWS and what I hope isn't a plan to screw partners:
On the 7th of February AWS edited their documentation to include a limit on Traffic Mirror Sessions that wasn't, until then, ever mentioned.
-
-
Every time I say that contention is a 'possibility' here, I mean if we didn't have these limits. But we do have the limits, so the AWS Network keeps its high reliability and performance.
-
Thank you for the explanation Colm. I'm sure that this feature can't be easy to maintain (from your side) at scale, so I don't doubt that the limitations that are in place are useful. That being said, I still believe there are many aspects of this feature that were 1/n
- 1 more reply
New conversation -
-
-
I 100% agree with you, but there is an argument to be made between what you can do with a medium C5n capable of 20 assets with these limitations and the 100+ that are recommended for dedicated EC2s.
-
20 assets obviously doesn't mean full throughput of the instance in question. Forcing users to go with a NLB for a possible 5Gbps on an instance that can do up to 25Gbps is a - possible - waste of resources (and cash).
End of conversation
New conversation -
-
-
I also don't fully understand how an NLB helps with shared ENI load: If my Target is an NLB and my NLB is sending data to an EC2 ENI, won't the same amount of data reach the EC2 just as if the NLB wasn't there? Maybe I'm missing something from the documentation.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.