Release: AWS SDK for Ruby 1.6.4

AWS::SimpleEmailService::Identity now supports the new DKIM attributes.

ses = AWS::SimpleEmailService.new

domain = ses.identities['my-domain-name.com']

domain.verify_dkim #=> returns tokens

domain.dkim_verification_status #= > '...'
domain.dkim_tokens #=> [...]
domain.dkim_enabled #=> true/false

In addition to string and numbers, you can now store binary attributes.

ddb = AWS::DynamoDB.new
table = ddb.tables['table-name']
table.hash_key = { 'id' => :string }

i = table.items.create('id' => 'abc', 'data' => AWS::DynamoDB::Binary.new('data'))
i.attributes['data']
#=> returns an AWS::DynamoDB::Binary object that is a string containing 'data'
            

Binary attributes are automatically base 64 encoded over the wire, but are stored in Dynamo as binary (reducing store costs).

You can use binary attributes in your key shema as well.

ddb.tables.create('table-name', 10, 5, :hash_key => { :id => :binary })
            

You can also provide binary attributes directly to the AWS::DynamoDB::Client.

ddb.client.put_item(
  :table_name => "table-name",
  :item => {
    "id" => {:s=>"abc"},
    "data" => {:b=>"data"}, # "data" will be encoded for you
  }
)

You can now set content disposition when performing a copy operation.

s3 = AWS::S3.new
s3.buckets['bucket-name'].objects['target'].copy_from('source', :content_disposition => '...')
s3.buckets['bucket-name'].objects['source'].copy_to('target', :content_disposition => '...')
s3.buckets['bucket-name'].objects['source'].move_to('target', :content_disposition => '...')
            

Resolved an issue that related to XML ordering elements. Root level options were not always getting properly serialized in the xml order expected.

Running tests no longer forces a dependancy on the simplecov gem.

Now escaping S3 object keys properly when calling AWS::S3::Client#delete_objects.