@aws-sdk/client-iam 3.154.0 → 3.160.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -3,6 +3,30 @@
3
3
  All notable changes to this project will be documented in this file.
4
4
  See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
5
5
 
6
+ # [3.160.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.159.0...v3.160.0) (2022-08-29)
7
+
8
+ **Note:** Version bump only for package @aws-sdk/client-iam
9
+
10
+
11
+
12
+
13
+
14
+ # [3.159.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.158.0...v3.159.0) (2022-08-26)
15
+
16
+ **Note:** Version bump only for package @aws-sdk/client-iam
17
+
18
+
19
+
20
+
21
+
22
+ # [3.157.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.156.0...v3.157.0) (2022-08-24)
23
+
24
+ **Note:** Version bump only for package @aws-sdk/client-iam
25
+
26
+
27
+
28
+
29
+
6
30
  # [3.154.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.153.0...v3.154.0) (2022-08-19)
7
31
 
8
32
  **Note:** Version bump only for package @aws-sdk/client-iam
@@ -1443,11 +1443,13 @@ export declare class IAM extends IAMClient {
1443
1443
  * If there is none, the operation returns an empty list.</p>
1444
1444
  * <p>Although each user is limited to a small number of keys, you can still paginate the
1445
1445
  * results using the <code>MaxItems</code> and <code>Marker</code> parameters.</p>
1446
- * <p>If the <code>UserName</code> field is not specified, the user name is determined
1447
- * implicitly based on the Amazon Web Services access key ID used to sign the request. This operation
1448
- * works for access keys under the Amazon Web Services account. Consequently, you can use this operation
1449
- * to manage Amazon Web Services account root user credentials even if the Amazon Web Services account has no
1450
- * associated users.</p>
1446
+ * <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
1447
+ * based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
1448
+ * used, then <code>UserName</code> is required. If a long-term key is assigned to the
1449
+ * user, then <code>UserName</code> is not required. This operation works for access keys
1450
+ * under the Amazon Web Services account. Consequently, you can use this operation to manage
1451
+ * Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
1452
+ * users.</p>
1451
1453
  * <note>
1452
1454
  * <p>To ensure the security of your Amazon Web Services account, the secret access key is accessible
1453
1455
  * only during key and user creation.</p>
@@ -2557,8 +2559,10 @@ export declare class IAM extends IAMClient {
2557
2559
  * This operation can be used to disable a user's key as part of a key rotation
2558
2560
  * workflow.</p>
2559
2561
  * <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
2560
- * based on the Amazon Web Services access key ID used to sign the request. This operation works for
2561
- * access keys under the Amazon Web Services account. Consequently, you can use this operation to manage
2562
+ * based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
2563
+ * used, then <code>UserName</code> is required. If a long-term key is assigned to the
2564
+ * user, then <code>UserName</code> is not required. This operation works for access keys
2565
+ * under the Amazon Web Services account. Consequently, you can use this operation to manage
2562
2566
  * Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
2563
2567
  * users.</p>
2564
2568
  * <p>For information about rotating keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/ManagingCredentials.html">Managing keys and certificates</a>
@@ -11,11 +11,13 @@ export interface ListAccessKeysCommandOutput extends ListAccessKeysResponse, __M
11
11
  * If there is none, the operation returns an empty list.</p>
12
12
  * <p>Although each user is limited to a small number of keys, you can still paginate the
13
13
  * results using the <code>MaxItems</code> and <code>Marker</code> parameters.</p>
14
- * <p>If the <code>UserName</code> field is not specified, the user name is determined
15
- * implicitly based on the Amazon Web Services access key ID used to sign the request. This operation
16
- * works for access keys under the Amazon Web Services account. Consequently, you can use this operation
17
- * to manage Amazon Web Services account root user credentials even if the Amazon Web Services account has no
18
- * associated users.</p>
14
+ * <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
15
+ * based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
16
+ * used, then <code>UserName</code> is required. If a long-term key is assigned to the
17
+ * user, then <code>UserName</code> is not required. This operation works for access keys
18
+ * under the Amazon Web Services account. Consequently, you can use this operation to manage
19
+ * Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
20
+ * users.</p>
19
21
  * <note>
20
22
  * <p>To ensure the security of your Amazon Web Services account, the secret access key is accessible
21
23
  * only during key and user creation.</p>
@@ -11,8 +11,10 @@ export interface UpdateAccessKeyCommandOutput extends __MetadataBearer {
11
11
  * This operation can be used to disable a user's key as part of a key rotation
12
12
  * workflow.</p>
13
13
  * <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
14
- * based on the Amazon Web Services access key ID used to sign the request. This operation works for
15
- * access keys under the Amazon Web Services account. Consequently, you can use this operation to manage
14
+ * based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
15
+ * used, then <code>UserName</code> is required. If a long-term key is assigned to the
16
+ * user, then <code>UserName</code> is not required. This operation works for access keys
17
+ * under the Amazon Web Services account. Consequently, you can use this operation to manage
16
18
  * Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
17
19
  * users.</p>
18
20
  * <p>For information about rotating keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/ManagingCredentials.html">Managing keys and certificates</a>
@@ -5985,48 +5985,36 @@ export interface SimulateCustomPolicyRequest {
5985
5985
  * not match one of the following scenarios, then you can omit this parameter. The
5986
5986
  * following list shows each of the supported scenario values and the resources that you
5987
5987
  * must define to run the simulation.</p>
5988
- * <p>Each of the EC2 scenarios requires that you specify instance, image, and
5989
- * security-group resources. If your scenario includes an EBS volume, then you must specify
5990
- * that volume as a resource. If the EC2 scenario includes VPC, then you must supply the
5991
- * network-interface resource. If it includes an IP subnet, then you must specify the
5992
- * subnet resource. For more information on the EC2 scenario options, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-supported-platforms.html">Supported platforms</a> in the <i>Amazon EC2 User
5988
+ * <p>Each of the EC2 scenarios requires that you specify instance, image, and security
5989
+ * group resources. If your scenario includes an EBS volume, then you must specify that
5990
+ * volume as a resource. If the EC2 scenario includes VPC, then you must supply the network
5991
+ * interface resource. If it includes an IP subnet, then you must specify the subnet
5992
+ * resource. For more information on the EC2 scenario options, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-supported-platforms.html">Supported platforms</a> in the <i>Amazon EC2 User
5993
5993
  * Guide</i>.</p>
5994
5994
  * <ul>
5995
5995
  * <li>
5996
5996
  * <p>
5997
- * <b>EC2-Classic-InstanceStore</b>
5998
- * </p>
5999
- * <p>instance, image, security-group</p>
6000
- * </li>
6001
- * <li>
6002
- * <p>
6003
- * <b>EC2-Classic-EBS</b>
6004
- * </p>
6005
- * <p>instance, image, security-group, volume</p>
6006
- * </li>
6007
- * <li>
6008
- * <p>
6009
5997
  * <b>EC2-VPC-InstanceStore</b>
6010
5998
  * </p>
6011
- * <p>instance, image, security-group, network-interface</p>
5999
+ * <p>instance, image, security group, network interface</p>
6012
6000
  * </li>
6013
6001
  * <li>
6014
6002
  * <p>
6015
6003
  * <b>EC2-VPC-InstanceStore-Subnet</b>
6016
6004
  * </p>
6017
- * <p>instance, image, security-group, network-interface, subnet</p>
6005
+ * <p>instance, image, security group, network interface, subnet</p>
6018
6006
  * </li>
6019
6007
  * <li>
6020
6008
  * <p>
6021
6009
  * <b>EC2-VPC-EBS</b>
6022
6010
  * </p>
6023
- * <p>instance, image, security-group, network-interface, volume</p>
6011
+ * <p>instance, image, security group, network interface, volume</p>
6024
6012
  * </li>
6025
6013
  * <li>
6026
6014
  * <p>
6027
6015
  * <b>EC2-VPC-EBS-Subnet</b>
6028
6016
  * </p>
6029
- * <p>instance, image, security-group, network-interface, subnet, volume</p>
6017
+ * <p>instance, image, security group, network interface, subnet, volume</p>
6030
6018
  * </li>
6031
6019
  * </ul>
6032
6020
  */
@@ -6437,18 +6425,6 @@ export interface SimulatePrincipalPolicyRequest {
6437
6425
  * <ul>
6438
6426
  * <li>
6439
6427
  * <p>
6440
- * <b>EC2-Classic-InstanceStore</b>
6441
- * </p>
6442
- * <p>instance, image, security group</p>
6443
- * </li>
6444
- * <li>
6445
- * <p>
6446
- * <b>EC2-Classic-EBS</b>
6447
- * </p>
6448
- * <p>instance, image, security group, volume</p>
6449
- * </li>
6450
- * <li>
6451
- * <p>
6452
6428
  * <b>EC2-VPC-InstanceStore</b>
6453
6429
  * </p>
6454
6430
  * <p>instance, image, security group, network interface</p>
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-iam",
3
3
  "description": "AWS SDK for JavaScript Iam Client for Node.js, Browser and React Native",
4
- "version": "3.154.0",
4
+ "version": "3.160.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -18,38 +18,38 @@
18
18
  "dependencies": {
19
19
  "@aws-crypto/sha256-browser": "2.0.0",
20
20
  "@aws-crypto/sha256-js": "2.0.0",
21
- "@aws-sdk/client-sts": "3.154.0",
22
- "@aws-sdk/config-resolver": "3.130.0",
23
- "@aws-sdk/credential-provider-node": "3.154.0",
24
- "@aws-sdk/fetch-http-handler": "3.131.0",
25
- "@aws-sdk/hash-node": "3.127.0",
26
- "@aws-sdk/invalid-dependency": "3.127.0",
27
- "@aws-sdk/middleware-content-length": "3.127.0",
28
- "@aws-sdk/middleware-host-header": "3.127.0",
29
- "@aws-sdk/middleware-logger": "3.127.0",
30
- "@aws-sdk/middleware-recursion-detection": "3.127.0",
31
- "@aws-sdk/middleware-retry": "3.127.0",
32
- "@aws-sdk/middleware-serde": "3.127.0",
33
- "@aws-sdk/middleware-signing": "3.130.0",
34
- "@aws-sdk/middleware-stack": "3.127.0",
35
- "@aws-sdk/middleware-user-agent": "3.127.0",
36
- "@aws-sdk/node-config-provider": "3.127.0",
37
- "@aws-sdk/node-http-handler": "3.127.0",
38
- "@aws-sdk/protocol-http": "3.127.0",
39
- "@aws-sdk/smithy-client": "3.142.0",
40
- "@aws-sdk/types": "3.127.0",
41
- "@aws-sdk/url-parser": "3.127.0",
21
+ "@aws-sdk/client-sts": "3.160.0",
22
+ "@aws-sdk/config-resolver": "3.160.0",
23
+ "@aws-sdk/credential-provider-node": "3.160.0",
24
+ "@aws-sdk/fetch-http-handler": "3.160.0",
25
+ "@aws-sdk/hash-node": "3.160.0",
26
+ "@aws-sdk/invalid-dependency": "3.160.0",
27
+ "@aws-sdk/middleware-content-length": "3.160.0",
28
+ "@aws-sdk/middleware-host-header": "3.160.0",
29
+ "@aws-sdk/middleware-logger": "3.160.0",
30
+ "@aws-sdk/middleware-recursion-detection": "3.160.0",
31
+ "@aws-sdk/middleware-retry": "3.160.0",
32
+ "@aws-sdk/middleware-serde": "3.160.0",
33
+ "@aws-sdk/middleware-signing": "3.160.0",
34
+ "@aws-sdk/middleware-stack": "3.160.0",
35
+ "@aws-sdk/middleware-user-agent": "3.160.0",
36
+ "@aws-sdk/node-config-provider": "3.160.0",
37
+ "@aws-sdk/node-http-handler": "3.160.0",
38
+ "@aws-sdk/protocol-http": "3.160.0",
39
+ "@aws-sdk/smithy-client": "3.160.0",
40
+ "@aws-sdk/types": "3.160.0",
41
+ "@aws-sdk/url-parser": "3.160.0",
42
42
  "@aws-sdk/util-base64-browser": "3.109.0",
43
43
  "@aws-sdk/util-base64-node": "3.55.0",
44
44
  "@aws-sdk/util-body-length-browser": "3.154.0",
45
45
  "@aws-sdk/util-body-length-node": "3.55.0",
46
- "@aws-sdk/util-defaults-mode-browser": "3.142.0",
47
- "@aws-sdk/util-defaults-mode-node": "3.142.0",
48
- "@aws-sdk/util-user-agent-browser": "3.127.0",
49
- "@aws-sdk/util-user-agent-node": "3.127.0",
46
+ "@aws-sdk/util-defaults-mode-browser": "3.160.0",
47
+ "@aws-sdk/util-defaults-mode-node": "3.160.0",
48
+ "@aws-sdk/util-user-agent-browser": "3.160.0",
49
+ "@aws-sdk/util-user-agent-node": "3.160.0",
50
50
  "@aws-sdk/util-utf8-browser": "3.109.0",
51
51
  "@aws-sdk/util-utf8-node": "3.109.0",
52
- "@aws-sdk/util-waiter": "3.127.0",
52
+ "@aws-sdk/util-waiter": "3.160.0",
53
53
  "entities": "2.2.0",
54
54
  "fast-xml-parser": "3.19.0",
55
55
  "tslib": "^2.3.1"