Release: AWS SDK for iOS 1.4.4

Release Notes>iOS>Release: AWS SDK for iOS 1.4.4
This release adds support for long polling and Signature Version 4 in Amazon Simple Queue Service, support for Amazon DynamoDB consistent batch reads, an update to EC2 Spot Instance handling, support for archving Amazon S3 data to Amazon Glacier, support for the new Sydney region, and improved connection handling.


Submitted By: BobK@AWS
Latest Version: 1.4.4
Created On: November 14, 2012 2:24 AM GMT
Last Updated: November 14, 2012 4:38 PM GMT


Download the AWS SDK for iOS 1.4.4

New Features

Change Description
Amazon DynamoDB Consistent Batch Reads

The SDK now supports specifying consistent reads when performing a batch read operation in DynamoDB. The low-level client as well as the DynamoDBMapper utility both support specifying this new parameter.

Amazon DynamoDB CRC32 Consistency Checks

The SDK now automatically checks DynamoDB API requests for CRC32 checksum errors and retries requests when necessary.

EC2 Spot Instance Request Status

The SDK now support the latest API of EC2, which enables customers to determine the state of an EC2 Spot Instance request.

For more information, please read the service release notes.

Amazon Simple Queue Service Long Polling

Long polling allows for Amazon SQS to wait for a specified amount of time for a message to be available instead of returning an empty response if one is not available.

For more information about long polling, go to Amazon SQS Long Polling in the Amazon Simple Queue ServiceDeveloper Guide

Amazon Simple Queue Service Signature Version 4

Signature version 4 provides improved security and performance.

For more information about signature version 4, go to Query Request Authentication in the Amazon Simple Queue Service Developer Guide.

Amazon S3 - Archiving Objects to Amazon Glacier

Amazon S3 now provides a storage option that enables you to utilize Amazon Glacier's low-cost storage service for data archival. To archive objects, you define archival rules identifying objects and a timeline when you want Amazon S3 to archive these objects to Amazon Glacier. You can easily set the rules on a bucket using the Amazon S3 management console or programmatically using the SDK.

For more information, see Object Lifecycle Management.

New Asia Pacific (Sydney) Region - Endpoint Constants

Support for the new Asia Pacific (Sydney) Region has been added. Region endpoint constants have been added to AmazonEndpoints.h add helper methods have been updated to support returning endpoints in this new region.

Improved connection handling options for all clients

Developers can now set connection timeouts independently from request timeouts via the connectionTimeout property on the service clients (i.e. AmazonS3Client). Also, for longer connections using delegates, AmazonServiceRequests can be canceled.

Resolved Issues

Change Description
Inconsistent timeout handling for Amazon S3

This version corrects an inconsistency the AmazonS3Client which the could result in an increased number of timeouts on S3PutObjectRequests on iOS6.

Supported API Versions

This release of the SDK supports the following API versions:

Service API Version
Amazon CloudWatch 2010-08-01
Amazon DynamoDB 2011-12-05
Amazon Elastic Compute Cloud (EC2) 2012-10-01
Amazon Simple Email Service (SES) 2010-12-01
Amazon Simple Notification Service (SNS) 2010-03-31
Amazon Simple Queue Service 2012-11-05
Amazon Simple Storage Service (S3) 2006-03-01
Amazon SimpleDB 2009-04-15
Auto Scaling 2011-01-01
AWS Security Token Service 2011-06-15
Elastic Load Balancing 2011-11-15

Known Issues

Issue Description
AWS Persistence Framework for Core Data with iOS 5.0

While the rest of the AWS SDK for iOS still support iOS versions 4.3 and later, the AWS Persistence Framework for Core Data only supports iOS versions 5.0 and later.

Amazon S3 over 3G

Uploading large objects to Amazon S3 using 3G can fail frequently. The release of iOS v6 resolves this issue.

Amazon S3 client does not work around known Amazon S3 issues. The Amazon S3 library does not currently work around two known issues with the Amazon S3 API:
  • Bucket names can include '+' symbols in the name, but the '+' symbol does not get replaced in URL encodings and can result in spaces in bucket names instead.
  • It is possible to create an object with a key which includes characters that are not valid XML characters, which will cause an error in the response to the AmazonS3Client listObjects method. Refer to for guidelines on Amazon S3 keys.
©2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.