Amazon Web Services

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

Currently, we have websocket-related properties configured directly on provider level:

• provider.websocketsApiName
• provider.websocketsApiRouteSelectionExpression
• provider.websocketsDescription

This is not consistent with how iam, httpApi or

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to i

Describe the bug

When importing an existing EKS cluster into the stack with eks.Cluster.FromClusterAttributes, the KubectlLambdaRole property is ignored, and it uses the default lambda execution role instead. It works fine if you create the cluster with CDK instead.

Expected Behavior

The lambda that is created as part of methods like .AddServiceAccount should execute with th

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions

We are very interested in a a usage file feature. Currently, the breakdown command supports specifying it as a parameter. It brings additional complexity to our CI pipeline, as we try to use the same Terraform code for different environments (dev/qa/prod). And obviously, different environments produce different usage.

So to make

General Availability (GA) for docker compose v2 is "Almost There". With GA we could consider upgrading docker compose examples (sample project and [test](https://github.com/