The CDK is pretty easy to use. It's a set of tools for creating cloud formation templates. The problem with the console is that some options might be missing.

The CDK is pretty easy to use. It's a set of tools for creating cloud formation templates. The problem with the console is that some options might be missing. For instance, when creating a cognition userpool, any auth0 standard attribute may be set to immutable; however, this option isn't available in the console. Serverless might be missi g options, but it allows that to be supplemented with writing raw cloudformation in the serverless document. I enjoy the CDK because it's one less layer of abstraction to deal with compared to serverless, and what's actually being deployed isn't hidden behind the yaml. It's programmatic, maintained by aws, and the documentation is pretty stellar. The only downside is that it's not complete, so sometimes raw cloudformation will have to be written. Another thing to keep in mind that serverless and cdk allow for you to recycle time spent while just using the console does not in lost cases.