Yes, as the Forum post says -
A Customer could, and has, learn AWS Public routes over their DX peering and then readvertise those routes to other ASs (eg. ISPs). If those ASs via their ISP has a long enough AS Path to AWS, they could select those DX learned routes as their best path and would use the DX customer as transit.
To be clear, "worse" in this context simply means that if our routes are leaked by a customer to the Internet, from a BGP perspective they have a longer path and therefore should be less preferable than the paths we advertise directly to our peering and transit providers.
If this doesn't work for some reason with our customers - for example, they run eBGP internally and need to export the prefixes between those different internal ASN's, there are configurations they should be able to apply on their side to modify the communities and strip NO_EXPORT for example.
Direct Connect Public VIFasked 7 months ago
Direct Connect Failover with two Virtual Interfaces (VIFs)Accepted Answerasked 2 years ago
Is it better to have a single Direct Connect Gateway or multiple Direct Connect Gateways?Accepted AnswerEXPERTasked 5 months ago
AWS Direct Connect route limitAccepted Answerasked 7 months ago
AWS Direct Connect Jumbo Frames Enabled Locations?Accepted Answerasked 3 years ago
[Announcement] IP prefixes advertised on AWS Direct Connect Public Virtual Interfacesasked 5 years ago
VPN over Direct Connect with Direct Connect GatewayAccepted Answerasked 2 years ago
AWS's Capability in Handling Outbound Routing with Multiple AWS Direct Connect Connectionsasked 6 months ago
Direct Connect Gateway pricing?Accepted Answerasked 5 years ago
Why is AWS Direct Connect advertising prefixes with a minimum path length of 3?Accepted Answerasked 2 years ago