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

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

Add a monthly_replicated_write usage parameters to AWS [RDS Cluster] (https://github.com/infracost/infracost/blob/master/internal/resources/aws/rds_cluster.go) to track charges for Replicated Write I/Os (see https://aws.amazon.com/rds/aurora/pricing/#Database_Storage_and_IOs)

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/