Robust Tool
Rating: 9 out of 10
IncentivizedUse Cases and Deployment Scope
It has been used across the whole organization for doing stacks. It has helped us for doing specific environments for testing changes per branch (using GIT). In this way, fewer bugs are introduced to Production. It also allows preserving resources as it is very configurable. We can form stacks with just a basic configuration or with all of them.
Pros
- Configuring Stacks
- Deploying Stacks
- Managing Stacks
Cons
- Sometimes stacks are hard to delete due to the correlation of resources or configurations
- It could be tricky at first time when doing configurations
Likelihood to Recommend
It is really suited for professional environments. You can divide them into different stages, or with just specific changes. Those can be determined by the branch from the version control system (GIT, for example). If you are exploring and don't have too many resources this is not a very good option.
Alternatives
Heroku Platform
AWS CloudFormation has more features and robustness. It is suited for professional projects since it provides stability and a wide variety of options for configurations. These include not only dividing stacks by specific code changes, but also in regions. This allows more granularity and control over all stacks. If you want to delete them all just by a region, you can do it.