swaminathanmanish commented on issue #11761:
URL: https://github.com/apache/pinot/issues/11761#issuecomment-1762238755
> > > What do you think about downgrading the AWS-SDK version? (only in the
environment with the problem, not in the official release of course)
> >
> >
> > Just trying to understand the scope of impact - Looks like this impacts
only **DefaultCredentialsProvider** and not when you provide the credentials
(from **S3PinotFS**)
> > ` try { if (StringUtils.isNotEmpty(s3Config.getAccessKey()) &&
StringUtils.isNotEmpty(s3Config.getSecretKey())) { AwsBasicCredentials
awsBasicCredentials = AwsBasicCredentials.create(s3Config.getAccessKey(),
s3Config.getSecretKey()); awsCredentialsProvider =
StaticCredentialsProvider.create(awsBasicCredentials); } else {
**awsCredentialsProvider = DefaultCredentialsProvider.create();** }`
>
> We can't use access and secret keys on AWS as it is against our IT
security policy. We have to use role based access. Also does this not impact
other parts of the code where aws resources are accessed besides minion tasks
(like deep store)?
Tracking down when this update was made (from 2.14 to 2.20). Im not sure if
downgrade is an option, since it was upgraded to address a memory leak -
https://github.com/apache/pinot/pull/10898
cc @klsince
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
