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 configuring separate endpoints for S3 and DynamoDB clients. #2498

Open
adamfaulkner-at opened this issue May 10, 2024 · 0 comments
Labels
binding/rust Issues for the Rust crate enhancement New feature or request good first issue Good for newcomers storage/aws AWS S3 storage related

Comments

@adamfaulkner-at
Copy link

Description

aws_config supports the use of custom endpoints. This is currently exposed via the AWS_ENDPOINT_URL option and appears to be used for both DynamoDB and S3 clients.

It would be helpful if I could provide separate endpoints for DynamoDB and S3. Ideally, I would be able to pass in a DynamoDB client and an S3 client or object store directly, instead of interacting through the options hashmap full of strings.

Use Case

In my test environment, separate processes mock S3 and DynamoDB, and listen on different ports, so I cannot provide a single endpoint that does both.

Related Issue(s)

@adamfaulkner-at adamfaulkner-at added the enhancement New feature or request label May 10, 2024
@rtyler rtyler added good first issue Good for newcomers binding/rust Issues for the Rust crate storage/aws AWS S3 storage related labels May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binding/rust Issues for the Rust crate enhancement New feature or request good first issue Good for newcomers storage/aws AWS S3 storage related
Projects
None yet
Development

No branches or pull requests

2 participants