mitchlloyd opened a new issue #10375:
URL: https://github.com/apache/druid/issues/10375


   ### Description
   
   Druid currently uses the 1.11.199 version of the AWS SDK and I need a 
feature available in a later version of the SDK.
   
   I need the feature in the AWS SDK that allows applications to use [the 
AWS_STS_REGIONAL_ENDPOINTS environment variable to configure regional STS 
endpoint 
usage](https://docs.aws.amazon.com/credref/latest/refdocs/setting-global-sts_regional_endpoints.html).
 I'm deploying Druid in an environment where I cannot use global STS endpoints 
because using regional endpoints is a [documented best practice from 
AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html).
 This environment variable configuration feature is [available in version 
1.11.658 and 
later](https://github.com/aws/aws-sdk-java/issues/2362#issuecomment-647835178).
   
   ### Motivation
   
   I would like to move off of my Druid fork and back onto an official Druid 
version some day. Upgrading the AWS SDK in Druid brings me one step closer to 
that goal.
   
   ### Solutions
   
   I'm currently running a fork of Druid based on 0.17.1 that uses version 
1.11.854 of the AWS SDK. I use Kinesis supervisors, and S3 for long-term 
segment data, and a custom CloudWatch event emitter that all appear to be 
working.
   
   Would the maintainers be open to a PR that updates the AWS SDK to 1.11.854?
   
   I also opened [a PR to add STS endpoint 
configuration](https://github.com/apache/druid/pull/10218) before I knew about 
this environment variable option. That PR adds new configuration which puts 
more burden on Druid users to find and configure settings for STS in ingest 
specs. Upgrading the AWS SDK avoids adding new ingest spec configuration 
options.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to