Why isn't route advertisement to ingress sources working?

After enabling route advertisement to Transit Gateway, Direct Link, or both for an ingress routing table, the traffic isn't working as expected even though the VPN server is up and running.

A route conflict might exist.

Follow the steps to resolve this issue:

1. Navigate to Interconnectivity > Transit Gateway and locate the transit gateway that connects to the VPC where the VPN server exists.
2. In the Routes section on its Details page, click Generate report to see if there is a conflict (for example, overlapping routes).
3. Resolve the conflicted routes by adjusting address prefixes in VPC.