aws-sdk-s3 1.102.0 → 1.103.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 5e460144a4d67350a975bcb1b28dded53872af939cb512c74bc7c1e73ff1e616
4
- data.tar.gz: cfd0bc9fb977e27ec33f3d497a1547e92808a13fd42b3e9b1ee7f6a73bec5771
3
+ metadata.gz: 15712b72bf9c4eceb463344aa738f5e520a02161776d0a2e0c501c589ffba31b
4
+ data.tar.gz: 44bd3b0c543a0bb6b31ff26da9e664b431b0497ca5157385671526a9bbe8c589
5
5
  SHA512:
6
- metadata.gz: c58146b420fb36c1468743f06899a3ce195499a72966a1fe99ead757b4257da9c5cd29133977c371fdbd6fd9f4480b33807a0baae30deecee4fbb94de7f5a72e
7
- data.tar.gz: 84bdb26904354cb178793d2f329bb428903a5765b76dff87e34e5030c1e132a41d1b22af39a37ae0df778d43b2da673fb92d18ab9a685bbe1ba9451b4b1f5096
6
+ metadata.gz: f4dc0b61914a6c48dac9858321b0a6eb972991e2938d39a10d105140c18fcf7a43d1d905654942033f44336e491e82d5ad178eb2fc84beac05ac1e059da98be7
7
+ data.tar.gz: 709d8e45a27f894622800dabb2ebb300f0d4b6f888c081987e42022b602d703aa22bd42fab179aeb976ee5ef12b98cb6b04d1663a49749b8693ea81b8099a2d3
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.103.0 (2021-09-16)
5
+ ------------------
6
+
7
+ * Feature - Add support for access point arn filtering in S3 CW Request Metrics
8
+
4
9
  1.102.0 (2021-09-02)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.102.0
1
+ 1.103.0
@@ -517,12 +517,12 @@ module Aws::S3
517
517
  # If `x-amz-server-side-encryption` is present and has the value of
518
518
  # `aws:kms`, this header specifies the ID of the Amazon Web Services Key
519
519
  # Management Service (Amazon Web Services KMS) symmetrical customer
520
- # managed customer master key (CMK) that was used for the object. If you
521
- # specify `x-amz-server-side-encryption:aws:kms`, but do not provide`
520
+ # managed key that was used for the object. If you specify
521
+ # `x-amz-server-side-encryption:aws:kms`, but do not provide`
522
522
  # x-amz-server-side-encryption-aws-kms-key-id`, Amazon S3 uses the
523
- # Amazon Web Services managed CMK in Amazon Web Services to protect the
524
- # data. If the KMS key does not exist in the same account issuing the
525
- # command, you must use the full ARN and not just the ID.
523
+ # Amazon Web Services managed key to protect the data. If the KMS key
524
+ # does not exist in the same account issuing the command, you must use
525
+ # the full ARN and not just the ID.
526
526
  # @option options [String] :ssekms_encryption_context
527
527
  # Specifies the Amazon Web Services KMS Encryption Context to use for
528
528
  # object encryption. The value of this header is a base64-encoded UTF-8
@@ -1465,33 +1465,33 @@ module Aws::S3
1465
1465
  # * {Types::CreateBucketOutput#location #location} => String
1466
1466
  #
1467
1467
  #
1468
- # @example Example: To create a bucket in a specific region
1468
+ # @example Example: To create a bucket
1469
1469
  #
1470
- # # The following example creates a bucket. The request specifies an AWS region where to create the bucket.
1470
+ # # The following example creates a bucket.
1471
1471
  #
1472
1472
  # resp = client.create_bucket({
1473
1473
  # bucket: "examplebucket",
1474
- # create_bucket_configuration: {
1475
- # location_constraint: "eu-west-1",
1476
- # },
1477
1474
  # })
1478
1475
  #
1479
1476
  # resp.to_h outputs the following:
1480
1477
  # {
1481
- # location: "http://examplebucket.<Region>.s3.amazonaws.com/",
1478
+ # location: "/examplebucket",
1482
1479
  # }
1483
1480
  #
1484
- # @example Example: To create a bucket
1481
+ # @example Example: To create a bucket in a specific region
1485
1482
  #
1486
- # # The following example creates a bucket.
1483
+ # # The following example creates a bucket. The request specifies an AWS region where to create the bucket.
1487
1484
  #
1488
1485
  # resp = client.create_bucket({
1489
1486
  # bucket: "examplebucket",
1487
+ # create_bucket_configuration: {
1488
+ # location_constraint: "eu-west-1",
1489
+ # },
1490
1490
  # })
1491
1491
  #
1492
1492
  # resp.to_h outputs the following:
1493
1493
  # {
1494
- # location: "/examplebucket",
1494
+ # location: "http://examplebucket.<Region>.s3.amazonaws.com/",
1495
1495
  # }
1496
1496
  #
1497
1497
  # @example Request syntax with placeholder values
@@ -1562,15 +1562,14 @@ module Aws::S3
1562
1562
  # You can optionally request server-side encryption. For server-side
1563
1563
  # encryption, Amazon S3 encrypts your data as it writes it to disks in
1564
1564
  # its data centers and decrypts it when you access it. You can provide
1565
- # your own encryption key, or use Amazon Web Services Key Management
1566
- # Service (Amazon Web Services KMS) customer master keys (CMKs) or
1567
- # Amazon S3-managed encryption keys. If you choose to provide your own
1565
+ # your own encryption key, or use Amazon Web Services KMS keys or Amazon
1566
+ # S3-managed encryption keys. If you choose to provide your own
1568
1567
  # encryption key, the request headers you provide in [UploadPart][1] and
1569
1568
  # [UploadPartCopy][6] requests must match the headers you used in the
1570
1569
  # request to initiate the upload by using `CreateMultipartUpload`.
1571
1570
  #
1572
1571
  # To perform a multipart upload with encryption using an Amazon Web
1573
- # Services KMS CMK, the requester must have permission to the
1572
+ # Services KMS key, the requester must have permission to the
1574
1573
  # `kms:Decrypt` and `kms:GenerateDataKey*` actions on the key. These
1575
1574
  # permissions are required because Amazon S3 must decrypt and read data
1576
1575
  # from the encrypted file parts before it completes the multipart
@@ -1578,11 +1577,10 @@ module Aws::S3
1578
1577
  # permissions][7] in the *Amazon S3 User Guide*.
1579
1578
  #
1580
1579
  # If your Identity and Access Management (IAM) user or role is in the
1581
- # same Amazon Web Services account as the Amazon Web Services KMS CMK,
1582
- # then you must have these permissions on the key policy. If your IAM
1583
- # user or role belongs to a different account than the key, then you
1584
- # must have the permissions on both the key policy and your IAM user or
1585
- # role.
1580
+ # same Amazon Web Services account as the KMS key, then you must have
1581
+ # these permissions on the key policy. If your IAM user or role belongs
1582
+ # to a different account than the key, then you must have the
1583
+ # permissions on both the key policy and your IAM user or role.
1586
1584
  #
1587
1585
  # For more information, see [Protecting Data Using Server-Side
1588
1586
  # Encryption][8].
@@ -1615,11 +1613,11 @@ module Aws::S3
1615
1613
  # option you use depends on whether you want to use Amazon Web
1616
1614
  # Services managed encryption keys or provide your own encryption key.
1617
1615
  #
