Release: AWS SDK for iOS 1.7.1

Release Notes>SDKs>iOS>Release: AWS SDK for iOS 1.7.1
This release introduces support for global secondary indexes in Amazon DynamoDB, updates for Amazon EC2 with support for the latest service API version, Elastic Load Balancing cross-zone load balancing, new features in AWS Security Token Service, and resolves a few issues.


Submitted By: yi@AWS
Created On: December 13, 2013 2:38 AM GMT
Last Updated: December 13, 2013 3:00 AM GMT


Download the AWS SDK for iOS 1.7.1

New Features

Change Description

Amazon DynamoDB Global Secondary Indexes

Added support for the new global secondary index feature in Amazon DynamoDB. As with a local secondary index, you define a global secondary index by using an alternate key from a table and then issuing Query requests on the index. Unlike a local secondary index, the hash key for the global secondary index does not have to be the same as that of the table; it can be any scalar attribute from the table. The range key is optional and can also be any scalar table attribute. A global secondary index also has its own provisioned throughput settings, which are separate from those of the parent table.

For more information, see Global Secondary Indexes.

Amazon EC2 API Update The Amazon EC2 client in the SDK now supports API version 2013-10-15. This API version includes support for enabling the Enhanced Networking (SR-IOV) support for the new C3 instance types, and also introduces pagination for the DescribeInstances and DescribeTags operations. To use pagination, you should call setMaxResults() on an instance of DescribeInstancesRequest or DescribeTagsRequest. The default is to continue returning all the results.
AWS Security Token Service This release updates the AWS Security Token Service client to support identity federation using Security Assertion Markup Language (SAML) 2.0. For more information, check Creating Temporary Security Credentials for SAML Federation in the AWS Security Token Service guide.
Amazon Simple Email Service Amazon SES now supports Signature version 4 which provides improved security and performance.

Resolved Issues

Change Description
S3TransferManager Error Handling We resolved two issues related to exception/error handling in the S3TransferManager that occur when either the credentials used don't allow all necessary operations or the the source file for a download is no longer present. These errors could cause an uncatchable exception if exceptions were enabled in the SDK.
AmazonS3Client and S3TransferManager Date Handling A GitHub community member submitted a fix to correct Date handling in S3 requests. This bug would prevent S3TransferManager from processing operations that were in the queue for too long before beginning.
AmazonS3Client Memory Leak We resolved a memory leak that would occur if using the listObjectsInBucket method while the device was offline.

Supported API Versions

This release of the SDK supports the following API versions:

Service API Version
Amazon CloudWatch 2010-08-01
Amazon DynamoDB 2012-08-10
Amazon Elastic Compute Cloud (EC2) 2013-10-15
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 2012-06-01

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.