Release: AWS SDK for PHP 1.3.7

Auto Scaling Features: SNS Notifications and Recurring Scheduled Events

With Amazon SNS notifications, you can now be notified whenever Auto Scaling launches or terminates Amazon EC2 instances for you. Because it uses Amazon SNS, you can choose to receive notifications in formats that are best suited to you and your applications, including HTTP/HTTPS, Email/Email-JSON, or Amazon SQS.

Using Recurrence for scheduled scaling activities, you can now scale your Auto Scaling group on a repeating schedule.

To learn more about Auto Scaling, visit: http://aws.amazon.com/autoscaling.

Documentation Errors

A number of minor typographical errors have been resolved.

Object Version URLs

The documentation for AmazonS3::get_object_url() has been updated to document the versionId parameter.

2GB limit for 32-bit stacks

Because PHP's integer type is signed and many platforms use 32-bit integers, the AWS SDK for PHP does not correctly handle files larger than 2GB on a 32-bit stack (whereby "stack" includes CPU, OS, web server, and PHP binary). This is a well-known PHP issue.

The recommended solution is to use a 64-bit stack, such as the 64-bit Amazon Linux AMI with the latest version of PHP installed.

For more information, please see: PHP filesize: Return values. A workaround is suggested in AmazonS3::create_mpu_object() with files bigger than 2GB.

Expiring request signatures

When leveraging AmazonS3::create_mpu_object(), it's possible that later parts of the multipart upload will fail if the upload takes more than 15 minutes.

Too many open file connections

When leveraging AmazonS3::create_mpu_object(), it's possible that the SDK will attempt to open too many file resources at once. Because the file connection limit is not available to the PHP environment, the SDK is unable to automatically adjust the number of connections it attempts to open.

The solution is to increase the part size so that fewer file connections are opened.

Exceptionally large batch requests

When leveraging the batch request feature to execute multiple requests in parallel, it's possible that the SDK will throw a fatal exception if a particular batch pool is exceptionally large and a service gets overloaded with requests.

This seems to be most common when attempting to send a large number of emails with the SES service.