This release includes backward compatibility work on the "Expires" parameter.

Author: aws-sdk-dotnet-automation

generator/ServiceModels/s3/s3-2006-03-01.api.json

@@ -3566,7 +3566,7 @@
       "type":"boolean",
       "box":true
     },
-    "Expires":{"type":"timestamp"},
+    "Expires":{"type":"string"},
     "ExposeHeader":{"type":"string"},
     "ExposeHeaders":{
       "type":"list",

generator/ServiceModels/s3/s3-2006-03-01.docs.json

@@ -405,7 +405,7 @@
         "GetObjectOutput$Body": "<p>Object data.</p>",
         "GetObjectTorrentOutput$Body": "<p>A Bencoded dictionary as defined by the BitTorrent specification</p>",
         "PutObjectRequest$Body": "<p>Object data.</p>",
-        "RecordsEvent$Payload": "<p>The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might split the same record across multiple record frames instead of aggregating the results in memory. Some S3 clients (for example, the SDKforJava) handle this behavior by creating a <code>ByteStream</code> out of the response by default. Other clients might not handle this behavior by default. In those cases, you must aggregate the results on the client side and parse the response.</p>",
+        "RecordsEvent$Payload": "<p>The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might split the same record across multiple record frames instead of aggregating the results in memory. Some S3 clients (for example, the SDK for Java) handle this behavior by creating a <code>ByteStream</code> out of the response by default. Other clients might not handle this behavior by default. In those cases, you must aggregate the results on the client side and parse the response.</p>",
         "UploadPartRequest$Body": "<p>Object data.</p>",
         "WriteGetObjectResponseRequest$Body": "<p>The object data.</p>"
       }

generator/ServiceModels/s3/s3-2006-03-01.normal.json

@@ -4309,7 +4309,7 @@
       "type":"boolean",
       "box":true
     },
-    "Expires":{"type":"timestamp"},
+    "Expires":{"type":"string"},
     "ExposeHeader":{"type":"string"},
     "ExposeHeaders":{
       "type":"list",
@@ -10773,7 +10773,7 @@
       "members":{
         "Payload":{
           "shape":"Body",
-          "documentation":"<p>The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might split the same record across multiple record frames instead of aggregating the results in memory. Some S3 clients (for example, the SDKforJava) handle this behavior by creating a <code>ByteStream</code> out of the response by default. Other clients might not handle this behavior by default. In those cases, you must aggregate the results on the client side and parse the response.</p>",
+          "documentation":"<p>The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might split the same record across multiple record frames instead of aggregating the results in memory. Some S3 clients (for example, the SDK for Java) handle this behavior by creating a <code>ByteStream</code> out of the response by default. Other clients might not handle this behavior by default. In those cases, you must aggregate the results on the client side and parse the response.</p>",
           "eventpayload":true
         }
       },