4 ms·
or you can utilize exported resources, like the article describes, and append your API endpoints to the "master" API Gateway resource that is not even in the sa
by kesor 8y ago
or you can utilize exported resources, like the article describes, and append your API endpoints to the "master" API Gateway resource that is not even in the same stack.
- olafalo 8y agoYes, that's the solution we came up with. One stack with lambdas, managed policies, roles, user pool, etc; one stack with the APIGateway::RestApi and some resources and methods, and then another stack with yet more resources and methods. This works, but I don't think it's a great solution. Wouldn't it be preferable to have one stack that encompasses the whole API for one service?