1618
- # * Use encryption keys managed by Amazon S3 or customer master keys
1619
- # (CMKs) stored in Amazon Web Services Key Management Service
1620
- # (Amazon Web Services KMS) – If you want Amazon Web Services to
1621
- # manage the keys used to encrypt data, specify the following
1622
- # headers in the request.
1616
+ # * Use encryption keys managed by Amazon S3 or customer managed key
1617
+ # stored in Amazon Web Services Key Management Service (Amazon Web
1618
+ # Services KMS) – If you want Amazon Web Services to manage the keys
1619
+ # used to encrypt data, specify the following headers in the
1620
+ # request.
1623
1621
  #
1624
1622
  # * x-amz-server-side-encryption
1625
1623
  #
@@ -1629,7 +1627,7 @@ module Aws::S3
1629
1627
  #
1630
1628
  # <note markdown="1"> If you specify `x-amz-server-side-encryption:aws:kms`, but don't
1631
1629
  # provide `x-amz-server-side-encryption-aws-kms-key-id`, Amazon S3
1632
- # uses the Amazon Web Services managed CMK in Amazon Web Services
1630
+ # uses the Amazon Web Services managed key in Amazon Web Services
1633
1631
  # KMS to protect the data.
1634
1632
  #
1635
1633
  # </note>
@@ -1638,10 +1636,9 @@ module Aws::S3
1638
1636
  # Services KMS fail if you don't make them with SSL or by using
1639
1637
  # SigV4.
1640
1638
  #
1641
- # For more information about server-side encryption with CMKs stored
1642
- # in Amazon Web Services KMS (SSE-KMS), see [Protecting Data Using
1643
- # Server-Side Encryption with CMKs stored in Amazon Web Services
1644
- # KMS][11].
1639
+ # For more information about server-side encryption with KMS key
1640
+ # (SSE-KMS), see [Protecting Data Using Server-Side Encryption with
1641
+ # KMS keys][11].
1645
1642
  #
1646
1643
  # * Use customer-provided encryption keys – If you want to manage your
1647
1644
  # own encryption keys, provide all the following headers in the
@@ -1653,10 +1650,9 @@ module Aws::S3
1653
1650
  #
1654
1651
  # * x-amz-server-side-encryption-customer-key-MD5
1655
1652
  #
1656
- # For more information about server-side encryption with CMKs stored
1657
- # in Amazon Web Services KMS (SSE-KMS), see [Protecting Data Using
1658
- # Server-Side Encryption with CMKs stored in Amazon Web Services
1659
- # KMS][11].
1653
+ # For more information about server-side encryption with KMS keys
1654
+ # (SSE-KMS), see [Protecting Data Using Server-Side Encryption with
1655
+ # KMS keys][11].
1660
1656
  #
1661
1657
  # Access-Control-List (ACL)-Specific Request Headers
1662
1658
  #
@@ -1881,13 +1877,13 @@ module Aws::S3
1881
1877
  # ensure that the encryption key was transmitted without error.
1882
1878
  #
1883
1879
  # @option params [String] :ssekms_key_id
1884
- # Specifies the ID of the symmetric customer managed Amazon Web Services
1885
- # KMS CMK to use for object encryption. All GET and PUT requests for an
1886
- # object protected by Amazon Web Services KMS will fail if not made via
1887
- # SSL or using SigV4. For information about configuring using any of the
1888
- # officially supported Amazon Web Services SDKs and Amazon Web Services
1889
- # CLI, see [Specifying the Signature Version in Request
1890
- # Authentication][1] in the *Amazon S3 User Guide*.
1880
+ # Specifies the ID of the symmetric customer managed key to use for
1881
+ # object encryption. All GET and PUT requests for an object protected by
1882
+ # Amazon Web Services KMS will fail if not made via SSL or using SigV4.
1883
+ # For information about configuring using any of the officially
1884
+ # supported Amazon Web Services SDKs and Amazon Web Services CLI, see
1885
+ # [Specifying the Signature Version in Request Authentication][1] in the
1886
+ # *Amazon S3 User Guide*.
1891
1887
  #
1892
1888
  #
1893
1889
  #
@@ -2257,21 +2253,23 @@ module Aws::S3
2257
2253
  #
2258
2254
  # The S3 Intelligent-Tiering storage class is designed to optimize
2259
2255
  # storage costs by automatically moving data to the most cost-effective
2260
- # storage access tier, without additional operational overhead. S3
2261
- # Intelligent-Tiering delivers automatic cost savings by moving data
2262
- # between access tiers, when access patterns change.
2263
- #
2264
- # The S3 Intelligent-Tiering storage class is suitable for objects
2265
- # larger than 128 KB that you plan to store for at least 30 days. If the
2266
- # size of an object is less than 128 KB, it is not eligible for
2267
- # auto-tiering. Smaller objects can be stored, but they are always
2268
- # charged at the frequent access tier rates in the S3
2269
- # Intelligent-Tiering storage class.
2270
- #
2271
- # If you delete an object before the end of the 30-day minimum storage
2272
- # duration period, you are charged for 30 days. For more information,
2273
- # see [Storage class for automatically optimizing frequently and
2274
- # infrequently accessed objects][1].
2256
+ # storage access tier, without performance impact or operational
2257
+ # overhead. S3 Intelligent-Tiering delivers automatic cost savings in
2258
+ # two low latency and high throughput access tiers. For data that can be
2259
+ # accessed asynchronously, you can choose to activate automatic
2260
+ # archiving capabilities within the S3 Intelligent-Tiering storage
2261
+ # class.
2262
+ #
2263
+ # The S3 Intelligent-Tiering storage class is the ideal storage class
2264
+ # for data with unknown, changing, or unpredictable access patterns,
2265
+ # independent of object size or retention period. If the size of an
2266
+ # object is less than 128 KB, it is not eligible for auto-tiering.
2267
+ # Smaller objects can be stored, but they are always charged at the
2268
+ # Frequent Access tier rates in the S3 Intelligent-Tiering storage
2269
+ # class.
2270
+ #
2271
+ # For more information, see [Storage class for automatically optimizing
2272
+ # frequently and infrequently accessed objects][1].
2275
2273
  #
2276
2274
  # Operations related to `DeleteBucketIntelligentTieringConfiguration`
2277
2275
  # include:
@@ -3721,21 +3719,23 @@ module Aws::S3
3721
3719
  #
3722
3720
  # The S3 Intelligent-Tiering storage class is designed to optimize
3723
3721
  # storage costs by automatically moving data to the most cost-effective
3724
- # storage access tier, without additional operational overhead. S3
3725
- # Intelligent-Tiering delivers automatic cost savings by moving data
3726
- # between access tiers, when access patterns change.
3727
- #
3728
- # The S3 Intelligent-Tiering storage class is suitable for objects
3729
- # larger than 128 KB that you plan to store for at least 30 days. If the
3730
- # size of an object is less than 128 KB, it is not eligible for
3731
- # auto-tiering. Smaller objects can be stored, but they are always
3732
- # charged at the frequent access tier rates in the S3
3733
- # Intelligent-Tiering storage class.
3734
- #
3735
- # If you delete an object before the end of the 30-day minimum storage
3736
- # duration period, you are charged for 30 days. For more information,
3737
- # see [Storage class for automatically optimizing frequently and
3738
- # infrequently accessed objects][1].
3722
+ # storage access tier, without performance impact or operational
3723
+ # overhead. S3 Intelligent-Tiering delivers automatic cost savings in
3724
+ # two low latency and high throughput access tiers. For data that can be
3725
+ # accessed asynchronously, you can choose to activate automatic
3726
+ # archiving capabilities within the S3 Intelligent-Tiering storage
3727
+ # class.
3728
+ #
3729
+ # The S3 Intelligent-Tiering storage class is the ideal storage class
3730
+ # for data with unknown, changing, or unpredictable access patterns,
3731
+ # independent of object size or retention period. If the size of an
3732
+ # object is less than 128 KB, it is not eligible for auto-tiering.
3733
+ # Smaller objects can be stored, but they are always charged at the
3734
+ # Frequent Access tier rates in the S3 Intelligent-Tiering storage
3735
+ # class.
3736
+ #
3737
+ # For more information, see [Storage class for automatically optimizing
3738
+ # frequently and infrequently accessed objects][1].
3739
3739
  #
