Amazon Web Services

Most of the tests that currently cover core functionalities depend heavily on (and sometimes test) internal implementation characteristics. While they should be testing whether the given implementation produces desired outcome (treating its implementation more as a black box).

_Current state of things is problematic for eventual internal improvements and refactors which occasionally we want t

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

What is the problem?

Cannot specify sslSupportMethod for CloudFront Distribution in distribution.ts.
I can specify minimumProtocolVersion but not sslSupportMethod.

Example of minimumProtocolVersion
https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-cloudfront/lib/distribution.ts#L222
https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-cloudfr

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

Previous discussion:

• infracost/infracost#953
• infracost/infracost#1172 (comment)

Infracost has a method of passing custom flags for when Infracost runs terraform plan, but it doesn't support passing custom flags to terraform init.

This will be useful for users who

1. Want to auto-upgrade modules using `terraform init -u

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/