Summary

ECS is the only MONGODB-AWS auth flow with no test in drivers-evergreen-tools. tests/test-aws.sh covers assume-role, ec2, regular, session-creds, env-creds, web-identity and eks. ECS is absent, so a regression in that path is found only when a driver's own build breaks.

Motivation

Who is the affected end user?

Driver teams running the MONGODB-AWS ECS variant, and anyone changing auth_aws in drivers-evergreen-tools.

How does this affect the end user?

A regression reaches drivers before drivers-evergreen-tools notices it, so the driver team debugs a failure whose cause is in another repository.

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

Edge case. The ECS path itself changes rarely, but it shares aws_setup.sh and the secrets handling with the flows that change often.

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

A driver's ECS variant fails and the cause is not in their repository. Lost debugging time, no outage.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes. No functional impact.

Acceptance Criteria

• A task exercises the ECS flow against a real container and asserts the staged test script runs there.
• The task is not tagged pr, so it stays off pull request runs while remaining selectable.