3740
3740
  # Operations related to `GetBucketIntelligentTieringConfiguration`
3741
3741
  # include:
@@ -4302,10 +4302,12 @@ module Aws::S3
4302
4302
  # resp.metrics_configuration.filter.prefix #=> String
4303
4303
  # resp.metrics_configuration.filter.tag.key #=> String
4304
4304
  # resp.metrics_configuration.filter.tag.value #=> String
4305
+ # resp.metrics_configuration.filter.access_point_arn #=> String
4305
4306
  # resp.metrics_configuration.filter.and.prefix #=> String
4306
4307
  # resp.metrics_configuration.filter.and.tags #=> Array
4307
4308
  # resp.metrics_configuration.filter.and.tags[0].key #=> String
4308
4309
  # resp.metrics_configuration.filter.and.tags[0].value #=> String
4310
+ # resp.metrics_configuration.filter.and.access_point_arn #=> String
4309
4311
  #
4310
4312
  # @see http://docs.aws.amazon.com/goto/WebAPI/s3-2006-03-01/GetBucketMetricsConfiguration AWS API Documentation
4311
4313
  #
@@ -5163,10 +5165,9 @@ module Aws::S3
5163
5165
  #
5164
5166
  # Encryption request headers, like `x-amz-server-side-encryption`,
5165
5167
  # should not be sent for GET requests if your object uses server-side
5166
- # encryption with CMKs stored in Amazon Web Services KMS (SSE-KMS) or
5167
- # server-side encryption with Amazon S3–managed encryption keys
5168
- # (SSE-S3). If your object does use these types of keys, you’ll get an
5169
- # HTTP 400 BadRequest error.
5168
+ # encryption with KMS keys (SSE-KMS) or server-side encryption with
5169
+ # Amazon S3–managed encryption keys (SSE-S3). If your object does use
5170
+ # these types of keys, you’ll get an HTTP 400 BadRequest error.
5170
5171
  #
5171
5172
  # If you encrypt an object by using server-side encryption with
5172
5173
  # customer-provided encryption keys (SSE-C) when you store the object in
@@ -5301,6 +5302,9 @@ module Aws::S3
5301
5302
  # name. For more information about access point ARNs, see [Using access
5302
5303
  # points][1] in the *Amazon S3 User Guide*.
5303
5304
  #
5305
+ # When using an Object Lambda access point the hostname takes the form
5306
+ # *AccessPointName*-*AccountId*.s3-object-lambda.*Region*.amazonaws.com.
5307
+ #
5304
5308
  # When using this action with Amazon S3 on Outposts, you must direct
5305
5309
  # requests to the S3 on Outposts hostname. The S3 on Outposts hostname
5306
5310
  # takes the form
@@ -5444,49 +5448,49 @@ module Aws::S3
5444
5448
  # * {Types::GetObjectOutput#object_lock_legal_hold_status #object_lock_legal_hold_status} => String
5445
5449
  #
5446
5450
  #
5447
- # @example Example: To retrieve a byte range of an object
5451
+ # @example Example: To retrieve an object
5448
5452
  #
5449
- # # The following example retrieves an object for an S3 bucket. The request specifies the range header to retrieve a
5450
- # # specific byte range.
5453
+ # # The following example retrieves an object for an S3 bucket.
5451
5454
  #
5452
5455
  # resp = client.get_object({
5453
5456
  # bucket: "examplebucket",
5454
- # key: "SampleFile.txt",
5455
- # range: "bytes=0-9",
5457
+ # key: "HappyFace.jpg",
5456
5458
  # })
5457
5459
  #
5458
5460
  # resp.to_h outputs the following:
5459
5461
  # {
5460
5462
  # accept_ranges: "bytes",
5461
- # content_length: 10,
5462
- # content_range: "bytes 0-9/43",
5463
- # content_type: "text/plain",
5464
- # etag: "\"0d94420ffd0bc68cd3d152506b97a9cc\"",
5465
- # last_modified: Time.parse("Thu, 09 Oct 2014 22:57:28 GMT"),
5463
+ # content_length: 3191,
5464
+ # content_type: "image/jpeg",
5465
+ # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
5466
+ # last_modified: Time.parse("Thu, 15 Dec 2016 01:19:41 GMT"),
5466
5467
  # metadata: {
5467
5468
  # },
5469
+ # tag_count: 2,
5468
5470
  # version_id: "null",
5469
5471
  # }
5470
5472
  #
5471
- # @example Example: To retrieve an object
5473
+ # @example Example: To retrieve a byte range of an object
5472
5474
  #
5473
- # # The following example retrieves an object for an S3 bucket.
5475
+ # # The following example retrieves an object for an S3 bucket. The request specifies the range header to retrieve a
5476
+ # # specific byte range.
5474
5477
  #
5475
5478
  # resp = client.get_object({
5476
5479
  # bucket: "examplebucket",
5477
- # key: "HappyFace.jpg",
5480
+ # key: "SampleFile.txt",
5481
+ # range: "bytes=0-9",
5478
5482
  # })
5479
5483
  #
5480
5484
  # resp.to_h outputs the following:
5481
5485
  # {
5482
5486
  # accept_ranges: "bytes",
5483
- # content_length: 3191,
5484
- # content_type: "image/jpeg",
5485
- # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
5486
- # last_modified: Time.parse("Thu, 15 Dec 2016 01:19:41 GMT"),
5487
+ # content_length: 10,
5488
+ # content_range: "bytes 0-9/43",
5489
+ # content_type: "text/plain",
5490
+ # etag: "\"0d94420ffd0bc68cd3d152506b97a9cc\"",
5491
+ # last_modified: Time.parse("Thu, 09 Oct 2014 22:57:28 GMT"),
5487
5492
  # metadata: {
5488
5493
  # },
5489
- # tag_count: 2,
5490
5494
  # version_id: "null",
5491
5495
  # }
5492
5496
  #
@@ -6034,49 +6038,49 @@ module Aws::S3
6034
6038
  # * {Types::GetObjectTaggingOutput#tag_set #tag_set} => Array&lt;Types::Tag&gt;
6035
6039
  #
6036
6040
  #
6037
- # @example Example: To retrieve tag set of an object
6041
+ # @example Example: To retrieve tag set of a specific object version
6038
6042
  #
6039
- # # The following example retrieves tag set of an object.
6043
+ # # The following example retrieves tag set of an object. The request specifies object version.
6040
6044
  #
6041
6045
  # resp = client.get_object_tagging({
6042
6046
  # bucket: "examplebucket",
6043
- # key: "HappyFace.jpg",
6047
+ # key: "exampleobject",
6048
+ # version_id: "ydlaNkwWm0SfKJR.T1b1fIdPRbldTYRI",
6044
6049
  # })
6045
6050
  #
6046
6051
  # resp.to_h outputs the following:
6047
6052
  # {
6048
6053
  # tag_set: [
6049
6054
  # {
6050
- # key: "Key4",
6051
- # value: "Value4",
6052
- # },
6053
- # {
6054
- # key: "Key3",
6055
- # value: "Value3",
6055
+ # key: "Key1",
6056
+ # value: "Value1",
6056
6057
  # },
