branch --> DC2 --> DC1 --> AWS
branch --> DC2 --> AWS
Next Peer Service Route
So, if we don't need to go branch-DC2-DC1-AWS and preserve existing sessions upon failover, then we don't need to use next-peer service route.
So, for non-resilient failover I would create two paths:
Branch --> DC1 & Branch --> DC2
Use different neighborhoods with their own respective Vector-to-DC1 and Vector-to-DC2.
In the service policy simply order the two vectors such that Vector-to-DC1 is at the top of the list.
This will do the trick.