I'm used to creating one API Gateway with all the routes for my application. I think the implication of creating two API stacks is to create two separate API Gateways. Is this assumption correction?

You can reference an existing api gateway instance if i recall correctly. I guess separating api’s into different stacks is worth it if you have huge api’s, but until now I didn’t find the need specifically

Hey @Jason S, you can just create 1 API in one of the stacks, and pass it to the other stack to add more routes to it. This is what @Arpad was suggesting and it often makes more sense than creating 2 separate API.

This is perfect thanks Frank