[DRIVERS-2623] AWS Lambda metadata detection logic is too permissive Created: 04/May/23 Updated: 20/Oct/23 Resolved: 20/Oct/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | FaaS, Handshake |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Shane Harvey | Assignee: | Shane Harvey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Teams that have already implemented DRIVERS-2209 must tweak the AWS lambda detection logic as described in this commit: Other teams should implement this change at the same time as DRIVERS-2209. |
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Engineering Lead: | |
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
DRIVERS-2209 outlined that if the AWS_EXECUTION_ENV env var is present, the app is running on AWS Lambda. This turns out to be too permissive because AWS_EXECUTION_ENV is used in other non-Lambda envs. For example the Windows evergreen machines have AWS_EXECUTION_ENV=EC2. According to Lambda env var docs, I believe the driver needs to validate that the AWS_EXECUTION_ENV var begins with the "AWS_Lambda_" prefix:
|
| Comments |
| Comment by Githook User [ 05/May/23 ] |
|
Author: {'name': 'Shane Harvey', 'email': 'shnhrv@gmail.com', 'username': 'ShaneHarvey'}Message: |
| Comment by Shane Harvey [ 05/May/23 ] |