chore: use aws-sdk to increase aws support in eks pods #262
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Allow the application to get credential from the AWS profile on the host. For our production environment the host being a container orchestrated by AWS EKS, we focus on using the ServiceAccount which may assume an AMI Role through OIDC.
By doing so, we will not be forced to provide access keys anymore and may improve our security standing.
Changes
aws4
on additional dependencies when building for production, required to support passwordless authentication with Mongo Atlas & AWS IAM