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?

Unlike the module aws_apigateway where I would just do

const api = new apigateway.RestApi(this, 'hello-api');
const plan = api.addUsagePlan('UsagePlan', {
  name: 'Easy',
  throttle: {
    rateLimit: 10,
    burstLimit: 2
  }
});

there doesnt seem to be an equivalent way of doing this in aws-apigatewayv2-alpha.

Reproduction Steps

I

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

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/