Update from code changes: EKS Pod Identity support for S3 credentials#1032
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: EKS Pod Identity support for S3 credentials#1032mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Document that
S3_USE_CREDENTIALS_FROM=ecsnow covers both classic ECS task roles and EKS Pod Identity, so self-hosted Lightdash deployments on EKS can use the documented setting instead of falling back to default SDK credential resolution.Changes
S3_USE_CREDENTIALS_FROM" subsection to the external object storage guide, including a provider table, an EKS Pod Identity example, and a note on the fall-through behavior when neitherAWS_CONTAINER_CREDENTIALS_RELATIVE_URInorAWS_CONTAINER_CREDENTIALS_FULL_URIis set.S3_USE_CREDENTIALS_FROMrow in the environment variables reference to mention both ECS task roles and EKS Pod Identity underecs.Context
Follows lightdash/lightdash#25743, which chains the Pod-Identity-aware
fromHttpcredential provider ahead offromContainerMetadatafor theecssource so EKS Pod Identity resolves correctly without a new config value.