This message was deleted.

If the resources have different lifecycles (i.e., one needs to be deployed more frequently or on a different schedule than others), then I’d probably put those resources in a separate project and use stack references as needed.

What about to use 2 stacks in the same project instead of 2 different projects?

That’s possible too. In general I’d recommend using stacks to model different environments for your infrastructure.

I liked the stack reference idea, because in this case the second round of deployment is running on top of the first round of deployment, and second round runs more often too.

Happy to help, let us know if we can help further!