[deltalake_aws] Allow configuring separate endpoints for S3 and DynamoDB clients. #2498
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
rtyler
added
good first issue
|
Hi @adamfaulkner-at , I am taking a look |
ion-elgreco
pushed a commit
that referenced
this issue
Jun 7, 2024
# Description Add custom dynamodb endpoint configuration Users can specify dynamodb endpoint in the map or set the environment variable `AWS_ENDPOINT_URL_DYNAMODB` to override dynamodb client endpoint. # Related Issue(s) [2498](#2498) # Documentation <!--- Share links to useful documentation --->
|
Thank you so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
aws_configsupports the use of custom endpoints. This is currently exposed via theAWS_ENDPOINT_URLoption 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)
The text was updated successfully, but these errors were encountered: