@michmoor Thanks. Gonna do my best to answer.
Essentially I have (2) /29's that are used for connecting to 2 public clouds via BGP. So when I say connection 1 is working, consider it cloud 1. My ASN covers both of my /29's.
Cloud 2 is the one that is not working. When I run a tracert from a workstation to a resource on each cloud, the tracert comes back with many ID'd hops for cloud 1, but cloud 2 only gets to the IP of the FW interface and then all other hops fail to ID.
I do not have a Gateway setup for either of them. This environment is not internet connected so it is just LAN to cloud and that's it. The routes retrieved from each cloud is not expected to be the exact same so it is not surprising that the count is different. Each cloud has different prefixes for different parts of the cloud that we will need to access.
The local-pref and as-path is something I am not familiar with. I see it in the BGP settings and route maps. How could I set this up so that it knows how to route? I mean I thought the routing was ok because the test for cloud 2 goes to my FW interface used for cloud 2, but it seems to get lost after that hop.