Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[deltalake_aws] Allow passing AWS_SESSION_TOKEN and other credentials more directly to DynamoDB client. #2497

Open
adamfaulkner-at opened this issue May 10, 2024 · 0 comments
Labels
enhancement New feature or request storage/aws AWS S3 storage related

Comments

@adamfaulkner-at
Copy link

Description

My understanding of the code here is that AWS_SESSION_TOKEN, AWS_SECRET_ACCESS_KEY, and AWS_ACCESS_KEY_ID are assigned to environment variables, and later inferred by the S3 client and the DynamoDB client. It would be nicer if they could be passed directly to these clients without being part of the process's environment.

I think an ideal solution would allow me to configure my own object store and dynamo client, and provide those when registering a table.

Use Case

My process is a big monolith with a bunch of stuff in it, completely unrelated to me. Many different identities are used in this process for many different purposes. Environment variables are a single global namespace, so it would be dangerous to plug my credentials in it.

Related Issue(s)

@adamfaulkner-at adamfaulkner-at added the enhancement New feature or request label May 10, 2024
@rtyler rtyler added the storage/aws AWS S3 storage related label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request storage/aws AWS S3 storage related
Projects
None yet
Development

No branches or pull requests

2 participants