6057
6058
  # ],
6058
- # version_id: "null",
6059
+ # version_id: "ydlaNkwWm0SfKJR.T1b1fIdPRbldTYRI",
6059
6060
  # }
6060
6061
  #
6061
- # @example Example: To retrieve tag set of a specific object version
6062
+ # @example Example: To retrieve tag set of an object
6062
6063
  #
6063
- # # The following example retrieves tag set of an object. The request specifies object version.
6064
+ # # The following example retrieves tag set of an object.
6064
6065
  #
6065
6066
  # resp = client.get_object_tagging({
6066
6067
  # bucket: "examplebucket",
6067
- # key: "exampleobject",
6068
- # version_id: "ydlaNkwWm0SfKJR.T1b1fIdPRbldTYRI",
6068
+ # key: "HappyFace.jpg",
6069
6069
  # })
6070
6070
  #
6071
6071
  # resp.to_h outputs the following:
6072
6072
  # {
6073
6073
  # tag_set: [
6074
6074
  # {
6075
- # key: "Key1",
6076
- # value: "Value1",
6075
+ # key: "Key4",
6076
+ # value: "Value4",
6077
+ # },
6078
+ # {
6079
+ # key: "Key3",
6080
+ # value: "Value3",
6077
6081
  # },
6078
6082
  # ],
6079
- # version_id: "ydlaNkwWm0SfKJR.T1b1fIdPRbldTYRI",
6083
+ # version_id: "null",
6080
6084
  # }
6081
6085
  #
6082
6086
  # @example Request syntax with placeholder values
@@ -6390,10 +6394,9 @@ module Aws::S3
6390
6394
  #
6391
6395
  # <note markdown="1"> * Encryption request headers, like `x-amz-server-side-encryption`,
6392
6396
  # should not be sent for GET requests if your object uses server-side
6393
- # encryption with CMKs stored in Amazon Web Services KMS (SSE-KMS) or
6394
- # server-side encryption with Amazon S3–managed encryption keys
6395
- # (SSE-S3). If your object does use these types of keys, you’ll get an
6396
- # HTTP 400 BadRequest error.
6397
+ # encryption with KMS keys (SSE-KMS) or server-side encryption with
6398
+ # Amazon S3–managed encryption keys (SSE-S3). If your object does use
6399
+ # these types of keys, you’ll get an HTTP 400 BadRequest error.
6397
6400
  #
6398
6401
  # * The last modified property in this case is the creation date of the
6399
6402
  # object.
@@ -6779,21 +6782,23 @@ module Aws::S3
6779
6782
  #
6780
6783
  # The S3 Intelligent-Tiering storage class is designed to optimize
6781
6784
  # storage costs by automatically moving data to the most cost-effective
6782
- # storage access tier, without additional operational overhead. S3
6783
- # Intelligent-Tiering delivers automatic cost savings by moving data
6784
- # between access tiers, when access patterns change.
6785
- #
6786
- # The S3 Intelligent-Tiering storage class is suitable for objects
6787
- # larger than 128 KB that you plan to store for at least 30 days. If the
6788
- # size of an object is less than 128 KB, it is not eligible for
6789
- # auto-tiering. Smaller objects can be stored, but they are always
6790
- # charged at the frequent access tier rates in the S3
6791
- # Intelligent-Tiering storage class.
6792
- #
6793
- # If you delete an object before the end of the 30-day minimum storage
6794
- # duration period, you are charged for 30 days. For more information,
6795
- # see [Storage class for automatically optimizing frequently and
6796
- # infrequently accessed objects][1].
6785
+ # storage access tier, without performance impact or operational
6786
+ # overhead. S3 Intelligent-Tiering delivers automatic cost savings in
6787
+ # two low latency and high throughput access tiers. For data that can be
6788
+ # accessed asynchronously, you can choose to activate automatic
6789
+ # archiving capabilities within the S3 Intelligent-Tiering storage
6790
+ # class.
6791
+ #
6792
+ # The S3 Intelligent-Tiering storage class is the ideal storage class
6793
+ # for data with unknown, changing, or unpredictable access patterns,
6794
+ # independent of object size or retention period. If the size of an
6795
+ # object is less than 128 KB, it is not eligible for auto-tiering.
6796
+ # Smaller objects can be stored, but they are always charged at the
6797
+ # Frequent Access tier rates in the S3 Intelligent-Tiering storage
6798
+ # class.
6799
+ #
6800
+ # For more information, see [Storage class for automatically optimizing
6801
+ # frequently and infrequently accessed objects][1].
6797
6802
  #
6798
6803
  # Operations related to `ListBucketIntelligentTieringConfigurations`
6799
6804
  # include:
@@ -7041,10 +7046,12 @@ module Aws::S3
7041
7046
  # resp.metrics_configuration_list[0].filter.prefix #=> String
7042
7047
  # resp.metrics_configuration_list[0].filter.tag.key #=> String
7043
7048
  # resp.metrics_configuration_list[0].filter.tag.value #=> String
7049
+ # resp.metrics_configuration_list[0].filter.access_point_arn #=> String
7044
7050
  # resp.metrics_configuration_list[0].filter.and.prefix #=> String
7045
7051
  # resp.metrics_configuration_list[0].filter.and.tags #=> Array
7046
7052
  # resp.metrics_configuration_list[0].filter.and.tags[0].key #=> String
7047
7053
  # resp.metrics_configuration_list[0].filter.and.tags[0].value #=> String
7054
+ # resp.metrics_configuration_list[0].filter.and.access_point_arn #=> String
7048
7055
  #
7049
7056
  # @see http://docs.aws.amazon.com/goto/WebAPI/s3-2006-03-01/ListBucketMetricsConfigurations AWS API Documentation
7050
7057
  #
@@ -7258,97 +7265,97 @@ module Aws::S3
7258
7265
  # The returned {Seahorse::Client::Response response} is a pageable response and is Enumerable. For details on usage see {Aws::PageableResponse PageableResponse}.
7259
7266
  #
7260
7267
  #
7261
- # @example Example: List next set of multipart uploads when previous result is truncated
7268
+ # @example Example: To list in-progress multipart uploads on a bucket
7262
7269
  #
7263
- # # The following example specifies the upload-id-marker and key-marker from previous truncated response to retrieve next
7264
- # # setup of multipart uploads.
7270
+ # # The following example lists in-progress multipart uploads on a specific bucket.
7265
7271
  #
7266
7272
  # resp = client.list_multipart_uploads({
7267
7273
  # bucket: "examplebucket",
7268
- # key_marker: "nextkeyfrompreviousresponse",
7269
- # max_uploads: 2,
7270
- # upload_id_marker: "valuefrompreviousresponse",
7271
7274
  # })
7272
7275
  #
7273
7276
  # resp.to_h outputs the following:
7274
7277
  # {
7275
- # bucket: "acl1",
7276
- # is_truncated: true,
7277
- # key_marker: "",
7278
- # max_uploads: 2,
7279
- # next_key_marker: "someobjectkey",
7280
- # next_upload_id_marker: "examplelo91lv1iwvWpvCiJWugw2xXLPAD7Z8cJyX9.WiIRgNrdG6Ldsn.9FtS63TCl1Uf5faTB.1U5Ckcbmdw--",
7281
- # upload_id_marker: "",
7282
7278
  # uploads: [
7283
7279
  # {
7284
7280
  # initiated: Time.parse("2014-05-01T05:40:58.000Z"),
7285
7281
  # initiator: {
7286
- # display_name: "ownder-display-name",
7282
+ # display_name: "display-name",
7287
7283
  # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7288
