Use Case

We are still seeing the "AWS_PROFILE is not set" issues in CI: https://spruce.mongodb.com/task/mongo_node_driver_next_ubuntu2004_test_mongodb_aws_aws_latest_auth_test_run_aws_auth_test_AssumeRoleWithWebIdentity_with_AWS_ROLE_SESSION_NAME_unset_cb88b05da0f0fe45acffb5e65d7602f7dc2f64a1_25_04_04_14_17_03/logs?execution=0

From talking with Steve over slack (thread here), he recommends

1. assuming the role needed to fetch secrets
2. explicitly set the new credentials into the environment for subsequent setup steps

This will avoid relying on the instance profile to fetch secrets, and hopefully should resolve these failures.

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward