Summary

Currently the drivers automated Lambda testing scripts set up clusters in Atlas prod. These should be changed to use cloud-qa. See: https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/atlas/setup-variables.sh#L20

Motivation

Who is the affected end user?

Drivers performing AWS Lambda automated testing.

How does this affect the end user?

Drivers team Atlas budget runs over periodically.

How likely is it that this problem or use case will occur?

Will be seen often when clusters are not terminated in a timely fashion.

If the problem does occur, what are the consequences and how severe are they?

Drivers project goes over budget.

Is this issue urgent?

TBD

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

Yes - for drivers automated Atlas testing.
Does this ticket have any functional impact, or is it just test improvements?

Acceptance Criteria

• Update the drivers API URL in drivers-tools to point to cloud QA
• Update each driver's environment variables to point to the correct cloud QA value: DRIVERS_ATLAS_PUBLIC_API_KEY, DRIVERS_ATLAS_PRIVATE_API_KEY, and DRIVERS_ATLAS_GROUP_ID
• Update create cluster configuration to use M0 cluster instead of M10