7284
  # },
7289
7285
  # key: "JavaFile",
7290
7286
  # owner: {
7291
- # display_name: "mohanataws",
7292
- # id: "852b113e7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7287
+ # display_name: "display-name",
7288
+ # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7293
7289
  # },
7294
7290
  # storage_class: "STANDARD",
7295
- # upload_id: "gZ30jIqlUa.CInXklLQtSMJITdUnoZ1Y5GACB5UckOtspm5zbDMCkPF_qkfZzMiFZ6dksmcnqxJyIBvQMG9X9Q--",
7291
+ # upload_id: "examplelUa.CInXklLQtSMJITdUnoZ1Y5GACB5UckOtspm5zbDMCkPF_qkfZzMiFZ6dksmcnqxJyIBvQMG9X9Q--",
7296
7292
  # },
7297
7293
  # {
7298
7294
  # initiated: Time.parse("2014-05-01T05:41:27.000Z"),
7299
7295
  # initiator: {
7300
- # display_name: "ownder-display-name",
7296
+ # display_name: "display-name",
7301
7297
  # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7302
7298
  # },
7303
7299
  # key: "JavaFile",
7304
7300
  # owner: {
7305
- # display_name: "ownder-display-name",
7301
+ # display_name: "display-name",
7306
7302
  # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7307
7303
  # },
7308
7304
  # storage_class: "STANDARD",
7309
- # upload_id: "b7tZSqIlo91lv1iwvWpvCiJWugw2xXLPAD7Z8cJyX9.WiIRgNrdG6Ldsn.9FtS63TCl1Uf5faTB.1U5Ckcbmdw--",
7305
+ # upload_id: "examplelo91lv1iwvWpvCiJWugw2xXLPAD7Z8cJyX9.WiIRgNrdG6Ldsn.9FtS63TCl1Uf5faTB.1U5Ckcbmdw--",
7310
7306
  # },
7311
7307
  # ],
7312
7308
  # }
7313
7309
  #
7314
- # @example Example: To list in-progress multipart uploads on a bucket
7310
+ # @example Example: List next set of multipart uploads when previous result is truncated
7315
7311
  #
7316
- # # The following example lists in-progress multipart uploads on a specific bucket.
7312
+ # # The following example specifies the upload-id-marker and key-marker from previous truncated response to retrieve next
7313
+ # # setup of multipart uploads.
7317
7314
  #
7318
7315
  # resp = client.list_multipart_uploads({
7319
7316
  # bucket: "examplebucket",
7317
+ # key_marker: "nextkeyfrompreviousresponse",
7318
+ # max_uploads: 2,
7319
+ # upload_id_marker: "valuefrompreviousresponse",
7320
7320
  # })
7321
7321
  #
7322
7322
  # resp.to_h outputs the following:
7323
7323
  # {
7324
+ # bucket: "acl1",
7325
+ # is_truncated: true,
7326
+ # key_marker: "",
7327
+ # max_uploads: 2,
7328
+ # next_key_marker: "someobjectkey",
7329
+ # next_upload_id_marker: "examplelo91lv1iwvWpvCiJWugw2xXLPAD7Z8cJyX9.WiIRgNrdG6Ldsn.9FtS63TCl1Uf5faTB.1U5Ckcbmdw--",
7330
+ # upload_id_marker: "",
7324
7331
  # uploads: [
7325
7332
  # {
7326
7333
  # initiated: Time.parse("2014-05-01T05:40:58.000Z"),
7327
7334
  # initiator: {
7328
- # display_name: "display-name",
7335
+ # display_name: "ownder-display-name",
7329
7336
  # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7330
7337
  # },
7331
7338
  # key: "JavaFile",
7332
7339
  # owner: {
7333
- # display_name: "display-name",
7334
- # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7340
+ # display_name: "mohanataws",
7341
+ # id: "852b113e7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7335
7342
  # },
7336
7343
  # storage_class: "STANDARD",
7337
- # upload_id: "examplelUa.CInXklLQtSMJITdUnoZ1Y5GACB5UckOtspm5zbDMCkPF_qkfZzMiFZ6dksmcnqxJyIBvQMG9X9Q--",
7344
+ # upload_id: "gZ30jIqlUa.CInXklLQtSMJITdUnoZ1Y5GACB5UckOtspm5zbDMCkPF_qkfZzMiFZ6dksmcnqxJyIBvQMG9X9Q--",
7338
7345
  # },
7339
7346
  # {
7340
7347
  # initiated: Time.parse("2014-05-01T05:41:27.000Z"),
7341
7348
  # initiator: {
7342
- # display_name: "display-name",
7349
+ # display_name: "ownder-display-name",
7343
7350
  # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7344
7351
  # },
7345
7352
  # key: "JavaFile",
7346
7353
  # owner: {
7347
- # display_name: "display-name",
7354
+ # display_name: "ownder-display-name",
7348
7355
  # id: "examplee7a2f25102679df27bb0ae12b3f85be6f290b936c4393484be31bebcc",
7349
7356
  # },
7350
7357
  # storage_class: "STANDARD",
7351
- # upload_id: "examplelo91lv1iwvWpvCiJWugw2xXLPAD7Z8cJyX9.WiIRgNrdG6Ldsn.9FtS63TCl1Uf5faTB.1U5Ckcbmdw--",
7358
+ # upload_id: "b7tZSqIlo91lv1iwvWpvCiJWugw2xXLPAD7Z8cJyX9.WiIRgNrdG6Ldsn.9FtS63TCl1Uf5faTB.1U5Ckcbmdw--",
7352
7359
  # },
7353
7360
  # ],
7354
7361
  # }
@@ -8822,12 +8829,12 @@ module Aws::S3
8822
8829
  # encryption and Amazon S3 Bucket Key for an existing bucket.
8823
8830
  #
8824
8831
  # Default encryption for a bucket can use server-side encryption with
8825
- # Amazon S3-managed keys (SSE-S3) or Amazon Web Services KMS customer
8826
- # master keys (SSE-KMS). If you specify default encryption using
8827
- # SSE-KMS, you can also configure Amazon S3 Bucket Key. For information
8828
- # about default encryption, see [Amazon S3 default bucket encryption][1]
8829
- # in the *Amazon S3 User Guide*. For more information about S3 Bucket
8830
- # Keys, see [Amazon S3 Bucket Keys][2] in the *Amazon S3 User Guide*.
8832
+ # Amazon S3-managed keys (SSE-S3) or customer managed keys (SSE-KMS). If
8833
+ # you specify default encryption using SSE-KMS, you can also configure
8834
+ # Amazon S3 Bucket Key. For information about default encryption, see
8835
+ # [Amazon S3 default bucket encryption][1] in the *Amazon S3 User
8836
+ # Guide*. For more information about S3 Bucket Keys, see [Amazon S3
8837
+ # Bucket Keys][2] in the *Amazon S3 User Guide*.
8831
8838
  #
8832
8839
  # This action requires Amazon Web Services Signature Version 4. For more
8833
8840
  # information, see [ Authenticating Requests (Amazon Web Services
@@ -8859,10 +8866,10 @@ module Aws::S3
8859
8866
  #
8860
8867
  # @option params [required, String] :bucket
8861
8868
  # Specifies default encryption for a bucket using server-side encryption
