Complete Construct Model

[awsmjs]

Description

It’s clear that constructs are imperative to the CDK experience. We repeatedly hear from CDK builders that the most important improvement that the CDK can make for its construct experience would be to provide greater service coverage. Because of this, the CDK team is investigating how we can provide more comprehensive AWS service coverage. In the past, the CDK has relied on community and in-house authored constructs to address construct demand. In the future, our goal is to bring CDK builders a complete and consistent construct model through largely autogenerated means. This model would provide builders with Day 1 support of AWS services--the moment services are launched--complete with the features that builders love in their L2s. As we are investigating this effort, it’s possible that there will be gradual rollouts for us to realize this goal. If you have any feedback or comments on this, we would highly appreciate you sharing them as a comment within this RFC.

[alecl]

It would be great to prioritize the EventBridge Scheduler L2 targets moving out of alpha. It's tough to justify moving to an API that may have vastly breaking changes (what Alpha implies) happen at any time.

In particular, the Lambda Invoke one is the highest value for my groups and likely many others.

https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-scheduler-targets-alpha/lib/lambda-invoke.ts

[gshpychka]

To be honest, it's not clear how you could achieve L2s via autogenerated means - could you give an example? As far as I understand, the purpose of L2 Constructs is to provide developers with opinionated abstractions - someone in the loop must be injecting these opinions.