Outside route vs local interface

Hello,

 

I'm using F5 in AWS as "Transit VPC Router". So it's termination point for multiple VPN tunnels (other accounts) and then propagating 0.0.0.0/0 using BGP - so technically it's my default GW for all AWS resources :-)

 

AWS offering also very good feature named VPC Peering - this is out of the box network link between multiple accounts. I'm thinking can I "expand" my setup so my "incoming traffic" will go over peering rather than IPSEC.

 

So I really got a question about route priority: For example I've got 172.16.0.0/24 on other side of VPN tunnel. So naturally this is my routing table going to tunnel interface and got metric 0 (flags UG). What happen I would change the (can I even do that?) metric of this route to let's say 50 and then add another static route 172.16.0.0/24 via metric 0 ?

 

Is that possible or F5 no matter what will go via local (tunnel) interface? So all what I really want is to push few subnets via default GW rather than IPSEC interface. So incoming traffic (web apps) will go via peering (it's faster than IPSEC/BGP).

 

Thanks Dariusz