[DRIVERS-2639] Fix handling of EC2 Instance Profile in EG Tests Created: 30/May/23  Updated: 21/Aug/23

Status: Implementing
Project: Drivers
Component/s: Evergreen Tools
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Steve Silvester Assignee: Steve Silvester
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by NODE-5325 Fix AWS ec2 404 errors Blocked
Issue split
split to RUBY-3291 Fix handling of EC2 Instance Profile ... Backlog
split to CDRIVER-4677 Fix handling of EC2 Instance Profile ... Closed
split to CSHARP-4714 Fix handling of EC2 Instance Profile ... Closed
split to CXX-2711 Fix handling of EC2 Instance Profile ... Closed
split to GODRIVER-2900 Fix handling of EC2 Instance Profile ... Closed
split to JAVA-5066 Fix handling of EC2 Instance Profile ... Closed
split to MOTOR-1150 Fix handling of EC2 Instance Profile ... Closed
split to NODE-5441 Fix handling of EC2 Instance Profile ... Closed
split to PYTHON-3825 Fix handling of EC2 Instance Profile ... Closed
split to RUST-1699 Fix handling of EC2 Instance Profile ... Closed
split to PHPC-2324 Fix handling of EC2 Instance Profile ... Scheduled
Related
Driver Changes: Needed - No Spec Changes
Downstream Changes Summary:

Add appropriate Evergreen Config to restore the Instance Profile that is removed during the AWS Web Identity test.

See example commit in Python: https://github.com/mongodb/mongo-python-driver/commit/2fe01929e93929cb904aafac1038fadd3d324395

Start date:
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4677 Fixed 1.24.5
CXX-2711 Won't Do
CSHARP-4714 Fixed 2.22.0
GODRIVER-2900 Done
JAVA-5066 Fixed 4.11.0
NODE-5441 Done
MOTOR-1150 Duplicate
PYTHON-3825 Duplicate
PHPC-2324 Scheduled
RUBY-3291 Backlog
RUST-1699 Fixed 2.7.0

 Description   

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



 Comments   
Comment by Githook User [ 01/Jun/23 ]

Author:

{'name': 'Steven Silvester', 'email': 'steven.silvester@ieee.org', 'username': 'blink1073'}

Message: DRIVERS-2639 Fix handling of EC2 Instance Profile in EG Tests (#313)
Branch: master
https://github.com/mongodb-labs/drivers-evergreen-tools/commit/06c0fb866ee6d2071786c48151aed27672163441

Comment by Steve Silvester [ 01/Jun/23 ]

jason.walsh@mongodb.com is there anything that needs to be done once we implement this across the drivers, such as reaping all the active hosts?

Generated at Thu Feb 08 08:26:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.