Driss Amri

The Java examples seem to have a lot of issues as well with Classes/Builders and imports: https://docs.aws.amazon.com/cdk/api/latest/java/index.html?software/amazon/awscdk/services/dynamodb/package-summary.html ``` Table table = new Table(this, "Table", new TableProps() .partitionKey(new Attribute().name("id").type(dynamodb.AttributeType.getSTRING()))); ``` should...

I have been using it for over a year, the biggest frustration is the size of the package. It makes my Lambda deployable 2-6x bigger just by adding this dependency

Sadly have been stuck on this and have to avoid enhanced dynamodb up to now in our native images. When this issue gets resolved it would simplify our business code...

If not this ticket, where should support for Intrinsic functions (Fn::Join) be requested for AutoPublishAlias?

Like mentioned above, integration with OTEL collector, Datadog integrations, Fluentbit sidecar..

Thanks for the great work! Is there any ETA on the 5.1.1 release for this?

I might misunderstand, but as there is already a L2 construct that is being used with [SpecRestApi](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_apigateway.SpecRestApi.html) it seems like there is value in connecting this with all best practises...

It was indeed my assumption that it would be under a different pattern like `aws-apigateway-openapi-lambda` Most of the code could/would be the same as the current pattern besides the setup...