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.|
|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
Supported API Versions
This release of the SDK supports the following API versions:
|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|
|AWS Security Token Service||2011-06-15|
|Elastic Load Balancing||2012-06-01|
|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: