For some reason the AWS SDK changed from numeric version numbers to a string version in the latest release: https://github.com/amazonwebservices/aws-sdk-for-php/commit/846506794c96....

Not exactly sure how we want to deal with this. One possibility seems to be to detect version number form the XML files that still use a numeric version. I am hoping this is a mistake which I have posted an issue to find out (https://github.com/amazonwebservices/aws-sdk-for-php/pull/30).

For those who just want a fix
If you want to fix locally make the following change https://github.com/boombatower/aws-sdk-for-php/commit/6d8d5ac83ccc15f98b... or checkout the version branch of my fork https://github.com/boombatower/aws-sdk-for-php/tree/version.

CommentFileSizeAuthor
#4 screenshot.png13.28 KBDrupalDan
#4 screenshot_status-report.png9.5 KBDrupalDan
#4 screenshot-compatibility-test.png26.5 KBDrupalDan
#2 1593454-version-make.patch820 bytesboombatower
#1 1593454-version.patch981 bytesboombatower
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

boombatower’s picture

boombatower CreditAttribution: boombatower commented
Title: Determine how to deal with non-numeric version of SDK » Determine how to deal with non-numeric version of SDK (fix for SDK 1.5.6)
FileSize
1593454-version.patch981 bytes

Update title for those looking for fix and attached a patch for quick application or drush make script.

boombatower’s picture

boombatower CreditAttribution: boombatower commented
Assigned: Unassigned » boombatower
Category: feature » task
Status: Active » Needs review
FileSize
1593454-version-make.patch820 bytes

This will patch against the make file for awssdk will add the patch in #1 to the Amazon SDK to reversion the version number. If you are building your site using drush make files you can simply add this patch to the awssdk in your drush make to alter it's make file before it is parsed.

For anyone looking for a quick fix use #1 or my github fork and/or does not know what all the drush make stuff is about.

boombatower’s picture

boombatower CreditAttribution: boombatower commented

Amazon employee confirmed it was an accident, so we just need to wait and see how they fix.

DrupalDan’s picture

DrupalDan CreditAttribution: DrupalDan commented
FileSize
screenshot-compatibility-test.png26.5 KB
screenshot_status-report.png9.5 KB
screenshot.png13.28 KB

@boombatower, I made the change in the sdk.class.php and it seems that it works! But what also follows that is the message that: Your PHP environment does not support the minimum requirements for the AWS SDK for PHP. I suppose it has something to do with SSL, right? Is there any way around to make local sites have SSL to meet the mini requirements, so that we can test everything out before moving into a production site?

Thanks for the fix and everything.

seaji’s picture

seaji CreditAttribution: seaji commented

What the path to sdk.class.php should be?
I tried:
sites/all/libraries/aws-sdk-for-php/sdk.class.php
sites/all/libraries/awssdk/sdk.class.php
sites/all/libraries/AWSSDK/sdk.class.php
None worked for me.
I use:
- sdk-1.5.6
- AWS SDK for PHP 7.x-5.3
- pached version of sdk.class.php from https://raw.github.com/boombatower/aws-sdk-for-php/version/sdk.class.php

boombatower’s picture

boombatower CreditAttribution: boombatower commented

The path should be sites/all/libraries/awssdk/sdk.class.php. Cleared cache and all? otherwise please open a support request.

boombatower’s picture

boombatower CreditAttribution: boombatower commented

@DrupalDan: By having SSL it means that curl can make requests with SSL not that the site is setup so that the webserver can accept incoming requests over SSL (https). Meaning you do not need to install certificates and what not you should just enable ssl in curl configuration or install appropriate extensions. In many cases you need to install the package that contains the list of certificate authorities so that it works.

DrupalDan’s picture

DrupalDan CreditAttribution: DrupalDan commented

Hi boombatower, good to hear from you again.

I google "enable curl" and I found that I can enable curl by uncommenting the line in php.ini

;extension=php_curl.dll

I checkeded the status report and the message in red is gone and everything seems work! I'm just a little cruious as to the installation of the package as you suggested. Do you mean it is better to enable curl by installing any package related for this purpose instead of making the change in php.ini?

I wouldn't be able to figure everything out and get things working without your help. Thanks for everything!

seaji’s picture

seaji CreditAttribution: seaji commented

Cache clear helped me.

boombatower’s picture

boombatower CreditAttribution: boombatower commented
Status: Needs review » Fixed

@DrupalDan: Depending on your distribution (assuming linux) there should be a package to enable curl for you. Additionally there should be one for the certificates, but if you are on windows or you may already have it installed then you are fine. Good to hear it worked out.

Amazon made an updated release with the fix to the version constant. I have listed the 1.5.6 release as incompatible on the compatibility page (http://drupal.org/node/1396596) and linked to this issue for the patch. Otherwise things should work with the latest release, but please re-open or file a new issue if they do not.

DrupalDan’s picture

DrupalDan CreditAttribution: DrupalDan commented

@boombatower, good to hear from you again! My local site is on windows but my server is linux, I think. I will check with my hosting provider to know how to enable curl with that package. Again, thanks for everything.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

clevername’s picture

clevername CreditAttribution: clevername commented

Also be sure to enable SSL module for Apache if you're getting the cUrl SSL error in the compatibility test screen. This can be down from Ubuntu with:
sudo a2enmod ssl