Release v2.1.23 - 2015-09-17

Tag release v2.1.23

References:
#925

• Upgrading - Aws::S3::Client - Deprecated two methods:

  • Aws::S3::Client#put_bucket_lifecycle
  • Aws::S3::Client#get_bucket_lifecycle

  These methods have been replaced by:

  • Aws::S3::Client#put_bucket_lifecycle_configuration
  • Aws::S3::Client#get_bucket_lifecycle_configuration

  Amazon S3 now permits multiple transitions for a single
  lifecycle rule. Previously, a lifecycle rule would
  return a transition value, or nil. Now it will always
  return an array.

• Feature - Aws::S3 - Added support for the new STANDARD_IA storage class,
  lifecycle transitions and cross region replication with storage class
  features.

Release v2.1.22 - 2015-09-17

Tag release v2.1.22

• Upgrading - Aws::S3::Client - Deprecated two methods:

  • Aws::S3::Client#put_bucket_lifecycle
  • Aws::S3::Client#get_bucket_lifecycle

  These methods have been replaced by:

  • Aws::S3::Client#put_bucket_lifecycle_configuration
  • Aws::S3::Client#get_bucket_lifecycle_configuration

  Amazon S3 now permits multiple transitions for a single
  lifecycle rule. Previously, a lifecycle rule would
  return a transition value, or nil. Now it will always
  return an array.

• Feature - Aws::S3 - Added support for the new STANDARD_IA storage class,
  lifecycle transitions and cross region replication with storage class
  features.

Release v2.1.21 - 2015-09-15

Tag release v2.1.21

References:
#923

• Feature - Aws::EC2 - Added two new fields to expose data encryption key id,
  and state message.

• Feature - Aws::EC2 - Added support for the new "Diversified" allocation
  strategy.

• Feature - Aws::ElasticFileSystem - Added support for optional mount
  target ID to the DescribeMountTargets operation.

• Feature - Aws::Route53 - Added support for calculated health checks and
  latency health checks.

• Issue - Aws::S3 - Resolved an issue which could raise a signature error
  when making reqeusts against an object where the key is prefixed
  with the bucket name. This only affects classic S3 signatures, not requests
  using signature version 4.

  See related GitHub issue #923.

Release v2.1.20 - 2015-09-10

Tag release v2.1.20

• Feature - Aws::IAM - Added two new APIs that enable programmatic access to the
  AWS Identity and Access Management policy simulator.

• Feature - Aws::S3::Object - Added a #move_to method that copies
  the object to the destination and then deletes the source object.

• Issue - Aws::S3::Client - Added support for errors returned from
  Amazon S3 in the body of HTTP 200 responses. Previously only
  the #complete_multipart_upload operation handled these errors.
  Extended this to #copy_object and #upload_part_copy.

• Issue - Aws::S3::Object - The #presigned_post method now respects
  the configured custom endpoint.

  obj = Aws::S3::Object.new("bucket", "key", endpoint: "http://custom-endpoint.com")
  obj.presigned_post.url
  #=> "http://bucket.custom-endpoint.com"

• Issue - Aws::S3::Presigner - Added validation to #presigned_url to
  ensure the :key option is not an empty string. This prevents a
  presigned :get_object URL from becoming a presigned :list_objects
  request on the bucket.

Release v1.66.0 - 2015-09-05

References: #870

• Issue - AWS::S3 - Resolved an issue where the SDK would not retry errors returned
  from Amazon S3 inside the bodies of 200 status code HTTP responses. This was
  correctly handled for AWS::S3::Client#complete_multipart_upload, but
  not for #copy_part, and :copy_object.

  This fix addresses an issue where managed multipart copies would raise an
  error about a missing etag. These operations should not be retried up to
  three times and raise a terminal error if they are not successful.

  See related GitHub issue #870.

Release v2.1.19 - 2015-09-03

Tag release v2.1.19

References:
#913, #914, #916, #917

• Feature - Aws::StorageGateway - Adds tagging support for AWS Storage Gateway.

• Issue - Aws::InstanceProfileCredentials - Expanded retry logic in the
  Aws::InstanceProfileCredentials class. Previously this class could
  raise JSON parse error if the instance metadata service responded but
  with an invalid JSON document. These errors will be retried 3 times now
  with backoff.

  See related GitHub issue #913.

• Feature - Aws::EC2 - Implemented Aws::EC2::VpcPeeringConnection#exists?.

  See related GitHub issue #916.

• Issue - Aws::EC2 - Added missing pagination configuraiton for the
  Aws::EC2::Client#describe_vpc_peering_connections operation. Without
  this, calling #each on the response fails to trigger paging and
  raises an error.

  See related GitHub issue #914.

Release v2.1.18 - 2015-08-31

Tag release v2.1.18

References:
#793, #890, #898, #901, #910, #912

• Feature - Aws::EC2 - Launch Amazon EC2 Spot instances that have the lowest
  price per unit of capacity using the updated RequestSpotFleet API. Define and
  set target capacity in any unit including instances, vCPUs, memory, storage,
  or network throughput. You can specify how much each instance type is worth to
  your application, and automatically adjust your bid price for each type. This
  enables you to bid on multiple instance types in a single request and
  provision cost-effective capacity, regardless of instance type.

• Feature - Aws::ElasticLoadBalancing - Added a waiter that will poll
  until an instance has been deregistered.

  See related GitHub issue #793.

• Issue - Aws::EC2 - Added a missing #load method for
  Aws::EC2::NetworkInterfaceAssociation.

  See related GitHub issue #890.

• Issue - Retries - No longer retrying non-networking errors generated during
  HTTP handling.

  See related GitHub issue #912.

Release v2.1.17 - 2015-08-27

Tag release v2.1.17

• Feature - Aws::ConfigService - Adds support for the
  #list_discovered_resources API.

Release v2.1.16 - 2015-08-25

Tag release v2.1.16

References:
#896, #907, #908, #911

• Feature - Aws::CodePipeline - Allows specification of an encryption key to use
  with the artifact bucket when creating and updating a pipeline.

• Feature - Logging - Now filtering potentially sensitive request parameters
  from logs. There is a default list of sensitive request parameters that
  should be filtered:

  require 'logger'
  
  kms = Aws::KMS::Client.new(logger: Logger.new($stdout))
  kms.encrypt({
    key_id: "key-arn",
    plaintext: "secret-data",
  })

  Produces:

  I, [2015-08-24T14:53:04.545354 #47906]  INFO -- : [Aws::KMS::Client 400 0.362187 0 retries] encrypt({key_id:"key-arn",plaintext:"[FILTERED]"})
  

  You can pass your own list of params to filter when you construct an
  Aws::Log::Formatter with a custom pattern.

  See related GitHub issue #908.

• Issue - Aws::PageableResponse::UnsafeEnumerableMethods - respond_to?
  was not being forwarded to ancestors and it was always retuning false
  except for #count.

Release v2.1.15 - 2015-08-20

Tag release v2.1.15

References:
#891, #899, #902, #903

• Issue - Aws::Glacier - Resolved an issue with how dates were serialized
  when specifying start and end dates with an inventory retrieval job.
• Feature - Aws::S3 - Added support for event notification filter rules.