This repository was archived by the owner on Apr 24, 2025. It is now read-only.
chore: use aws-sdk to increase aws support in eks pods #262
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## next #262 +/- ##
==========================================
+ Coverage 36.10% 36.28% +0.17%
==========================================
Files 185 186 +1
Lines 2703 2737 +34
Branches 496 507 +11
==========================================
+ Hits 976 993 +17
- Misses 1722 1739 +17
Partials 5 5
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
amille44420
force-pushed
the
feat/aws
branch
2 times, most recently
from
141ccb6 to
ee6b11e
Compare
When running in EKS pod with a ServeAccount trusted by an IAM role, the application can get credentials directly from the SA to call AWS API.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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
aws4on additional dependencies when building for production, required to support passwordless authentication with Mongo Atlas & AWS IAM