[MONGOCRYPT-188] Support other AWS credential mechanisms Created: 26/Mar/19 Updated: 13/Feb/20 Resolved: 15/Oct/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
AWS applications in production often use other mechanisms to pass credentials into their application. For example, see the various ways credential can be supplied to boto3, the Python AWS client. libmongocrypt can support these with additional help from the driver. For temporary credentials and using EC2 instance metadata, this would amount to making additional HTTP requests, and reacting to expired credentials. |