aws-sdk-iam 1.69.0 → 1.70.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: c5dbcb4800f65764e4a3e2f28b774766916a84654d446ff44ecfaab60455a8fd
4
- data.tar.gz: ea560b72220beed42179d02fed3ad1363d1494230583feb82dcd96feaf16d40e
3
+ metadata.gz: b20044b37e7389a1adce089513f2b2f2204d7097f729fa3dff342ec410bbfa09
4
+ data.tar.gz: 71be63000c36119494889895ff12ae0bde2c9a1a06b90b6a8a888c13bcfe361f
5
5
  SHA512:
6
- metadata.gz: 987a30d8cce522de9f26923e76ac05a5ee2803538353d5ffb2e211022257792702eef1938e91ae90abdca4b1011b096972e432a6473dc22b011333f5737d10af
7
- data.tar.gz: 877f9d957f7a694a1045f439edf5316b98b0be38eadef0e2025459012c3a7fbd76e163e6a50dba13d9b4beacb03ee971c94e63b7a5222fcbb7e04c4903d187f4
6
+ metadata.gz: 86529b3bac5fa9307d31e66af7bc568613e33a823ab41913f72ecea754256aa00e65a45a6d4c2dc6541819e7bf740a602edc1e2fcfd3af509f85c5f6b3514179
7
+ data.tar.gz: db1814b2451c0a3b2037ba902f251b2a289650b895e3732684c2a05aef23391a46ac5064b5d4eceeb213e174fa9d5709918557eec1ffe0b15e5cb7ff9497627c
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.70.0 (2022-08-24)
5
+ ------------------
6
+
7
+ * Feature - Documentation updates for AWS Identity and Access Management (IAM).
8
+
4
9
  1.69.0 (2022-06-08)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.69.0
1
+ 1.70.0
@@ -6173,12 +6173,14 @@ module Aws::IAM
6173
6173
  # Although each user is limited to a small number of keys, you can still
6174
6174
  # paginate the results using the `MaxItems` and `Marker` parameters.
6175
6175
  #
6176
- # If the `UserName` field is not specified, the user name is determined
6176
+ # If the `UserName` is not specified, the user name is determined
6177
6177
  # implicitly based on the Amazon Web Services access key ID used to sign
6178
- # the request. This operation works for access keys under the Amazon Web
6179
- # Services account. Consequently, you can use this operation to manage
6180
- # Amazon Web Services account root user credentials even if the Amazon
6181
- # Web Services account has no associated users.
6178
+ # the request. If a temporary access key is used, then `UserName` is
6179
+ # required. If a long-term key is assigned to the user, then `UserName`
6180
+ # is not required. This operation works for access keys under the Amazon
6181
+ # Web Services account. Consequently, you can use this operation to
6182
+ # manage Amazon Web Services account root user credentials even if the
6183
+ # Amazon Web Services account has no associated users.
6182
6184
  #
6183
6185
  # <note markdown="1"> To ensure the security of your Amazon Web Services account, the secret
6184
6186
  # access key is accessible only during key and user creation.
@@ -10226,36 +10228,28 @@ module Aws::IAM
10226
10228
  # resources that you must define to run the simulation.
10227
10229
  #
10228
10230
  # Each of the EC2 scenarios requires that you specify instance, image,
10229
- # and security-group resources. If your scenario includes an EBS volume,
10231
+ # and security group resources. If your scenario includes an EBS volume,
10230
10232
  # then you must specify that volume as a resource. If the EC2 scenario
10231
- # includes VPC, then you must supply the network-interface resource. If
10233
+ # includes VPC, then you must supply the network interface resource. If
10232
10234
  # it includes an IP subnet, then you must specify the subnet resource.
10233
10235
  # For more information on the EC2 scenario options, see [Supported
10234
10236
  # platforms][1] in the *Amazon EC2 User Guide*.
10235
10237
  #
10236
- # * **EC2-Classic-InstanceStore**
10237
- #
10238
- # instance, image, security-group
10239
- #
10240
- # * **EC2-Classic-EBS**
10241
- #
10242
- # instance, image, security-group, volume
10243
- #
10244
10238
  # * **EC2-VPC-InstanceStore**
10245
10239
  #
10246
- # instance, image, security-group, network-interface
10240
+ # instance, image, security group, network interface
10247
10241
  #
10248
10242
  # * **EC2-VPC-InstanceStore-Subnet**
10249
10243
  #
10250
- # instance, image, security-group, network-interface, subnet
10244
+ # instance, image, security group, network interface, subnet
10251
10245
  #
10252
10246
  # * **EC2-VPC-EBS**
10253
10247
  #
10254
- # instance, image, security-group, network-interface, volume
10248
+ # instance, image, security group, network interface, volume
10255
10249
  #
10256
10250
  # * **EC2-VPC-EBS-Subnet**
10257
10251
  #
10258
- # instance, image, security-group, network-interface, subnet, volume
10252
+ # instance, image, security group, network interface, subnet, volume
10259
10253
  #
10260
10254
  #
10261
10255
  #