8862
- # with Amazon S3-managed keys (SSE-S3) or customer master keys stored in
8863
- # Amazon Web Services KMS (SSE-KMS). For information about the Amazon S3
8864
- # default encryption feature, see [Amazon S3 Default Bucket
8865
- # Encryption][1] in the *Amazon S3 User Guide*.
8869
+ # with Amazon S3-managed keys (SSE-S3) or customer managed keys
8870
+ # (SSE-KMS). For information about the Amazon S3 default encryption
8871
+ # feature, see [Amazon S3 Default Bucket Encryption][1] in the *Amazon
8872
+ # S3 User Guide*.
8866
8873
  #
8867
8874
  #
8868
8875
  #
@@ -8920,21 +8927,23 @@ module Aws::S3
8920
8927
  #
8921
8928
  # The S3 Intelligent-Tiering storage class is designed to optimize
8922
8929
  # storage costs by automatically moving data to the most cost-effective
8923
- # storage access tier, without additional operational overhead. S3
8924
- # Intelligent-Tiering delivers automatic cost savings by moving data
8925
- # between access tiers, when access patterns change.
8926
- #
8927
- # The S3 Intelligent-Tiering storage class is suitable for objects
8928
- # larger than 128 KB that you plan to store for at least 30 days. If the
8929
- # size of an object is less than 128 KB, it is not eligible for
8930
- # auto-tiering. Smaller objects can be stored, but they are always
8931
- # charged at the frequent access tier rates in the S3
8932
- # Intelligent-Tiering storage class.
8933
- #
8934
- # If you delete an object before the end of the 30-day minimum storage
8935
- # duration period, you are charged for 30 days. For more information,
8936
- # see [Storage class for automatically optimizing frequently and
8937
- # infrequently accessed objects][1].
8930
+ # storage access tier, without performance impact or operational
8931
+ # overhead. S3 Intelligent-Tiering delivers automatic cost savings in
8932
+ # two low latency and high throughput access tiers. For data that can be
8933
+ # accessed asynchronously, you can choose to activate automatic
8934
+ # archiving capabilities within the S3 Intelligent-Tiering storage
8935
+ # class.
8936
+ #
8937
+ # The S3 Intelligent-Tiering storage class is the ideal storage class
8938
+ # for data with unknown, changing, or unpredictable access patterns,
8939
+ # independent of object size or retention period. If the size of an
8940
+ # object is less than 128 KB, it is not eligible for auto-tiering.
8941
+ # Smaller objects can be stored, but they are always charged at the
8942
+ # Frequent Access tier rates in the S3 Intelligent-Tiering storage
8943
+ # class.
8944
+ #
8945
+ # For more information, see [Storage class for automatically optimizing
8946
+ # frequently and infrequently accessed objects][1].
8938
8947
  #
8939
8948
  # Operations related to `PutBucketIntelligentTieringConfiguration`
8940
8949
  # include:
@@ -9652,7 +9661,7 @@ module Aws::S3
9652
9661
  #
9653
9662
  # * [DeleteBucketMetricsConfiguration][4]
9654
9663
  #
9655
- # * [PutBucketMetricsConfiguration][5]
9664
+ # * [GetBucketMetricsConfiguration][5]
9656
9665
  #
9657
9666
  # * [ListBucketMetricsConfigurations][6]
9658
9667
  #
@@ -9671,7 +9680,7 @@ module Aws::S3
9671
9680
  # [2]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html
9672
9681
  # [3]: https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html
9673
9682
  # [4]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html
9674
- # [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html
9683
+ # [5]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html
9675
9684
  # [6]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html
9676
9685
  #
9677
9686
  # @option params [required, String] :bucket
@@ -9703,6 +9712,7 @@ module Aws::S3
9703
9712
  # key: "ObjectKey", # required
9704
9713
  # value: "Value", # required
9705
9714
  # },
9715
+ # access_point_arn: "AccessPointArn",
9706
9716
  # and: {
9707
9717
  # prefix: "Prefix",
9708
9718
  # tags: [
@@ -9711,6 +9721,7 @@ module Aws::S3
9711
9721
  # value: "Value", # required
9712
9722
  # },
9713
9723
  # ],
9724
+ # access_point_arn: "AccessPointArn",
9714
9725
  # },
9715
9726
  # },
9716
9727
  # },
@@ -10143,13 +10154,12 @@ module Aws::S3
10143
10154
  # **Handling Replication of Encrypted Objects**
10144
10155
  #
10145
10156
  # By default, Amazon S3 doesn't replicate objects that are stored at
10146
- # rest using server-side encryption with CMKs stored in Amazon Web
10147
- # Services KMS. To replicate Amazon Web Services KMS-encrypted objects,
10148
- # add the following: `SourceSelectionCriteria`,
10149
- # `SseKmsEncryptedObjects`, `Status`, `EncryptionConfiguration`, and
10150
- # `ReplicaKmsKeyID`. For information about replication configuration,
10151
- # see [Replicating Objects Created with SSE Using CMKs stored in Amazon
10152
- # Web Services KMS][4].
10157
+ # rest using server-side encryption with KMS keys. To replicate Amazon
10158
+ # Web Services KMS-encrypted objects, add the following:
10159
+ # `SourceSelectionCriteria`, `SseKmsEncryptedObjects`, `Status`,
10160
+ # `EncryptionConfiguration`, and `ReplicaKmsKeyID`. For information
10161
+ # about replication configuration, see [Replicating Objects Created with
10162
+ # SSE Using KMS keys][4].
10153
10163
  #
10154
10164
  # For information on `PutBucketReplication` errors, see [List of
10155
10165
  # replication-related error codes][5]
@@ -11112,12 +11122,12 @@ module Aws::S3
11112
11122
  # If `x-amz-server-side-encryption` is present and has the value of
11113
11123
  # `aws:kms`, this header specifies the ID of the Amazon Web Services Key
11114
11124
  # Management Service (Amazon Web Services KMS) symmetrical customer
11115
- # managed customer master key (CMK) that was used for the object. If you
11116
- # specify `x-amz-server-side-encryption:aws:kms`, but do not provide`
11125
+ # managed key that was used for the object. If you specify
11126
+ # `x-amz-server-side-encryption:aws:kms`, but do not provide`
11117
11127
  # x-amz-server-side-encryption-aws-kms-key-id`, Amazon S3 uses the
11118
- # Amazon Web Services managed CMK in Amazon Web Services to protect the
11119
- # data. If the KMS key does not exist in the same account issuing the
11120
- # command, you must use the full ARN and not just the ID.
11128
+ # Amazon Web Services managed key to protect the data. If the KMS key
11129
+ # does not exist in the same account issuing the command, you must use
11130
+ # the full ARN and not just the ID.
11121
11131
  #
11122
11132
  # @option params [String] :ssekms_encryption_context
11123
11133
  # Specifies the Amazon Web Services KMS Encryption Context to use for
@@ -11182,134 +11192,134 @@ module Aws::S3
11182
11192
  # * {Types::PutObjectOutput#request_charged #request_charged} => String
11183
11193
  #
11184
11194
  #
11185
- # @example Example: To upload an object (specify optional headers)
11195
+ # @example Example: To upload an object and specify optional tags
11186
11196
  #
11187
- # # The following example uploads an object. The request specifies optional request headers to directs S3 to use specific
11188
- # # storage class and use server-side encryption.
11197
+ # # The following example uploads an object. The request specifies optional object tags. The bucket is versioned, therefore
11198
+ # # S3 returns version ID of the newly created object.
11189
11199
  #
11190
11200
  # resp = client.put_object({
11191
- # body: "HappyFace.jpg",
11201
+ # body: "c:\\HappyFace.jpg",
11192
11202
  # bucket: "examplebucket",
11193
11203
  # key: "HappyFace.jpg",
