You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/06/27 16:07:52 UTC
[jira] [Updated] (HADOOP-13325) s3n fails to work with S3 Frankfurt
or Seol - 400 : Bad Request
[ https://issues.apache.org/jira/browse/HADOOP-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-13325:
------------------------------------
Summary: s3n fails to work with S3 Frankfurt or Seol - 400 : Bad Request (was: s3n fails to work with S3 Frankfurt or Seol)
> s3n fails to work with S3 Frankfurt or Seol - 400 : Bad Request
> ---------------------------------------------------------------
>
> Key: HADOOP-13325
> URL: https://issues.apache.org/jira/browse/HADOOP-13325
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.6.0
> Reporter: Steve Loughran
> Priority: Minor
>
> The Hadoop S3N {{s3n://}} client does not work with AWS S3 Frankfurt, S3 Seol.
> This is because these S3 installations support the V4 signing API.
> S3A *does* work with them —filing this JIRA just to provide a searchable bug report
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org