[DRIVERS-834] AWS Auth support for AWS Lambda Created: 26/Feb/20  Updated: 06/Aug/20  Resolved: 26/Feb/20

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Clyde Bazile III (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related

 Description   

Cloud Product Managers asked for support for AWS Lambda in the IAM Auth project on Jan 9.

AWS Lambda functions can provide temporary credentials for a user if the function is is assigned an execution role. These are passed via environment variables AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN.

The client authentication should check these environment variables if there is not an explicit user name and password provided before the check for local instance metadata services.

IAM Auth design spec has been updated to reflect these changes. The server made these changes as part of SERVER-45471.

References:
https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#environment-variables


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