@@ -10590,14 +10584,6 @@ module Aws::IAM
10590
10584
  # For more information on the EC2 scenario options, see [Supported
10591
10585
  # platforms][1] in the *Amazon EC2 User Guide*.
10592
10586
  #
10593
- # * **EC2-Classic-InstanceStore**
10594
- #
10595
- # instance, image, security group
10596
- #
10597
- # * **EC2-Classic-EBS**
10598
- #
10599
- # instance, image, security group, volume
10600
- #
10601
10587
  # * **EC2-VPC-InstanceStore**
10602
10588
  #
10603
10589
  # instance, image, security group, network interface
@@ -11772,10 +11758,12 @@ module Aws::IAM
11772
11758
  #
11773
11759
  # If the `UserName` is not specified, the user name is determined
11774
11760
  # implicitly based on the Amazon Web Services access key ID used to sign
11775
- # the request. This operation works for access keys under the Amazon Web
11776
- # Services account. Consequently, you can use this operation to manage
11777
- # Amazon Web Services account root user credentials even if the Amazon
11778
- # Web Services account has no associated users.
11761
+ # the request. If a temporary access key is used, then `UserName` is
11762
+ # required. If a long-term key is assigned to the user, then `UserName`
11763
+ # is not required. This operation works for access keys under the Amazon
11764
+ # Web Services account. Consequently, you can use this operation to
11765
+ # manage Amazon Web Services account root user credentials even if the
11766
+ # Amazon Web Services account has no associated users.
11779
11767
  #
11780
11768
  # For information about rotating keys, see [Managing keys and
11781
11769
  # certificates][1] in the *IAM User Guide*.
@@ -13225,7 +13213,7 @@ module Aws::IAM
13225
13213
  params: params,
13226
13214
  config: config)
13227
13215
  context[:gem_name] = 'aws-sdk-iam'
13228
- context[:gem_version] = '1.69.0'
13216
+ context[:gem_version] = '1.70.0'
13229
13217
  Seahorse::Client::Request.new(handlers, context)
13230
13218
  end
13231
13219
 
@@ -10624,36 +10624,28 @@ module Aws::IAM
10624
10624
  # simulation.
10625
10625
  #
10626
10626
  # Each of the EC2 scenarios requires that you specify instance, image,
10627
- # and security-group resources. If your scenario includes an EBS
10627
+ # and security group resources. If your scenario includes an EBS
10628
10628
  # volume, then you must specify that volume as a resource. If the EC2
10629
- # scenario includes VPC, then you must supply the network-interface
10629
+ # scenario includes VPC, then you must supply the network interface
10630
10630
  # resource. If it includes an IP subnet, then you must specify the
10631
10631
  # subnet resource. For more information on the EC2 scenario options,
10632
10632
  # see [Supported platforms][1] in the *Amazon EC2 User Guide*.
10633
10633
  #
10634
- # * **EC2-Classic-InstanceStore**
10635
- #
10636
- # instance, image, security-group
10637
- #
10638
- # * **EC2-Classic-EBS**
10639
- #
10640
- # instance, image, security-group, volume
10641
- #
10642
10634
  # * **EC2-VPC-InstanceStore**
10643
10635
  #
10644
- # instance, image, security-group, network-interface
10636
+ # instance, image, security group, network interface
10645
10637
  #
10646
10638
  # * **EC2-VPC-InstanceStore-Subnet**
10647
10639
  #
10648
- # instance, image, security-group, network-interface, subnet
10640
+ # instance, image, security group, network interface, subnet
10649
10641
  #
10650
10642
  # * **EC2-VPC-EBS**
10651
10643
  #
10652
- # instance, image, security-group, network-interface, volume
10644
+ # instance, image, security group, network interface, volume
10653
10645
  #
10654
10646
  # * **EC2-VPC-EBS-Subnet**
10655
10647
  #
10656
- # instance, image, security-group, network-interface, subnet, volume
10648
+ # instance, image, security group, network interface, subnet, volume
10657
10649
  #
10658
10650
  #
10659
10651
  #
@@ -10960,14 +10952,6 @@ module Aws::IAM
10960
10952
  # subnet resource. For more information on the EC2 scenario options,
10961
10953
  # see [Supported platforms][1] in the *Amazon EC2 User Guide*.
10962
10954
  #
10963
- # * **EC2-Classic-InstanceStore**
10964
- #
10965
- # instance, image, security group
10966
- #
10967
- # * **EC2-Classic-EBS**
10968
- #
10969
- # instance, image, security group, volume
10970
- #
10971
10955
  # * **EC2-VPC-InstanceStore**
10972
10956
  #
10973
10957
  # instance, image, security group, network interface
data/lib/aws-sdk-iam.rb CHANGED
@@ -70,6 +70,6 @@ require_relative 'aws-sdk-iam/customizations'
70
70
  # @!group service
71
71
  module Aws::IAM
72
72
 
73
- GEM_VERSION = '1.69.0'
73
+ GEM_VERSION = '1.70.0'
74
74
 
75
75
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-iam
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.69.0
4
+ version: 1.70.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2022-06-08 00:00:00.000000000 Z
11
+ date: 2022-08-24 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core