Bug #99779 for Net-Amazon-EC2: Signature Version 4 support

Fri Oct 24 14:15:25 2014 cloudcontrollers [...] gmail.com - Ticket created

Subject:	Signature Version 4 support
Date:	Fri, 24 Oct 2014 11:15:16 -0700
To:	bug-Net-Amazon-EC2 [...] rt.cpan.org
From:	Jack Murgia <cloudcontrollers [...] gmail.com>

Hello, This module does not work with new eu-central-1 region due to signature version requirement. Changing the default on line 207 to "4" does not work. Some discussion on the changes here in the aws forums: https://forums.aws.amazon.com/thread.jspa?messageID=578987&tstart=0

Fri Oct 24 15:19:20 2014 mrallen1 [...] yahoo.com - Correspondence added

On Fri Oct 24 14:15:25 2014, cloudcontrollers@gmail.com wrote: Show quoted text

> Hello, > > This module does not work with new eu-central-1 region due to signature > version requirement. Changing the default on line 207 to "4" does not work. > Some discussion on the changes here in the aws forums: > https://forums.aws.amazon.com/thread.jspa?messageID=578987&tstart=0

Yes aws signature 4 is a little more involved computationally than just changing the version string. Thanks for the report. I will look into this. It might be time to offload signing requests into a specialized library.

Fri Oct 24 15:19:20 2014 The RT System itself - Status changed from 'new' to 'open'

Sat May 02 03:05:09 2015 ec29340244 [...] streetwisemail.com - Correspondence added

From:

ec29340244 [...] streetwisemail.com

Attached is a patch that implements the v4 signature. It does not try to support both versions of the signature, opting in instead to just replace the current signature functionality with the v4 equivalent. This is because all EC2 in all AWS regions supports v4 and therefore I see no need to support v2. This is working well for us in production (on all regions). However, the temp-creds part is untested since we don't use those.

Subject:

Net.Amazon.EC2.v4_sig_patch

Download Net.Amazon.EC2.v4_sig_patch
application/octet-stream 5.5k

Message body not shown because it is not plain text.

Sat May 02 17:27:01 2015 mrallen1 [...] yahoo.com - Correspondence added

On Sat May 02 03:05:09 2015, ec29340244@streetwisemail.com wrote: Show quoted text

> Attached is a patch that implements the v4 signature. It does not try > to support both versions of the signature, opting in instead to just > replace the current signature functionality with the v4 equivalent. > This is because all EC2 in all AWS regions supports v4 and therefore I > see no need to support v2. > > This is working well for us in production (on all regions). However, > the temp-creds part is untested since we don't use those.

Thanks for the patch. It looks solid - and I will get it into a forthcoming release. I am wary about completely removing v2 support though since there are "EC2 compatible" APIs which still allow v2 signatures like Eucalyptus so I will probably leave both versions in the release. Thanks again for the patch. Really appreciate it.

Tue Jun 16 00:46:16 2015 mrallen1 [...] yahoo.com - Correspondence added

On Sat May 02 03:05:09 2015, ec29340244@streetwisemail.com wrote: Show quoted text

> Attached is a patch that implements the v4 signature. It does not try > to support both versions of the signature, opting in instead to just > replace the current signature functionality with the v4 equivalent. > This is because all EC2 in all AWS regions supports v4 and therefore I > see no need to support v2. > > This is working well for us in production (on all regions). However, > the temp-creds part is untested since we don't use those.

Just uploaded 0.30_1 to CPAN with support for v4 signatures based on your patch and v2 signatures as the default (for now) Thanks.

Tue Jun 16 00:46:23 2015 mrallen1 [...] yahoo.com - Status changed from 'open' to 'patched'

Wed Sep 02 21:53:24 2015 mrallen1 [...] yahoo.com - Status changed from 'patched' to 'resolved'

Wed Sep 02 21:54:06 2015 mrallen1 [...] yahoo.com - Correspondence added

On Sat May 02 03:05:09 2015, ec29340244@streetwisemail.com wrote: Show quoted text

> Attached is a patch that implements the v4 signature. It does not try > to support both versions of the signature, opting in instead to just > replace the current signature functionality with the v4 equivalent. > This is because all EC2 in all AWS regions supports v4 and therefore I > see no need to support v2.

Just released 0.31 to CPAN with a modified version of your original patch. Commit 5643c21