-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Evergreen Tools
-
None
-
Needed - No Spec Changes
-
In DRIVERS-2605 we switched to using the EC2 Instance Profile that is added by the build team to each EG host.
However, we were still removing the instance profile as part of our AWS "web identity" tests, because the AWS SDKs would not use the web identity credentials if instance profile credentials were available.
When those hosts would get reused, they would not have the assigned instance profile. This would cause 404 errors in our AWS tests that relied on the predefined instance profile, and would also affect any other EG users that were relying on the new capability.
This ticket tracks ensuring that we restore the instance profile as part of the teardown of the EG build.
Relevant change to drivers-eg-tools: https://github.com/mongodb-labs/drivers-evergreen-tools/pull/307
Python driver update: https://github.com/mongodb/mongo-python-driver/pull/1218
Node driver update: https://github.com/mongodb/node-mongodb-native/pull/3686
- is depended on by
-
NODE-5325 Fix AWS ec2 404 errors
- Blocked
- split to
-
RUBY-3291 Fix handling of EC2 Instance Profile in EG Tests
- Backlog
-
CDRIVER-4677 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
CSHARP-4714 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
CXX-2711 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
GODRIVER-2900 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
JAVA-5066 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
MOTOR-1150 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
NODE-5441 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
PHPC-2324 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
PYTHON-3825 Fix handling of EC2 Instance Profile in EG Tests
- Closed
-
RUST-1699 Fix handling of EC2 Instance Profile in EG Tests
- Closed