11194
- # server_side_encryption: "AES256",
11195
- # storage_class: "STANDARD_IA",
11204
+ # tagging: "key1=value1&key2=value2",
11196
11205
  # })
11197
11206
  #
11198
11207
  # resp.to_h outputs the following:
11199
11208
  # {
11200
11209
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11201
- # server_side_encryption: "AES256",
11202
- # version_id: "CG612hodqujkf8FaaNfp8U..FIhLROcp",
11210
+ # version_id: "psM2sYY4.o1501dSx8wMvnkOzSBB.V4a",
11203
11211
  # }
11204
11212
  #
11205
- # @example Example: To upload an object and specify server-side encryption and object tags
11213
+ # @example Example: To upload an object and specify canned ACL.
11206
11214
  #
11207
- # # The following example uploads and object. The request specifies the optional server-side encryption option. The request
11208
- # # also specifies optional object tags. If the bucket is versioning enabled, S3 returns version ID in response.
11215
+ # # The following example uploads and object. The request specifies optional canned ACL (access control list) to all READ
11216
+ # # access to authenticated users. If the bucket is versioning enabled, S3 returns version ID in response.
11209
11217
  #
11210
11218
  # resp = client.put_object({
11219
+ # acl: "authenticated-read",
11211
11220
  # body: "filetoupload",
11212
11221
  # bucket: "examplebucket",
11213
11222
  # key: "exampleobject",
11214
- # server_side_encryption: "AES256",
11215
- # tagging: "key1=value1&key2=value2",
11216
11223
  # })
11217
11224
  #
11218
11225
  # resp.to_h outputs the following:
11219
11226
  # {
11220
11227
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11221
- # server_side_encryption: "AES256",
11222
- # version_id: "Ri.vC6qVlA4dEnjgRV4ZHsHoFIjqEMNt",
11228
+ # version_id: "Kirh.unyZwjQ69YxcQLA8z4F5j3kJJKr",
11223
11229
  # }
11224
11230
  #
11225
- # @example Example: To create an object.
11231
+ # @example Example: To upload an object and specify server-side encryption and object tags
11226
11232
  #
11227
- # # The following example creates an object. If the bucket is versioning enabled, S3 returns version ID in response.
11233
+ # # The following example uploads and object. The request specifies the optional server-side encryption option. The request
11234
+ # # also specifies optional object tags. If the bucket is versioning enabled, S3 returns version ID in response.
11228
11235
  #
11229
11236
  # resp = client.put_object({
11230
11237
  # body: "filetoupload",
11231
11238
  # bucket: "examplebucket",
11232
- # key: "objectkey",
11239
+ # key: "exampleobject",
11240
+ # server_side_encryption: "AES256",
11241
+ # tagging: "key1=value1&key2=value2",
11233
11242
  # })
11234
11243
  #
11235
11244
  # resp.to_h outputs the following:
11236
11245
  # {
11237
11246
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11238
- # version_id: "Bvq0EDKxOcXLJXNo_Lkz37eM3R4pfzyQ",
11247
+ # server_side_encryption: "AES256",
11248
+ # version_id: "Ri.vC6qVlA4dEnjgRV4ZHsHoFIjqEMNt",
11239
11249
  # }
11240
11250
  #
11241
- # @example Example: To upload object and specify user-defined metadata
11251
+ # @example Example: To create an object.
11242
11252
  #
11243
- # # The following example creates an object. The request also specifies optional metadata. If the bucket is versioning
11244
- # # enabled, S3 returns version ID in response.
11253
+ # # The following example creates an object. If the bucket is versioning enabled, S3 returns version ID in response.
11245
11254
  #
11246
11255
  # resp = client.put_object({
11247
11256
  # body: "filetoupload",
11248
11257
  # bucket: "examplebucket",
11249
- # key: "exampleobject",
11250
- # metadata: {
11251
- # "metadata1" => "value1",
11252
- # "metadata2" => "value2",
11253
- # },
11258
+ # key: "objectkey",
11254
11259
  # })
11255
11260
  #
11256
11261
  # resp.to_h outputs the following:
11257
11262
  # {
11258
11263
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11259
- # version_id: "pSKidl4pHBiNwukdbcPXAIs.sshFFOc0",
11264
+ # version_id: "Bvq0EDKxOcXLJXNo_Lkz37eM3R4pfzyQ",
11260
11265
  # }
11261
11266
  #
11262
- # @example Example: To upload an object and specify canned ACL.
11267
+ # @example Example: To upload an object
11263
11268
  #
11264
- # # The following example uploads and object. The request specifies optional canned ACL (access control list) to all READ
11265
- # # access to authenticated users. If the bucket is versioning enabled, S3 returns version ID in response.
11269
+ # # The following example uploads an object to a versioning-enabled bucket. The source file is specified using Windows file
11270
+ # # syntax. S3 returns VersionId of the newly created object.
11266
11271
  #
11267
11272
  # resp = client.put_object({
11268
- # acl: "authenticated-read",
11269
- # body: "filetoupload",
11273
+ # body: "HappyFace.jpg",
11270
11274
  # bucket: "examplebucket",
11271
- # key: "exampleobject",
11275
+ # key: "HappyFace.jpg",
11272
11276
  # })
11273
11277
  #
11274
11278
  # resp.to_h outputs the following:
11275
11279
  # {
11276
11280
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11277
- # version_id: "Kirh.unyZwjQ69YxcQLA8z4F5j3kJJKr",
11281
+ # version_id: "tpf3zF08nBplQK1XLOefGskR7mGDwcDk",
11278
11282
  # }
11279
11283
  #
11280
- # @example Example: To upload an object
11284
+ # @example Example: To upload an object (specify optional headers)
11281
11285
  #
11282
- # # The following example uploads an object to a versioning-enabled bucket. The source file is specified using Windows file
11283
- # # syntax. S3 returns VersionId of the newly created object.
11286
+ # # The following example uploads an object. The request specifies optional request headers to directs S3 to use specific
11287
+ # # storage class and use server-side encryption.
11284
11288
  #
11285
11289
  # resp = client.put_object({
11286
11290
  # body: "HappyFace.jpg",
11287
11291
  # bucket: "examplebucket",
11288
11292
  # key: "HappyFace.jpg",
11293
+ # server_side_encryption: "AES256",
11294
+ # storage_class: "STANDARD_IA",
11289
11295
  # })
11290
11296
  #
11291
11297
  # resp.to_h outputs the following:
11292
11298
  # {
11293
11299
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11294
- # version_id: "tpf3zF08nBplQK1XLOefGskR7mGDwcDk",
11300
+ # server_side_encryption: "AES256",
11301
+ # version_id: "CG612hodqujkf8FaaNfp8U..FIhLROcp",
11295
11302
  # }
11296
11303
  #
11297
- # @example Example: To upload an object and specify optional tags
11304
+ # @example Example: To upload object and specify user-defined metadata
11298
11305
  #
11299
- # # The following example uploads an object. The request specifies optional object tags. The bucket is versioned, therefore
11300
- # # S3 returns version ID of the newly created object.
11306
+ # # The following example creates an object. The request also specifies optional metadata. If the bucket is versioning
11307
+ # # enabled, S3 returns version ID in response.
11301
11308
  #
11302
11309
  # resp = client.put_object({
11303
- # body: "c:\\HappyFace.jpg",
11310
+ # body: "filetoupload",
11304
11311
  # bucket: "examplebucket",
11305
- # key: "HappyFace.jpg",
11306
- # tagging: "key1=value1&key2=value2",
11312
+ # key: "exampleobject",
11313
+ # metadata: {
11314
+ # "metadata1" => "value1",
11315
+ # "metadata2" => "value2",
11316
+ # },
11307
11317
  # })
