Add a provider to support EKS Pod Identity#87
Merged
onno-vos-dev merged 2 commits intoaws-beam:masterfrom Jul 21, 2025
Merged
Conversation
Co-authored-by: Ryan Spore <ryan@mechanical-orchard.com>
Member
|
LGTM Linter is unhappy though due to tabs in Once merged, I can follow up and bump deps across |
Contributor
|
Got the formatting, but had a bit of a fight with dialyzer over types. I ended up expanding the value side of |
onno-vos-dev
approved these changes
Jul 21, 2025
Member
|
Released as 0.3.5 thank you both! 🙇 ❤️ |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a credential provider that can acquire credentials using the EKS Pod Identity system. This enables authenticating to AWS services from Kubernetes pods running in AWS EKS.
Licensing:
This contribution is made by employees of Mechanical Orchard, Inc. under the terms of the project’s license.