Skip to content

Commit 2e58d72

Browse files
author
awstools
committed
docs(client-iam): Documentation updates for AWS Identity and Access Management (IAM).
1 parent ccd5d97 commit 2e58d72

File tree

5 files changed

+35
-51
lines changed

5 files changed

+35
-51
lines changed

‎clients/client-iam/src/IAM.ts

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3928,11 +3928,13 @@ export class IAM extends IAMClient {
39283928
* If there is none, the operation returns an empty list.</p>
39293929
* <p>Although each user is limited to a small number of keys, you can still paginate the
39303930
* results using the <code>MaxItems</code> and <code>Marker</code> parameters.</p>
3931-
* <p>If the <code>UserName</code> field is not specified, the user name is determined
3932-
* implicitly based on the Amazon Web Services access key ID used to sign the request. This operation
3933-
* works for access keys under the Amazon Web Services account. Consequently, you can use this operation
3934-
* to manage Amazon Web Services account root user credentials even if the Amazon Web Services account has no
3935-
* associated users.</p>
3931+
* <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
3932+
* based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
3933+
* used, then <code>UserName</code> is required. If a long-term key is assigned to the
3934+
* user, then <code>UserName</code> is not required. This operation works for access keys
3935+
* under the Amazon Web Services account. Consequently, you can use this operation to manage
3936+
* Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
3937+
* users.</p>
39363938
* <note>
39373939
* <p>To ensure the security of your Amazon Web Services account, the secret access key is accessible
39383940
* only during key and user creation.</p>
@@ -6642,8 +6644,10 @@ export class IAM extends IAMClient {
66426644
* This operation can be used to disable a user's key as part of a key rotation
66436645
* workflow.</p>
66446646
* <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
6645-
* based on the Amazon Web Services access key ID used to sign the request. This operation works for
6646-
* access keys under the Amazon Web Services account. Consequently, you can use this operation to manage
6647+
* based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
6648+
* used, then <code>UserName</code> is required. If a long-term key is assigned to the
6649+
* user, then <code>UserName</code> is not required. This operation works for access keys
6650+
* under the Amazon Web Services account. Consequently, you can use this operation to manage
66476651
* Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
66486652
* users.</p>
66496653
* <p>For information about rotating keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/ManagingCredentials.html">Managing keys and certificates</a>

‎clients/client-iam/src/commands/ListAccessKeysCommand.ts

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,13 @@ export interface ListAccessKeysCommandOutput extends ListAccessKeysResponse, __M
3232
* If there is none, the operation returns an empty list.</p>
3333
* <p>Although each user is limited to a small number of keys, you can still paginate the
3434
* results using the <code>MaxItems</code> and <code>Marker</code> parameters.</p>
35-
* <p>If the <code>UserName</code> field is not specified, the user name is determined
36-
* implicitly based on the Amazon Web Services access key ID used to sign the request. This operation
37-
* works for access keys under the Amazon Web Services account. Consequently, you can use this operation
38-
* to manage Amazon Web Services account root user credentials even if the Amazon Web Services account has no
39-
* associated users.</p>
35+
* <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
36+
* based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
37+
* used, then <code>UserName</code> is required. If a long-term key is assigned to the
38+
* user, then <code>UserName</code> is not required. This operation works for access keys
39+
* under the Amazon Web Services account. Consequently, you can use this operation to manage
40+
* Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
41+
* users.</p>
4042
* <note>
4143
* <p>To ensure the security of your Amazon Web Services account, the secret access key is accessible
4244
* only during key and user creation.</p>

‎clients/client-iam/src/commands/UpdateAccessKeyCommand.ts

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,10 @@ export interface UpdateAccessKeyCommandOutput extends __MetadataBearer {}
2727
* This operation can be used to disable a user's key as part of a key rotation
2828
* workflow.</p>
2929
* <p>If the <code>UserName</code> is not specified, the user name is determined implicitly
30-
* based on the Amazon Web Services access key ID used to sign the request. This operation works for
31-
* access keys under the Amazon Web Services account. Consequently, you can use this operation to manage
30+
* based on the Amazon Web Services access key ID used to sign the request. If a temporary access key is
31+
* used, then <code>UserName</code> is required. If a long-term key is assigned to the
32+
* user, then <code>UserName</code> is not required. This operation works for access keys
33+
* under the Amazon Web Services account. Consequently, you can use this operation to manage
3234
* Amazon Web Services account root user credentials even if the Amazon Web Services account has no associated
3335
* users.</p>
3436
* <p>For information about rotating keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/ManagingCredentials.html">Managing keys and certificates</a>

‎clients/client-iam/src/models/models_0.ts

Lines changed: 9 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -6893,48 +6893,36 @@ export interface SimulateCustomPolicyRequest {
68936893
* not match one of the following scenarios, then you can omit this parameter. The
68946894
* following list shows each of the supported scenario values and the resources that you
68956895
* must define to run the simulation.</p>
6896-
* <p>Each of the EC2 scenarios requires that you specify instance, image, and
6897-
* security-group resources. If your scenario includes an EBS volume, then you must specify
6898-
* that volume as a resource. If the EC2 scenario includes VPC, then you must supply the
6899-
* network-interface resource. If it includes an IP subnet, then you must specify the
6900-
* 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
6896+
* <p>Each of the EC2 scenarios requires that you specify instance, image, and security
6897+
* group resources. If your scenario includes an EBS volume, then you must specify that
6898+
* volume as a resource. If the EC2 scenario includes VPC, then you must supply the network
6899+
* interface resource. If it includes an IP subnet, then you must specify the subnet
6900+
* 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
69016901
* Guide</i>.</p>
69026902
* <ul>
69036903
* <li>
69046904
* <p>
6905-
* <b>EC2-Classic-InstanceStore</b>
6906-
* </p>
6907-
* <p>instance, image, security-group</p>
6908-
* </li>
6909-
* <li>
6910-
* <p>
6911-
* <b>EC2-Classic-EBS</b>
6912-
* </p>
6913-
* <p>instance, image, security-group, volume</p>
6914-
* </li>
6915-
* <li>
6916-
* <p>
69176905
* <b>EC2-VPC-InstanceStore</b>
69186906
* </p>
6919-
* <p>instance, image, security-group, network-interface</p>
6907+
* <p>instance, image, security group, network interface</p>
69206908
* </li>
69216909
* <li>
69226910
* <p>
69236911
* <b>EC2-VPC-InstanceStore-Subnet</b>
69246912
* </p>
6925-
* <p>instance, image, security-group, network-interface, subnet</p>
6913+
* <p>instance, image, security group, network interface, subnet</p>
69266914
* </li>
69276915
* <li>
69286916
* <p>
69296917
* <b>EC2-VPC-EBS</b>
69306918
* </p>
6931-
* <p>instance, image, security-group, network-interface, volume</p>
6919+
* <p>instance, image, security group, network interface, volume</p>
69326920
* </li>
69336921
* <li>
69346922
* <p>
69356923
* <b>EC2-VPC-EBS-Subnet</b>
69366924
* </p>
6937-
* <p>instance, image, security-group, network-interface, subnet, volume</p>
6925+
* <p>instance, image, security group, network interface, subnet, volume</p>
69386926
* </li>
69396927
* </ul>
69406928
*/
@@ -7385,18 +7373,6 @@ export interface SimulatePrincipalPolicyRequest {
73857373
* <ul>
73867374
* <li>
73877375
* <p>
7388-
* <b>EC2-Classic-InstanceStore</b>
7389-
* </p>
7390-
* <p>instance, image, security group</p>
7391-
* </li>
7392-
* <li>
7393-
* <p>
7394-
* <b>EC2-Classic-EBS</b>
7395-
* </p>
7396-
* <p>instance, image, security group, volume</p>
7397-
* </li>
7398-
* <li>
7399-
* <p>
74007376
* <b>EC2-VPC-InstanceStore</b>
74017377
* </p>
74027378
* <p>instance, image, security group, network interface</p>

0 commit comments

Comments
 (0)