11308
11318
  #
11309
11319
  # resp.to_h outputs the following:
11310
11320
  # {
11311
11321
  # etag: "\"6805f2cfc46c0f04559748bb039d69ae\"",
11312
- # version_id: "psM2sYY4.o1501dSx8wMvnkOzSBB.V4a",
11322
+ # version_id: "pSKidl4pHBiNwukdbcPXAIs.sshFFOc0",
11313
11323
  # }
11314
11324
  #
11315
11325
  # @example Streaming a file from disk
@@ -12742,12 +12752,11 @@ module Aws::S3
12742
12752
  # Encryption Keys)][5] in the *Amazon S3 User Guide*.
12743
12753
  #
12744
12754
  # For objects that are encrypted with Amazon S3 managed encryption
12745
- # keys (SSE-S3) and customer master keys (CMKs) stored in Amazon Web
12746
- # Services Key Management Service (SSE-KMS), server-side encryption is
12747
- # handled transparently, so you don't need to specify anything. For
12748
- # more information about server-side encryption, including SSE-S3 and
12749
- # SSE-KMS, see [Protecting Data Using Server-Side Encryption][6] in
12750
- # the *Amazon S3 User Guide*.
12755
+ # keys (SSE-S3) and Amazon Web Services KMS keys (SSE-KMS),
12756
+ # server-side encryption is handled transparently, so you don't need
12757
+ # to specify anything. For more information about server-side
12758
+ # encryption, including SSE-S3 and SSE-KMS, see [Protecting Data Using
12759
+ # Server-Side Encryption][6] in the *Amazon S3 User Guide*.
12751
12760
  #
12752
12761
  # **Working with the Response Body**
12753
12762
  #
@@ -13654,45 +13663,45 @@ module Aws::S3
13654
13663
  # * {Types::UploadPartCopyOutput#request_charged #request_charged} => String
13655
13664
  #
13656
13665
  #
13657
- # @example Example: To upload a part by copying byte range from an existing object as data source
13666
+ # @example Example: To upload a part by copying data from an existing object as data source
13658
13667
  #
13659
- # # The following example uploads a part of a multipart upload by copying a specified byte range from an existing object as
13660
- # # data source.
13668
+ # # The following example uploads a part of a multipart upload by copying data from an existing object as data source.
13661
13669
  #
13662
13670
  # resp = client.upload_part_copy({
13663
13671
  # bucket: "examplebucket",
13664
13672
  # copy_source: "/bucketname/sourceobjectkey",
13665
- # copy_source_range: "bytes=1-100000",
13666
13673
  # key: "examplelargeobject",
13667
- # part_number: 2,
13674
+ # part_number: 1,
13668
13675
  # upload_id: "exampleuoh_10OhKhT7YukE9bjzTPRiuaCotmZM_pFngJFir9OZNrSr5cWa3cq3LZSUsfjI4FI7PkP91We7Nrw--",
13669
13676
  # })
13670
13677
  #
13671
13678
  # resp.to_h outputs the following:
13672
13679
  # {
13673
13680
  # copy_part_result: {
13674
- # etag: "\"65d16d19e65a7508a51f043180edcc36\"",
13675
- # last_modified: Time.parse("2016-12-29T21:44:28.000Z"),
13681
+ # etag: "\"b0c6f0e7e054ab8fa2536a2677f8734d\"",
13682
+ # last_modified: Time.parse("2016-12-29T21:24:43.000Z"),
13676
13683
  # },
13677
13684
  # }
13678
13685
  #
13679
- # @example Example: To upload a part by copying data from an existing object as data source
13686
+ # @example Example: To upload a part by copying byte range from an existing object as data source
13680
13687
  #
13681
- # # The following example uploads a part of a multipart upload by copying data from an existing object as data source.
13688
+ # # The following example uploads a part of a multipart upload by copying a specified byte range from an existing object as
13689
+ # # data source.
13682
13690
  #
13683
13691
  # resp = client.upload_part_copy({
13684
13692
  # bucket: "examplebucket",
13685
13693
  # copy_source: "/bucketname/sourceobjectkey",
13694
+ # copy_source_range: "bytes=1-100000",
13686
13695
  # key: "examplelargeobject",
13687
- # part_number: 1,
13696
+ # part_number: 2,
13688
13697
  # upload_id: "exampleuoh_10OhKhT7YukE9bjzTPRiuaCotmZM_pFngJFir9OZNrSr5cWa3cq3LZSUsfjI4FI7PkP91We7Nrw--",
13689
13698
  # })
13690
13699
  #
13691
13700
  # resp.to_h outputs the following:
13692
13701
  # {
13693
13702
  # copy_part_result: {
13694
- # etag: "\"b0c6f0e7e054ab8fa2536a2677f8734d\"",
13695
- # last_modified: Time.parse("2016-12-29T21:24:43.000Z"),
13703
+ # etag: "\"65d16d19e65a7508a51f043180edcc36\"",
13704
+ # last_modified: Time.parse("2016-12-29T21:44:28.000Z"),
13696
13705
  # },
13697
13706
  # }
13698
13707
  #
@@ -13742,9 +13751,9 @@ module Aws::S3
13742
13751
  end
13743
13752
 
13744
13753
  # Passes transformed objects to a `GetObject` operation when using
13745
- # Object Lambda Access Points. For information about Object Lambda
13746
- # Access Points, see [Transforming objects with Object Lambda Access
13747
- # Points][1] in the *Amazon S3 User Guide*.
13754
+ # Object Lambda access points. For information about Object Lambda
13755
+ # access points, see [Transforming objects with Object Lambda access
13756
+ # points][1] in the *Amazon S3 User Guide*.
13748
13757
  #
13749
13758
  # This operation supports metadata that can be returned by
13750
13759
  # [GetObject][2], in addition to `RequestRoute`, `RequestToken`,
@@ -13766,8 +13775,8 @@ module Aws::S3
13766
13775
  # identifiable information (PII) and decompress S3 objects. These Lambda
13767
13776
  # functions are available in the Amazon Web Services Serverless
13768
13777
  # Application Repository, and can be selected through the Amazon Web
13769
- # Services Management Console when you create your Object Lambda Access
13770
- # Point.
13778
+ # Services Management Console when you create your Object Lambda access
13779
+ # point.
13771
13780
  #
13772
13781
  # Example 1: PII Access Control - This Lambda function uses Amazon
13773
13782
  # Comprehend, a natural language processing (NLP) service using machine
@@ -13959,8 +13968,8 @@ module Aws::S3
13959
13968
  #
13960
13969
  # @option params [String] :ssekms_key_id
13961
13970
  # If present, specifies the ID of the Amazon Web Services Key Management
13962
- # Service (Amazon Web Services KMS) symmetric customer managed customer
13963
- # master key (CMK) that was used for stored in Amazon S3 object.
13971
+ # Service (Amazon Web Services KMS) symmetric customer managed key that
13972
+ # was used for stored in Amazon S3 object.
13964
13973
  #
13965
13974
  # @option params [String] :sse_customer_key_md5
13966
13975
  # 128-bit MD5 digest of customer-provided encryption key used in Amazon
@@ -14052,7 +14061,7 @@ module Aws::S3
14052
14061
  params: params,
14053
14062
  config: config)
14054
14063
  context[:gem_name] = 'aws-sdk-s3'
14055
- context[:gem_version] = '1.102.0'
14064
+ context[:gem_version] = '1.103.0'
14056
14065
  Seahorse::Client::Request.new(handlers, context)
14057
14066
  end
14058
14067