You would not use MED on the CGW (Cisco), also please note the below statements from the documentation. Weight, LP and AS Path are all evaluated before MED. Ideally the CGW should support Active-Active tunnels with Asymmetric routing enabled, however if it does not then use AS Path prepending and Local preference.
To ensure that the up tunnel with the lower MED is preferred, ensure that your customer gateway device uses the same Weight and Local Preference values for both tunnels (Weight and Local Preference have higher priority than MED).
AWS strongly recommends using customer gateway devices that support asymmetric routing.
For customer gateway devices that support asymmetric routing, we do not recommend using AS PATH prepending, to ensure that both tunnels have equal AS PATH. This helps to ensure that the multi-exit discriminator (MED) value that we set on a tunnel during VPN tunnel endpoint updates is used to determine tunnel priority.
For customer gateway devices that do not support asymmetric routing, please use AS-path-prepending and Local-Preference to prefer one tunnel over the other
AWS VPN Client on macOS - DNS not resolvingasked 6 months ago
Important notice about your AWS Account regarding VPN connectionsasked a month ago
VPN Connection Public IPAccepted AnswerEXPERTasked 2 years ago
How can I make a third-party cloud vpn connection?asked a month ago
Can I delete one VPN tunnel from site-to-site VPN connection ?asked 5 months ago
How can we connect a Sagemaker Studio user to a gitlab repo within a private VPN?Accepted Answerasked 7 months ago
Routing to a prefix from TGW through a primary and secondary datacenter VPN connection pathAccepted Answerasked 2 years ago
can I prevent Client VPN from setting the hostname on the client machine?Accepted Answerasked a year ago
Is possible to set up the BGP pass on a S2S VPN connectionAccepted Answerasked 4 months ago
Site-to-Site VPNasked 15 days ago