[
https://issues.apache.org/jira/browse/HADOOP-18683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933076#comment-17933076
]
Steve Loughran commented on HADOOP-18683:
-----------------------------------------
returning to this, I think we need a flag to indicate that the client is
in-AWS, irrespective of type/location of the s3 store.
Within EC2 we should rely on IAM as a fallback for credentials and for the
region of the bucket, falling back to probing us-central only if that doesn't
work.
> S3A Add new store vendor config option
> --------------------------------------
>
> Key: HADOOP-18683
> URL: https://issues.apache.org/jira/browse/HADOOP-18683
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.5
> Reporter: Ahmar Suhail
> Priority: Minor
>
> Add in a new fs.s3a.store.vendor config, where users can specify the storage
> vendor they are using (eg: aws, netapp, minio).
> This will allow us to configure S3A correctly per vendor. For example, if the
> vendor is not AWS, you probably want to use ListObjectsV1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
