Release: AWS SDK for Ruby 1.5.5

The latest API update to Amazon SES allows you to use Amazon Simple Notification Service (Amazon SNS) to receive notifications about bounces and complaints for emails that you send. Once configured, you will receive bounce and complaint feedback notifications for emails through Amazon SNS in a machine-readable format that you can process programmatically. For more information, see Feedback Notifications via Amazon SNS.

# configure bounce and complaint notifications to be sent
# to SNS toipcs for the identity "mydomain.com":

# create the topics
sns = AWS::SNS.new
complaints = sns.topics.create('mydomain.com-complaints')
bounces = sns.topics.create('mydomain.com-bounces')

# you should subscribe something to these topics (e.g.
# an email address, http endpoint, SQS queue, etc)

ses = AWS::SimpleEmailService.new
identity = ses.identities['mydomain.com']
identity.complaint_topic = complaints
identity.bounce_topic = bounces

The latest API update to Amazon S3 allows you to specify custom Access Control Lists (ACLs) when you upload objects. Previously you could specify a generic a canned ACL (e.g. :public_read, :private) at the same time as uploading an object, but the latest API update allows you to specify any custom ACL to be applied immediately when your object is uploaded.

s3 = AWS::S3.new
bucket = s3.buckets.create('my-bucket', :grants => {
  :grant_read => { 
    :uri => "http://acs.amazonaws.com/groups/global/AllUsers", # uri
  },
  :grant_full_control => [
    { :email_address => 'foo@bar.com' }, # email address
    { :id => 'abc...mno' }               # cannonical user id
  ]
})
            

You can provide the following grants:

• :grant_read
• :grant_write
• :grant_read_acp
• :grant_write_acp
• :grant_full_control

Each grant accepts one or more grantees. Grantees may be provided as:

• a string (of comma delimited grantees)
• a grantee hash (with :id, :uri or :email_address)
• An array of grantee strings or grantee hashes

Added configuration options to control HTTP timeouts and debug logging.

# the new configuration options are:
AWS.config.http_open_timeout #=> new session timeout (15 seconds)
AWS.config.http_read_timeout #=> read response timeout (60 seconds)
AWS.config.http_idle_timeout #=> persistant connections idle longer are closed (60 seconds)
AWS.config.http_wire_trace #=> When true, HTTP wire traces are logged (false)

# you can update the timeouts (with seconds)
AWS.config(:http_open_timeout => 5, :http_read_timeout => 120)

# log to the rails logger
AWS.config(:http_wire_trace => true, :logger => Rails.logger)

# send wire traces to standard out
AWS.config(:http_wire_trace => true, :logger => nil)

You can now export Windows instances to S3.

# first prepare your bucket with the proper permissions
s3 = AWS::S3.new
bucket = s3.buckets['windows-images']
bucket.acl.change do |acl|
  acl.grant(:read_acp).to(:amazon_customer_email => 'vm-import-export@amazon.com')
  acl.grant(:write).to(:amazon_customer_email => 'vm-import-export@amazon.com')
end

# export an instance to s3
ec2 = AWS::EC2.new
task = ec2.instances['i-12345678'].export_to_s3(bucket)

# wait for the task status to be complete

# download the export
File.open('image.ova', 'w') {|f| f.write(task.s3_object.read) }

Updated bundle ca-bundle.cert

Updated AWS::AutoScaling::Request to use signature version 4.

Resolved an issue when creating a stack, the :template param was construed as a url string when it included "http": https://github.com/amazonwebservices/aws-sdk-for-ruby/pull/55.