[ 
https://issues.apache.org/jira/browse/FLUME-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zeeshan khan updated FLUME-2554:
--------------------------------
    Description: 
The AWS Frankfurt data center supports only the newer AWS authentication 
mechanism version 4 (generally called AWS4, AWS4-HMAC-SHA256 or just V4). 
Flume-ng currently doesn’t support the V4 and hence cannot be used with the 
Frankfurt data center. 
The command line or the flume-env.sh option 
-Dcom.amazonaws.services.s3.enableV4 also doesnt work, hence it is an issue at 
the toolkit/SDK level: 
https://bitbucket.org/jmurty/jets3t/issue/183/support-for-aws-signature-version-4


  was:
The Frankfurt data center supports only the newer AWS authentication mechanism 
version 4 (generally called AWS4, AWS4-HMAC-SHA256 or just V4). 
Flume-ng currently doesn’t support the V4 and hence cannot be used with the 
Frankfurt data center. 
The command line or the flume-env.sh option 
-Dcom.amazonaws.services.s3.enableV4 also doesnt work, hence it is an issue at 
the toolkit/SDK level: 
https://bitbucket.org/jmurty/jets3t/issue/183/support-for-aws-signature-version-4



> Support for AWS Authentication Version 4, AWS4, AWS4-HMAC-SHA256
> ----------------------------------------------------------------
>
>                 Key: FLUME-2554
>                 URL: https://issues.apache.org/jira/browse/FLUME-2554
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Zeeshan khan
>            Priority: Critical
>
> The AWS Frankfurt data center supports only the newer AWS authentication 
> mechanism version 4 (generally called AWS4, AWS4-HMAC-SHA256 or just V4). 
> Flume-ng currently doesn’t support the V4 and hence cannot be used with the 
> Frankfurt data center. 
> The command line or the flume-env.sh option 
> -Dcom.amazonaws.services.s3.enableV4 also doesnt work, hence it is an issue 
> at the toolkit/SDK level: 
> https://bitbucket.org/jmurty/jets3t/issue/183/support-for-aws-signature-version-4



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to