This message was deleted.
# clouds
steep-balloon-41261
07/13/2023, 11:30 AMThis message was deleted.
d
dry-elephant-14928
07/13/2023, 4:00 PMyup it does! On the other end, Egress will also pick the edge closest to the RTMP destination and start the session from there.
our network will handle routing of media internally whenever possible
i
important-boots-3535
07/13/2023, 4:46 PMCool, thanks!
important-boots-3535
07/13/2023, 4:50 PMIs this based on some kind of geo-based DNS routing, or a different method? Some of our users at times want to stream to a certain region, wondering if there's some sort of 'override' option with LK.
d
dry-elephant-14928
07/13/2023, 5:04 PMIngress is based on geo-based DNS. can you say more about why users would want to stream to a certain region?
i
important-boots-3535
07/13/2023, 5:10 PMSome users (and I'm talking a very small percentage here) want to be absolutely certain that their streams are being sent to a given region, rather than left to the DNS-routing system to decide. Seems to be more prevalent in Europe - say users are running a session in Germany with participants only in Germany, they want to be certain that the stream is being ingested and played back from servers in Germany for privacy / security reasons (I know, it's pretty vague).
Having worked with AWS Route53 in the past, I know it is possible that there are cases were a user's true location cannot be determined via DNS, though in reality I don't know how real of a problem that actually is.
d
dry-elephant-14928
07/13/2023, 5:18 PMI see! that makes sense. we can probably expose some regional endpoints as well. You are right that there are rare cases where DNS routing could be inaccurate (we've seen cases where corporate VPNs using shared DNS servers returning incorrect locations).