GitHub user paepke opened a pull request:

    https://github.com/apache/libcloud/pull/796

    amazon suggests using signature_version 4 for accessing the elasticlo…

    ## [LIBCLOUD-824] Elastic loadbalancer signature version 4
    
    ### Description
    
    
    At least the region eu-central-1 does not support Signature Version 2.
    At 
http://docs.aws.amazon.com/ElasticLoadBalancing/latest/APIReference/using-query-api.html
 is stated that newer applications should support Version 4 as the standard 
signing.
    See [Amazon ELB 
Docs](http://docs.aws.amazon.com/ElasticLoadBalancing/latest/APIReference/using-query-api.html).
    
    
    ### Status
    
    - done, ready for review
    
    ### Checklist (tick everything that applies)
    
    - [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
    - [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/paepke/libcloud LIBCLOUD-824_elb_signature_v4

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/796.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #796
    
----
commit fc7a719b234a529bfe839b62805bb50c3fc3c99a
Author: Tobias Paepke <tobias.pae...@fhe3.com>
Date:   2016-05-27T13:16:00Z

    amazon suggests using signature_version 4 for accessing the 
elasticloadbalancing api. Currently at least eu-central-1 requires using this 
version in my case.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to