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 I create a Subnet using ec2.Subnet.from_subnet_attributes and don't specify a routeTableId, I'm getting the following warning:

[Warning at /euc1-dv-rest-alb-alb/subnet-0] No routeTableId was provided to the subnet at 'euc1-dv-rest-alb-alb/subnet-0'. Attempting to read its .routeTable.routeTableId will return null/undefined. (More info: https://github

I suggest adding MongoDB Atlas to the supported cloud as a feather.

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, they generate extra noise for issue followers and do

With v0.9.22 of the CLI, I took me a while to debug an issue as infracost breakdown --path examples/terraform --usage-file BLAH.yaml worked even though the file BLAH.yaml didn't exist. We should throw a nice error like we do for the config-file:

> infracost breakdown --config-file BLAH.yaml
Error: config file does not exist at BLAH.yaml

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/