In the doc describing the use of s3_credentials_config, arguments are defined as AWS when they actually appear to be for anything S3.
This is confusing to users utilizing tools like minio (I see more of these than AWS S3 users) since it appears to be AWS-specific, but there are no apparent configurations for the rest of the s3-verse. We've tested by adding credentials in this block under the hypthothesis that they would work for other S3 providers (Minio in this case) and the credentials were communicated correctly to the s3 provider.
If it's not accurate, we should remove the AWS label from any arguments that are not AWS exclusive, but instead just conform to the S3 standards.
Description
In the doc describing the use of
s3_credentials_config, arguments are defined asAWSwhen they actually appear to be for anythingS3.This is confusing to users utilizing tools like minio (I see more of these than AWS S3 users) since it appears to be AWS-specific, but there are no apparent configurations for the rest of the s3-verse. We've tested by adding credentials in this block under the hypthothesis that they would work for other S3 providers (Minio in this case) and the credentials were communicated correctly to the s3 provider.
If it's not accurate, we should remove the AWS label from any arguments that are not AWS exclusive, but instead just conform to the S3 standards.