Currently, in my API I have two very similar routes:
When ran locally the two routes are seen as a distinct from each other executing different logic. After deploying to my AWS lambda, the two routes are no longer seen as distinct and the logic for route 1, also runs for route 2. Is this some type of AWS policy that enforces distinct names for routes? Or is there something I'm missing?