@aws-sdk/client-sts 3.42.0 → 3.43.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,17 @@
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.43.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.42.0...v3.43.0) (2021-11-29)
7
+
8
+
9
+ ### Features
10
+
11
+ * **clients:** update clients as of 11/28/2021 ([#3072](https://github.com/aws/aws-sdk-js-v3/issues/3072)) ([2ad1622](https://github.com/aws/aws-sdk-js-v3/commit/2ad1622ba8586b926fe508055211803bb29e3976))
12
+
13
+
14
+
15
+
16
+
6
17
  # [3.42.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.41.0...v3.42.0) (2021-11-19)
7
18
 
8
19
 
@@ -18,20 +18,19 @@ import { STSClient } from "./STSClient";
18
18
  export declare class STS extends STSClient {
19
19
  /**
20
20
  * <p>Returns a set of temporary security credentials that you can use to access Amazon Web Services
21
- * resources that you might not normally have access to. These temporary credentials
22
- * consist of an access key ID, a secret access key, and a security token. Typically, you
23
- * use <code>AssumeRole</code> within your account or for cross-account access. For a
24
- * comparison of <code>AssumeRole</code> with other API operations that produce temporary
25
- * credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
26
- * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing
27
- * the STS API operations</a> in the
28
- * <i>IAM User Guide</i>.</p>
21
+ * resources that you might not normally have access to. These temporary credentials consist
22
+ * of an access key ID, a secret access key, and a security token. Typically, you use
23
+ * <code>AssumeRole</code> within your account or for cross-account access. For a
24
+ * comparison of <code>AssumeRole</code> with other API operations that produce temporary
25
+ * credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
26
+ * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
27
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
29
28
  * <p>
30
29
  * <b>Permissions</b>
31
30
  * </p>
32
31
  * <p>The temporary security credentials created by <code>AssumeRole</code> can be used to
33
32
  * make API calls to any Amazon Web Services service with the following exception: You cannot call the
34
- * STS <code>GetFederationToken</code> or <code>GetSessionToken</code> API
33
+ * Amazon Web Services STS <code>GetFederationToken</code> or <code>GetSessionToken</code> API
35
34
  * operations.</p>
36
35
  * <p>(Optional) You can pass inline or managed <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">session policies</a> to
37
36
  * this operation. You can pass a single JSON policy document to use as an inline session
@@ -45,28 +44,35 @@ export declare class STS extends STSClient {
45
44
  * by the identity-based policy of the role that is being assumed. For more information, see
46
45
  * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session
47
46
  * Policies</a> in the <i>IAM User Guide</i>.</p>
48
- * <p>To assume a role from a different account, your account must be trusted by the
47
+ * <p>When you create a role, you create two policies: A role trust policy that specifies
48
+ * <i>who</i> can assume the role and a permissions policy that specifies
49
+ * <i>what</i> can be done with the role. You specify the trusted principal
50
+ * who is allowed to assume the role in the role trust policy.</p>
51
+ * <p>To assume a role from a different account, your Amazon Web Services account must be trusted by the
49
52
  * role. The trust relationship is defined in the role's trust policy when the role is
50
53
  * created. That trust policy states which accounts are allowed to delegate that access to
51
54
  * users in the account. </p>
52
55
  * <p>A user who wants to access a role in a different account must also have permissions that
53
56
  * are delegated from the user account administrator. The administrator must attach a policy
54
57
  * that allows the user to call <code>AssumeRole</code> for the ARN of the role in the other
55
- * account. If the user is in the same account as the role, then you can do either of the
58
+ * account.</p>
59
+ * <p>To allow a user to assume a role in the same account, you can do either of the
56
60
  * following:</p>
57
61
  * <ul>
58
62
  * <li>
59
- * <p>Attach a policy to the user (identical to the previous user in a different
60
- * account).</p>
63
+ * <p>Attach a policy to the user that allows the user to call
64
+ * <code>AssumeRole</code> (as long as the role's trust policy trusts the account).</p>
61
65
  * </li>
62
66
  * <li>
63
67
  * <p>Add the user as a principal directly in the role's trust policy.</p>
64
68
  * </li>
65
69
  * </ul>
66
- * <p>In this case, the trust policy acts as an IAM resource-based policy. Users in the same
67
- * account as the role do not need explicit permission to assume the role. For more
68
- * information about trust policies and resource-based policies, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html">IAM Policies</a> in
69
- * the <i>IAM User Guide</i>.</p>
70
+ * <p>You can do either because the role’s trust policy acts as an IAM resource-based
71
+ * policy. When a resource-based policy grants access to a principal in the same account, no
72
+ * additional identity-based policy is required. For more information about trust policies and
73
+ * resource-based policies, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html">IAM Policies</a> in the
74
+ * <i>IAM User Guide</i>.</p>
75
+ *
70
76
  * <p>
71
77
  * <b>Tags</b>
72
78
  * </p>
@@ -112,7 +118,7 @@ export declare class STS extends STSClient {
112
118
  * credentials or configuration. For a comparison of <code>AssumeRoleWithSAML</code> with the
113
119
  * other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
114
120
  * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
115
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
121
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
116
122
  * <p>The temporary security credentials returned by this operation consist of an access key
117
123
  * ID, a secret access key, and a security token. Applications can use these temporary
118
124
  * security credentials to sign calls to Amazon Web Services services.</p>
@@ -134,15 +140,15 @@ export declare class STS extends STSClient {
134
140
  * console URL. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html">Using IAM Roles</a> in the
135
141
  * <i>IAM User Guide</i>.</p>
136
142
  * <note>
137
- * <p>
138
- * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-role-chaining">Role chaining</a> limits your CLI or Amazon Web Services API
139
- * role session to a maximum of one hour. When you use the <code>AssumeRole</code> API
140
- * operation to assume a role, you can specify the duration of your role session with
141
- * the <code>DurationSeconds</code> parameter. You can specify a parameter value of up
142
- * to 43200 seconds (12 hours), depending on the maximum session duration setting for
143
- * your role. However, if you assume a role using role chaining and provide a
144
- * <code>DurationSeconds</code> parameter value greater than one hour, the
145
- * operation fails.</p>
143
+ * <p>
144
+ * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-role-chaining">Role chaining</a> limits your CLI or Amazon Web Services API role
145
+ * session to a maximum of one hour. When you use the <code>AssumeRole</code> API operation
146
+ * to assume a role, you can specify the duration of your role session with the
147
+ * <code>DurationSeconds</code> parameter. You can specify a parameter value of up to
148
+ * 43200 seconds (12 hours), depending on the maximum session duration setting for your
149
+ * role. However, if you assume a role using role chaining and provide a
150
+ * <code>DurationSeconds</code> parameter value greater than one hour, the operation
151
+ * fails.</p>
146
152
  * </note>
147
153
  * <p>
148
154
  * <b>Permissions</b>
@@ -194,9 +200,9 @@ export declare class STS extends STSClient {
194
200
  * request are to the upper size limit.
195
201
  * </p>
196
202
  * </note>
197
- * <p>You can pass a session tag with the same key as a tag that is
198
- * attached to the role. When you do, session tags override the role's tags with the same
199
- * key.</p>
203
+ *
204
+ * <p>You can pass a session tag with the same key as a tag that is attached to the role. When
205
+ * you do, session tags override the role's tags with the same key.</p>
200
206
  * <p>An administrator must grant you the permissions necessary to pass session tags. The
201
207
  * administrator can also create granular permissions to allow you to pass only specific
202
208
  * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using Tags
@@ -265,7 +271,7 @@ export declare class STS extends STSClient {
265
271
  * <code>AssumeRoleWithWebIdentity</code> with the other API operations that produce
266
272
  * temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
267
273
  * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
268
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
274
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
269
275
  * <p>The temporary security credentials returned by this API consist of an access key ID, a
270
276
  * secret access key, and a security token. Applications can use these temporary security
271
277
  * credentials to sign calls to Amazon Web Services service API operations.</p>
@@ -323,9 +329,9 @@ export declare class STS extends STSClient {
323
329
  * request are to the upper size limit.
324
330
  * </p>
325
331
  * </note>
326
- * <p>You can pass a session tag with the same key as a tag that is
327
- * attached to the role. When you do, the session tag overrides the role tag with the same
328
- * key.</p>
332
+ *
333
+ * <p>You can pass a session tag with the same key as a tag that is attached to the role. When
334
+ * you do, the session tag overrides the role tag with the same key.</p>
329
335
  * <p>An administrator must grant you the permissions necessary to pass session tags. The
330
336
  * administrator can also create granular permissions to allow you to pass only specific
331
337
  * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using Tags
@@ -395,9 +401,9 @@ export declare class STS extends STSClient {
395
401
  * documentation for an individual operation indicates whether that operation returns an
396
402
  * encoded message in addition to returning an HTTP code.</p>
397
403
  * </note>
398
- * <p>The message is encoded because the details of the authorization status can constitute
404
+ * <p>The message is encoded because the details of the authorization status can contain
399
405
  * privileged information that the user who requested the operation should not see. To decode
400
- * an authorization status message, a user must be granted permissions via an IAM policy to
406
+ * an authorization status message, a user must be granted permissions through an IAM <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html">policy</a> to
401
407
  * request the <code>DecodeAuthorizationMessage</code>
402
408
  * (<code>sts:DecodeAuthorizationMessage</code>) action. </p>
403
409
  * <p>The decoded message includes the following type of information:</p>
@@ -426,38 +432,38 @@ export declare class STS extends STSClient {
426
432
  decodeAuthorizationMessage(args: DecodeAuthorizationMessageCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DecodeAuthorizationMessageCommandOutput) => void): void;
427
433
  /**
428
434
  * <p>Returns the account identifier for the specified access key ID.</p>
429
- * <p>Access keys consist of two parts: an access key ID (for example,
430
- * <code>AKIAIOSFODNN7EXAMPLE</code>) and a secret access key (for example,
431
- * <code>wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY</code>). For more information about
432
- * access keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html">Managing Access Keys for IAM
433
- * Users</a> in the <i>IAM User Guide</i>.</p>
434
- * <p>When you pass an access key ID to this operation, it returns the ID of the Amazon Web Services
435
- * account to which the keys belong. Access key IDs beginning with <code>AKIA</code> are
436
- * long-term credentials for an IAM user or the Amazon Web Services account root user. Access key IDs
437
- * beginning with <code>ASIA</code> are temporary credentials that are created using STS
438
- * operations. If the account in the response belongs to you, you can sign in as the root
439
- * user and review your root user access keys. Then, you can pull a <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_getting-report.html">credentials report</a> to learn which IAM user owns the keys. To learn who
440
- * requested the temporary credentials for an <code>ASIA</code> access key, view the STS
441
- * events in your <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/cloudtrail-integration.html">CloudTrail logs</a> in the
442
- * <i>IAM User Guide</i>.</p>
443
- * <p>This operation does not indicate the state of the access key. The key might be active,
444
- * inactive, or deleted. Active keys might not have permissions to perform an operation.
445
- * Providing a deleted access key might return an error that the key doesn't exist.</p>
435
+ * <p>Access keys consist of two parts: an access key ID (for example,
436
+ * <code>AKIAIOSFODNN7EXAMPLE</code>) and a secret access key (for example,
437
+ * <code>wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY</code>). For more information about
438
+ * access keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html">Managing Access Keys for IAM
439
+ * Users</a> in the <i>IAM User Guide</i>.</p>
440
+ * <p>When you pass an access key ID to this operation, it returns the ID of the Amazon Web Services account
441
+ * to which the keys belong. Access key IDs beginning with <code>AKIA</code> are long-term
442
+ * credentials for an IAM user or the Amazon Web Services account root user. Access key IDs beginning with
443
+ * <code>ASIA</code> are temporary credentials that are created using STS operations. If
444
+ * the account in the response belongs to you, you can sign in as the root user and review
445
+ * your root user access keys. Then, you can pull a <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_getting-report.html">credentials report</a> to
446
+ * learn which IAM user owns the keys. To learn who requested the temporary credentials for
447
+ * an <code>ASIA</code> access key, view the STS events in your <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/cloudtrail-integration.html">CloudTrail logs</a> in the
448
+ * <i>IAM User Guide</i>.</p>
449
+ * <p>This operation does not indicate the state of the access key. The key might be active,
450
+ * inactive, or deleted. Active keys might not have permissions to perform an operation.
451
+ * Providing a deleted access key might return an error that the key doesn't exist.</p>
446
452
  */
447
453
  getAccessKeyInfo(args: GetAccessKeyInfoCommandInput, options?: __HttpHandlerOptions): Promise<GetAccessKeyInfoCommandOutput>;
448
454
  getAccessKeyInfo(args: GetAccessKeyInfoCommandInput, cb: (err: any, data?: GetAccessKeyInfoCommandOutput) => void): void;
449
455
  getAccessKeyInfo(args: GetAccessKeyInfoCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetAccessKeyInfoCommandOutput) => void): void;
450
456
  /**
451
457
  * <p>Returns details about the IAM user or role whose credentials are used to call the
452
- * operation.</p>
453
- * <note>
458
+ * operation.</p>
459
+ * <note>
454
460
  * <p>No permissions are required to perform this operation. If an administrator adds a
455
- * policy to your IAM user or role that explicitly denies access to the
456
- * <code>sts:GetCallerIdentity</code> action, you can still perform this operation.
457
- * Permissions are not required because the same information is returned when an IAM
458
- * user or role is denied access. To view an example response, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_access-denied-delete-mfa">I Am Not Authorized to Perform: iam:DeleteVirtualMFADevice</a> in the
459
- * <i>IAM User Guide</i>.</p>
460
- * </note>
461
+ * policy to your IAM user or role that explicitly denies access to the
462
+ * <code>sts:GetCallerIdentity</code> action, you can still perform this operation.
463
+ * Permissions are not required because the same information is returned when an IAM user
464
+ * or role is denied access. To view an example response, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_access-denied-delete-mfa">I Am Not Authorized to Perform: iam:DeleteVirtualMFADevice</a> in the
465
+ * <i>IAM User Guide</i>.</p>
466
+ * </note>
461
467
  */
462
468
  getCallerIdentity(args: GetCallerIdentityCommandInput, options?: __HttpHandlerOptions): Promise<GetCallerIdentityCommandOutput>;
463
469
  getCallerIdentity(args: GetCallerIdentityCommandInput, cb: (err: any, data?: GetCallerIdentityCommandOutput) => void): void;
@@ -472,7 +478,7 @@ export declare class STS extends STSClient {
472
478
  * server-based application. For a comparison of <code>GetFederationToken</code> with the
473
479
  * other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
474
480
  * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
475
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
481
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
476
482
  * <note>
477
483
  * <p>You can create a mobile-based or browser-based app that can authenticate users using
478
484
  * a web identity provider like Login with Amazon, Facebook, Google, or an OpenID
@@ -491,8 +497,8 @@ export declare class STS extends STSClient {
491
497
  * </p>
492
498
  * <p>The temporary credentials are valid for the specified duration, from 900 seconds (15
493
499
  * minutes) up to a maximum of 129,600 seconds (36 hours). The default session duration is
494
- * 43,200 seconds (12 hours). Temporary credentials that are obtained by using Amazon Web Services account
495
- * root user credentials have a maximum duration of 3,600 seconds (1 hour).</p>
500
+ * 43,200 seconds (12 hours). Temporary credentials obtained by using the Amazon Web Services account root
501
+ * user credentials have a maximum duration of 3,600 seconds (1 hour).</p>
496
502
  * <p>
497
503
  * <b>Permissions</b>
498
504
  * </p>
@@ -530,78 +536,25 @@ export declare class STS extends STSClient {
530
536
  * <p>(Optional) You can pass tag key-value pairs to your session. These are called session
531
537
  * tags. For more information about session tags, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Passing Session Tags in STS</a> in the
532
538
  * <i>IAM User Guide</i>.</p>
533
- * <note>
534
- * <p>You can create a mobile-based or browser-based app that can authenticate users
535
- * using a web identity provider like Login with Amazon, Facebook, Google, or an OpenID
536
- * Connect-compatible identity provider. In this case, we recommend that you use <a href="http://aws.amazon.com/cognito/">Amazon Cognito</a> or
537
- * <code>AssumeRoleWithWebIdentity</code>. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity">Federation Through a Web-based Identity Provider</a> in the
538
- * <i>IAM User Guide</i>.</p>
539
- * </note>
540
- * <p>You can also call <code>GetFederationToken</code> using the security credentials of an
541
- * Amazon Web Services account root user, but we do not recommend it. Instead, we recommend that you
542
- * create an IAM user for the purpose of the proxy application. Then attach a policy to
543
- * the IAM user that limits federated users to only the actions and resources that they
544
- * need to access. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html">IAM Best Practices</a> in the
545
- * <i>IAM User Guide</i>. </p>
546
- * <p>
547
- * <b>Session duration</b>
548
- * </p>
549
- * <p>The temporary credentials are valid for the specified duration, from 900 seconds (15
550
- * minutes) up to a maximum of 129,600 seconds (36 hours). The default session duration is
551
- * 43,200 seconds (12 hours). Temporary credentials that are obtained by using Amazon Web Services
552
- * account root user credentials have a maximum duration of 3,600 seconds (1 hour).</p>
553
- * <p>
554
- * <b>Permissions</b>
555
- * </p>
556
- * <p>You can use the temporary credentials created by <code>GetFederationToken</code> in
557
- * any Amazon Web Services service except the following:</p>
558
- * <ul>
559
- * <li>
560
- * <p>You cannot call any IAM operations using the CLI or the Amazon Web Services API.
561
- * </p>
562
- * </li>
563
- * <li>
564
- * <p>You cannot call any STS operations except
565
- * <code>GetCallerIdentity</code>.</p>
566
- * </li>
567
- * </ul>
568
- * <p>You must pass an inline or managed <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">session policy</a> to
569
- * this operation. You can pass a single JSON policy document to use as an inline session
570
- * policy. You can also specify up to 10 managed policies to use as managed session
571
- * policies. The plain text that you use for both inline and managed session policies can't
572
- * exceed 2,048 characters.</p>
573
- * <p>Though the session policy parameters are optional, if you do not pass a policy, then
574
- * the resulting federated user session has no permissions. When you pass session policies,
575
- * the session permissions are the intersection of the IAM user policies and the session
576
- * policies that you pass. This gives you a way to further restrict the permissions for a
577
- * federated user. You cannot use session policies to grant more permissions than those
578
- * that are defined in the permissions policy of the IAM user. For more information, see
579
- * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session Policies</a>
580
- * in the <i>IAM User Guide</i>. For information about using
581
- * <code>GetFederationToken</code> to create temporary security credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getfederationtoken">GetFederationToken—Federation Through a Custom Identity Broker</a>. </p>
582
- * <p>You can use the credentials to access a resource that has a resource-based policy. If
583
- * that policy specifically references the federated user session in the
584
- * <code>Principal</code> element of the policy, the session has the permissions
585
- * allowed by the policy. These permissions are granted in addition to the permissions
586
- * granted by the session policies.</p>
587
- * <p>
588
- * <b>Tags</b>
589
- * </p>
590
- * <p>(Optional) You can pass tag key-value pairs to your session. These are called session
591
- * tags. For more information about session tags, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Passing Session Tags in STS</a> in
592
- * the <i>IAM User Guide</i>.</p>
593
- * <p>An administrator must grant you the permissions necessary to pass session tags. The
594
- * administrator can also create granular permissions to allow you to pass only specific
595
- * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using
596
- * Tags for Attribute-Based Access Control</a> in the
597
- * <i>IAM User Guide</i>.</p>
598
- * <p>Tag key–value pairs are not case sensitive, but case is preserved. This means that you
599
- * cannot have separate <code>Department</code> and <code>department</code> tag keys.
600
- * Assume that the user that you are federating has the
601
- * <code>Department</code>=<code>Marketing</code> tag and you pass the
602
- * <code>department</code>=<code>engineering</code> session tag.
603
- * <code>Department</code> and <code>department</code> are not saved as separate tags,
604
- * and the session tag passed in the request takes precedence over the user tag.</p>
539
+ * <note>
540
+ * <p>You can create a mobile-based or browser-based app that can authenticate users using
541
+ * a web identity provider like Login with Amazon, Facebook, Google, or an OpenID
542
+ * Connect-compatible identity provider. In this case, we recommend that you use <a href="http://aws.amazon.com/cognito/">Amazon Cognito</a> or
543
+ * <code>AssumeRoleWithWebIdentity</code>. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity">Federation Through a Web-based Identity Provider</a> in the
544
+ * <i>IAM User Guide</i>.</p>
545
+ * </note>
546
+ * <p>An administrator must grant you the permissions necessary to pass session tags. The
547
+ * administrator can also create granular permissions to allow you to pass only specific
548
+ * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using Tags
549
+ * for Attribute-Based Access Control</a> in the
550
+ * <i>IAM User Guide</i>.</p>
551
+ * <p>Tag key–value pairs are not case sensitive, but case is preserved. This means that you
552
+ * cannot have separate <code>Department</code> and <code>department</code> tag keys. Assume
553
+ * that the user that you are federating has the
554
+ * <code>Department</code>=<code>Marketing</code> tag and you pass the
555
+ * <code>department</code>=<code>engineering</code> session tag. <code>Department</code>
556
+ * and <code>department</code> are not saved as separate tags, and the session tag passed in
557
+ * the request takes precedence over the user tag.</p>
605
558
  */
606
559
  getFederationToken(args: GetFederationTokenCommandInput, options?: __HttpHandlerOptions): Promise<GetFederationTokenCommandOutput>;
607
560
  getFederationToken(args: GetFederationTokenCommandInput, cb: (err: any, data?: GetFederationTokenCommandOutput) => void): void;
@@ -618,7 +571,7 @@ export declare class STS extends STSClient {
618
571
  * the API returns an access denied error. For a comparison of <code>GetSessionToken</code>
619
572
  * with the other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting
620
573
  * Temporary Security Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
621
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
574
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
622
575
  * <p>
623
576
  * <b>Session Duration</b>
624
577
  * </p>
@@ -8,20 +8,19 @@ export interface AssumeRoleCommandOutput extends AssumeRoleResponse, __MetadataB
8
8
  }
9
9
  /**
10
10
  * <p>Returns a set of temporary security credentials that you can use to access Amazon Web Services
11
- * resources that you might not normally have access to. These temporary credentials
12
- * consist of an access key ID, a secret access key, and a security token. Typically, you
13
- * use <code>AssumeRole</code> within your account or for cross-account access. For a
14
- * comparison of <code>AssumeRole</code> with other API operations that produce temporary
15
- * credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
16
- * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing
17
- * the STS API operations</a> in the
18
- * <i>IAM User Guide</i>.</p>
11
+ * resources that you might not normally have access to. These temporary credentials consist
12
+ * of an access key ID, a secret access key, and a security token. Typically, you use
13
+ * <code>AssumeRole</code> within your account or for cross-account access. For a
14
+ * comparison of <code>AssumeRole</code> with other API operations that produce temporary
15
+ * credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
16
+ * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
17
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
19
18
  * <p>
20
19
  * <b>Permissions</b>
21
20
  * </p>
22
21
  * <p>The temporary security credentials created by <code>AssumeRole</code> can be used to
23
22
  * make API calls to any Amazon Web Services service with the following exception: You cannot call the
24
- * STS <code>GetFederationToken</code> or <code>GetSessionToken</code> API
23
+ * Amazon Web Services STS <code>GetFederationToken</code> or <code>GetSessionToken</code> API
25
24
  * operations.</p>
26
25
  * <p>(Optional) You can pass inline or managed <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">session policies</a> to
27
26
  * this operation. You can pass a single JSON policy document to use as an inline session
@@ -35,28 +34,35 @@ export interface AssumeRoleCommandOutput extends AssumeRoleResponse, __MetadataB
35
34
  * by the identity-based policy of the role that is being assumed. For more information, see
36
35
  * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session
37
36
  * Policies</a> in the <i>IAM User Guide</i>.</p>
38
- * <p>To assume a role from a different account, your account must be trusted by the
37
+ * <p>When you create a role, you create two policies: A role trust policy that specifies
38
+ * <i>who</i> can assume the role and a permissions policy that specifies
39
+ * <i>what</i> can be done with the role. You specify the trusted principal
40
+ * who is allowed to assume the role in the role trust policy.</p>
41
+ * <p>To assume a role from a different account, your Amazon Web Services account must be trusted by the
39
42
  * role. The trust relationship is defined in the role's trust policy when the role is
40
43
  * created. That trust policy states which accounts are allowed to delegate that access to
41
44
  * users in the account. </p>
42
45
  * <p>A user who wants to access a role in a different account must also have permissions that
43
46
  * are delegated from the user account administrator. The administrator must attach a policy
44
47
  * that allows the user to call <code>AssumeRole</code> for the ARN of the role in the other
45
- * account. If the user is in the same account as the role, then you can do either of the
48
+ * account.</p>
49
+ * <p>To allow a user to assume a role in the same account, you can do either of the
46
50
  * following:</p>
47
51
  * <ul>
48
52
  * <li>
49
- * <p>Attach a policy to the user (identical to the previous user in a different
50
- * account).</p>
53
+ * <p>Attach a policy to the user that allows the user to call
54
+ * <code>AssumeRole</code> (as long as the role's trust policy trusts the account).</p>
51
55
  * </li>
52
56
  * <li>
53
57
  * <p>Add the user as a principal directly in the role's trust policy.</p>
54
58
  * </li>
55
59
  * </ul>
56
- * <p>In this case, the trust policy acts as an IAM resource-based policy. Users in the same
57
- * account as the role do not need explicit permission to assume the role. For more
58
- * information about trust policies and resource-based policies, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html">IAM Policies</a> in
59
- * the <i>IAM User Guide</i>.</p>
60
+ * <p>You can do either because the role’s trust policy acts as an IAM resource-based
61
+ * policy. When a resource-based policy grants access to a principal in the same account, no
62
+ * additional identity-based policy is required. For more information about trust policies and
63
+ * resource-based policies, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html">IAM Policies</a> in the
64
+ * <i>IAM User Guide</i>.</p>
65
+ *
60
66
  * <p>
61
67
  * <b>Tags</b>
62
68
  * </p>
@@ -13,7 +13,7 @@ export interface AssumeRoleWithSAMLCommandOutput extends AssumeRoleWithSAMLRespo
13
13
  * credentials or configuration. For a comparison of <code>AssumeRoleWithSAML</code> with the
14
14
  * other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
15
15
  * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
16
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
16
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
17
17
  * <p>The temporary security credentials returned by this operation consist of an access key
18
18
  * ID, a secret access key, and a security token. Applications can use these temporary
19
19
  * security credentials to sign calls to Amazon Web Services services.</p>
@@ -35,15 +35,15 @@ export interface AssumeRoleWithSAMLCommandOutput extends AssumeRoleWithSAMLRespo
35
35
  * console URL. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html">Using IAM Roles</a> in the
36
36
  * <i>IAM User Guide</i>.</p>
37
37
  * <note>
38
- * <p>
39
- * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-role-chaining">Role chaining</a> limits your CLI or Amazon Web Services API
40
- * role session to a maximum of one hour. When you use the <code>AssumeRole</code> API
41
- * operation to assume a role, you can specify the duration of your role session with
42
- * the <code>DurationSeconds</code> parameter. You can specify a parameter value of up
43
- * to 43200 seconds (12 hours), depending on the maximum session duration setting for
44
- * your role. However, if you assume a role using role chaining and provide a
45
- * <code>DurationSeconds</code> parameter value greater than one hour, the
46
- * operation fails.</p>
38
+ * <p>
39
+ * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-role-chaining">Role chaining</a> limits your CLI or Amazon Web Services API role
40
+ * session to a maximum of one hour. When you use the <code>AssumeRole</code> API operation
41
+ * to assume a role, you can specify the duration of your role session with the
42
+ * <code>DurationSeconds</code> parameter. You can specify a parameter value of up to
43
+ * 43200 seconds (12 hours), depending on the maximum session duration setting for your
44
+ * role. However, if you assume a role using role chaining and provide a
45
+ * <code>DurationSeconds</code> parameter value greater than one hour, the operation
46
+ * fails.</p>
47
47
  * </note>
48
48
  * <p>
49
49
  * <b>Permissions</b>
@@ -95,9 +95,9 @@ export interface AssumeRoleWithSAMLCommandOutput extends AssumeRoleWithSAMLRespo
95
95
  * request are to the upper size limit.
96
96
  * </p>
97
97
  * </note>
98
- * <p>You can pass a session tag with the same key as a tag that is
99
- * attached to the role. When you do, session tags override the role's tags with the same
100
- * key.</p>
98
+ *
99
+ * <p>You can pass a session tag with the same key as a tag that is attached to the role. When
100
+ * you do, session tags override the role's tags with the same key.</p>
101
101
  * <p>An administrator must grant you the permissions necessary to pass session tags. The
102
102
  * administrator can also create granular permissions to allow you to pass only specific
103
103
  * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using Tags
@@ -29,7 +29,7 @@ export interface AssumeRoleWithWebIdentityCommandOutput extends AssumeRoleWithWe
29
29
  * <code>AssumeRoleWithWebIdentity</code> with the other API operations that produce
30
30
  * temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
31
31
  * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
32
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
32
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
33
33
  * <p>The temporary security credentials returned by this API consist of an access key ID, a
34
34
  * secret access key, and a security token. Applications can use these temporary security
35
35
  * credentials to sign calls to Amazon Web Services service API operations.</p>
@@ -87,9 +87,9 @@ export interface AssumeRoleWithWebIdentityCommandOutput extends AssumeRoleWithWe
87
87
  * request are to the upper size limit.
88
88
  * </p>
89
89
  * </note>
90
- * <p>You can pass a session tag with the same key as a tag that is
91
- * attached to the role. When you do, the session tag overrides the role tag with the same
92
- * key.</p>
90
+ *
91
+ * <p>You can pass a session tag with the same key as a tag that is attached to the role. When
92
+ * you do, the session tag overrides the role tag with the same key.</p>
93
93
  * <p>An administrator must grant you the permissions necessary to pass session tags. The
94
94
  * administrator can also create granular permissions to allow you to pass only specific
95
95
  * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using Tags
@@ -18,9 +18,9 @@ export interface DecodeAuthorizationMessageCommandOutput extends DecodeAuthoriza
18
18
  * documentation for an individual operation indicates whether that operation returns an
19
19
  * encoded message in addition to returning an HTTP code.</p>
20
20
  * </note>
21
- * <p>The message is encoded because the details of the authorization status can constitute
21
+ * <p>The message is encoded because the details of the authorization status can contain
22
22
  * privileged information that the user who requested the operation should not see. To decode
23
- * an authorization status message, a user must be granted permissions via an IAM policy to
23
+ * an authorization status message, a user must be granted permissions through an IAM <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html">policy</a> to
24
24
  * request the <code>DecodeAuthorizationMessage</code>
25
25
  * (<code>sts:DecodeAuthorizationMessage</code>) action. </p>
26
26
  * <p>The decoded message includes the following type of information:</p>
@@ -8,23 +8,23 @@ export interface GetAccessKeyInfoCommandOutput extends GetAccessKeyInfoResponse,
8
8
  }
9
9
  /**
10
10
  * <p>Returns the account identifier for the specified access key ID.</p>
11
- * <p>Access keys consist of two parts: an access key ID (for example,
12
- * <code>AKIAIOSFODNN7EXAMPLE</code>) and a secret access key (for example,
13
- * <code>wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY</code>). For more information about
14
- * access keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html">Managing Access Keys for IAM
15
- * Users</a> in the <i>IAM User Guide</i>.</p>
16
- * <p>When you pass an access key ID to this operation, it returns the ID of the Amazon Web Services
17
- * account to which the keys belong. Access key IDs beginning with <code>AKIA</code> are
18
- * long-term credentials for an IAM user or the Amazon Web Services account root user. Access key IDs
19
- * beginning with <code>ASIA</code> are temporary credentials that are created using STS
20
- * operations. If the account in the response belongs to you, you can sign in as the root
21
- * user and review your root user access keys. Then, you can pull a <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_getting-report.html">credentials report</a> to learn which IAM user owns the keys. To learn who
22
- * requested the temporary credentials for an <code>ASIA</code> access key, view the STS
23
- * events in your <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/cloudtrail-integration.html">CloudTrail logs</a> in the
24
- * <i>IAM User Guide</i>.</p>
25
- * <p>This operation does not indicate the state of the access key. The key might be active,
26
- * inactive, or deleted. Active keys might not have permissions to perform an operation.
27
- * Providing a deleted access key might return an error that the key doesn't exist.</p>
11
+ * <p>Access keys consist of two parts: an access key ID (for example,
12
+ * <code>AKIAIOSFODNN7EXAMPLE</code>) and a secret access key (for example,
13
+ * <code>wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY</code>). For more information about
14
+ * access keys, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html">Managing Access Keys for IAM
15
+ * Users</a> in the <i>IAM User Guide</i>.</p>
16
+ * <p>When you pass an access key ID to this operation, it returns the ID of the Amazon Web Services account
17
+ * to which the keys belong. Access key IDs beginning with <code>AKIA</code> are long-term
18
+ * credentials for an IAM user or the Amazon Web Services account root user. Access key IDs beginning with
19
+ * <code>ASIA</code> are temporary credentials that are created using STS operations. If
20
+ * the account in the response belongs to you, you can sign in as the root user and review
21
+ * your root user access keys. Then, you can pull a <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_getting-report.html">credentials report</a> to
22
+ * learn which IAM user owns the keys. To learn who requested the temporary credentials for
23
+ * an <code>ASIA</code> access key, view the STS events in your <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/cloudtrail-integration.html">CloudTrail logs</a> in the
24
+ * <i>IAM User Guide</i>.</p>
25
+ * <p>This operation does not indicate the state of the access key. The key might be active,
26
+ * inactive, or deleted. Active keys might not have permissions to perform an operation.
27
+ * Providing a deleted access key might return an error that the key doesn't exist.</p>
28
28
  * @example
29
29
  * Use a bare-bones client and the command you need to make an API call.
30
30
  * ```javascript
@@ -8,15 +8,15 @@ export interface GetCallerIdentityCommandOutput extends GetCallerIdentityRespons
8
8
  }
9
9
  /**
10
10
  * <p>Returns details about the IAM user or role whose credentials are used to call the
11
- * operation.</p>
12
- * <note>
11
+ * operation.</p>
12
+ * <note>
13
13
  * <p>No permissions are required to perform this operation. If an administrator adds a
14
- * policy to your IAM user or role that explicitly denies access to the
15
- * <code>sts:GetCallerIdentity</code> action, you can still perform this operation.
16
- * Permissions are not required because the same information is returned when an IAM
17
- * user or role is denied access. To view an example response, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_access-denied-delete-mfa">I Am Not Authorized to Perform: iam:DeleteVirtualMFADevice</a> in the
18
- * <i>IAM User Guide</i>.</p>
19
- * </note>
14
+ * policy to your IAM user or role that explicitly denies access to the
15
+ * <code>sts:GetCallerIdentity</code> action, you can still perform this operation.
16
+ * Permissions are not required because the same information is returned when an IAM user
17
+ * or role is denied access. To view an example response, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_access-denied-delete-mfa">I Am Not Authorized to Perform: iam:DeleteVirtualMFADevice</a> in the
18
+ * <i>IAM User Guide</i>.</p>
19
+ * </note>
20
20
  * @example
21
21
  * Use a bare-bones client and the command you need to make an API call.
22
22
  * ```javascript
@@ -16,7 +16,7 @@ export interface GetFederationTokenCommandOutput extends GetFederationTokenRespo
16
16
  * server-based application. For a comparison of <code>GetFederationToken</code> with the
17
17
  * other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting Temporary Security
18
18
  * Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
19
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
19
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
20
20
  * <note>
21
21
  * <p>You can create a mobile-based or browser-based app that can authenticate users using
22
22
  * a web identity provider like Login with Amazon, Facebook, Google, or an OpenID
@@ -35,8 +35,8 @@ export interface GetFederationTokenCommandOutput extends GetFederationTokenRespo
35
35
  * </p>
36
36
  * <p>The temporary credentials are valid for the specified duration, from 900 seconds (15
37
37
  * minutes) up to a maximum of 129,600 seconds (36 hours). The default session duration is
38
- * 43,200 seconds (12 hours). Temporary credentials that are obtained by using Amazon Web Services account
39
- * root user credentials have a maximum duration of 3,600 seconds (1 hour).</p>
38
+ * 43,200 seconds (12 hours). Temporary credentials obtained by using the Amazon Web Services account root
39
+ * user credentials have a maximum duration of 3,600 seconds (1 hour).</p>
40
40
  * <p>
41
41
  * <b>Permissions</b>
42
42
  * </p>
@@ -74,78 +74,25 @@ export interface GetFederationTokenCommandOutput extends GetFederationTokenRespo
74
74
  * <p>(Optional) You can pass tag key-value pairs to your session. These are called session
75
75
  * tags. For more information about session tags, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Passing Session Tags in STS</a> in the
76
76
  * <i>IAM User Guide</i>.</p>
77
- * <note>
78
- * <p>You can create a mobile-based or browser-based app that can authenticate users
79
- * using a web identity provider like Login with Amazon, Facebook, Google, or an OpenID
80
- * Connect-compatible identity provider. In this case, we recommend that you use <a href="http://aws.amazon.com/cognito/">Amazon Cognito</a> or
81
- * <code>AssumeRoleWithWebIdentity</code>. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity">Federation Through a Web-based Identity Provider</a> in the
82
- * <i>IAM User Guide</i>.</p>
83
- * </note>
84
- * <p>You can also call <code>GetFederationToken</code> using the security credentials of an
85
- * Amazon Web Services account root user, but we do not recommend it. Instead, we recommend that you
86
- * create an IAM user for the purpose of the proxy application. Then attach a policy to
87
- * the IAM user that limits federated users to only the actions and resources that they
88
- * need to access. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html">IAM Best Practices</a> in the
89
- * <i>IAM User Guide</i>. </p>
90
- * <p>
91
- * <b>Session duration</b>
92
- * </p>
93
- * <p>The temporary credentials are valid for the specified duration, from 900 seconds (15
94
- * minutes) up to a maximum of 129,600 seconds (36 hours). The default session duration is
95
- * 43,200 seconds (12 hours). Temporary credentials that are obtained by using Amazon Web Services
96
- * account root user credentials have a maximum duration of 3,600 seconds (1 hour).</p>
97
- * <p>
98
- * <b>Permissions</b>
99
- * </p>
100
- * <p>You can use the temporary credentials created by <code>GetFederationToken</code> in
101
- * any Amazon Web Services service except the following:</p>
102
- * <ul>
103
- * <li>
104
- * <p>You cannot call any IAM operations using the CLI or the Amazon Web Services API.
105
- * </p>
106
- * </li>
107
- * <li>
108
- * <p>You cannot call any STS operations except
109
- * <code>GetCallerIdentity</code>.</p>
110
- * </li>
111
- * </ul>
112
- * <p>You must pass an inline or managed <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">session policy</a> to
113
- * this operation. You can pass a single JSON policy document to use as an inline session
114
- * policy. You can also specify up to 10 managed policies to use as managed session
115
- * policies. The plain text that you use for both inline and managed session policies can't
116
- * exceed 2,048 characters.</p>
117
- * <p>Though the session policy parameters are optional, if you do not pass a policy, then
118
- * the resulting federated user session has no permissions. When you pass session policies,
119
- * the session permissions are the intersection of the IAM user policies and the session
120
- * policies that you pass. This gives you a way to further restrict the permissions for a
121
- * federated user. You cannot use session policies to grant more permissions than those
122
- * that are defined in the permissions policy of the IAM user. For more information, see
123
- * <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session Policies</a>
124
- * in the <i>IAM User Guide</i>. For information about using
125
- * <code>GetFederationToken</code> to create temporary security credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getfederationtoken">GetFederationToken—Federation Through a Custom Identity Broker</a>. </p>
126
- * <p>You can use the credentials to access a resource that has a resource-based policy. If
127
- * that policy specifically references the federated user session in the
128
- * <code>Principal</code> element of the policy, the session has the permissions
129
- * allowed by the policy. These permissions are granted in addition to the permissions
130
- * granted by the session policies.</p>
131
- * <p>
132
- * <b>Tags</b>
133
- * </p>
134
- * <p>(Optional) You can pass tag key-value pairs to your session. These are called session
135
- * tags. For more information about session tags, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Passing Session Tags in STS</a> in
136
- * the <i>IAM User Guide</i>.</p>
137
- * <p>An administrator must grant you the permissions necessary to pass session tags. The
138
- * administrator can also create granular permissions to allow you to pass only specific
139
- * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using
140
- * Tags for Attribute-Based Access Control</a> in the
141
- * <i>IAM User Guide</i>.</p>
142
- * <p>Tag key–value pairs are not case sensitive, but case is preserved. This means that you
143
- * cannot have separate <code>Department</code> and <code>department</code> tag keys.
144
- * Assume that the user that you are federating has the
145
- * <code>Department</code>=<code>Marketing</code> tag and you pass the
146
- * <code>department</code>=<code>engineering</code> session tag.
147
- * <code>Department</code> and <code>department</code> are not saved as separate tags,
148
- * and the session tag passed in the request takes precedence over the user tag.</p>
77
+ * <note>
78
+ * <p>You can create a mobile-based or browser-based app that can authenticate users using
79
+ * a web identity provider like Login with Amazon, Facebook, Google, or an OpenID
80
+ * Connect-compatible identity provider. In this case, we recommend that you use <a href="http://aws.amazon.com/cognito/">Amazon Cognito</a> or
81
+ * <code>AssumeRoleWithWebIdentity</code>. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity">Federation Through a Web-based Identity Provider</a> in the
82
+ * <i>IAM User Guide</i>.</p>
83
+ * </note>
84
+ * <p>An administrator must grant you the permissions necessary to pass session tags. The
85
+ * administrator can also create granular permissions to allow you to pass only specific
86
+ * session tags. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html">Tutorial: Using Tags
87
+ * for Attribute-Based Access Control</a> in the
88
+ * <i>IAM User Guide</i>.</p>
89
+ * <p>Tag key–value pairs are not case sensitive, but case is preserved. This means that you
90
+ * cannot have separate <code>Department</code> and <code>department</code> tag keys. Assume
91
+ * that the user that you are federating has the
92
+ * <code>Department</code>=<code>Marketing</code> tag and you pass the
93
+ * <code>department</code>=<code>engineering</code> session tag. <code>Department</code>
94
+ * and <code>department</code> are not saved as separate tags, and the session tag passed in
95
+ * the request takes precedence over the user tag.</p>
149
96
  * @example
150
97
  * Use a bare-bones client and the command you need to make an API call.
151
98
  * ```javascript
@@ -18,7 +18,7 @@ export interface GetSessionTokenCommandOutput extends GetSessionTokenResponse, _
18
18
  * the API returns an access denied error. For a comparison of <code>GetSessionToken</code>
19
19
  * with the other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting
20
20
  * Temporary Security Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing the
21
- * STS API operations</a> in the <i>IAM User Guide</i>.</p>
21
+ * Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.</p>
22
22
  * <p>
23
23
  * <b>Session Duration</b>
24
24
  * </p>
@@ -43,7 +43,7 @@ export declare namespace PolicyDescriptorType {
43
43
  /**
44
44
  * <p>You can pass custom key-value pair attributes when you assume a role or federate a user.
45
45
  * These are called session tags. You can then use the session tags to control access to
46
- * resources. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Tagging STS Sessions</a> in the
46
+ * resources. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Tagging Amazon Web Services STS Sessions</a> in the
47
47
  * <i>IAM User Guide</i>.</p>
48
48
  */
49
49
  export interface Tag {
@@ -93,6 +93,7 @@ export interface AssumeRoleRequest {
93
93
  * plaintext that you use for both inline and managed session policies can't exceed 2,048
94
94
  * characters. For more information about ARNs, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">Amazon Resource Names (ARNs) and Amazon Web Services
95
95
  * Service Namespaces</a> in the Amazon Web Services General Reference.</p>
96
+ *
96
97
  * <note>
97
98
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
98
99
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -127,6 +128,7 @@ export interface AssumeRoleRequest {
127
128
  * character to the end of the valid character list (\u0020 through \u00FF). It can also
128
129
  * include the tab (\u0009), linefeed (\u000A), and carriage return (\u000D)
129
130
  * characters.</p>
131
+ *
130
132
  * <note>
131
133
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
132
134
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -138,13 +140,19 @@ export interface AssumeRoleRequest {
138
140
  */
139
141
  Policy?: string;
140
142
  /**
141
- * <p>The duration, in seconds, of the role session. The value specified can can range from
142
- * 900 seconds (15 minutes) up to the maximum session duration that is set for the role. The
143
- * maximum session duration setting can have a value from 1 hour to 12 hours. If you specify a
144
- * value higher than this setting or the administrator setting (whichever is lower), the
145
- * operation fails. For example, if you specify a session duration of 12 hours, but your
146
- * administrator set the maximum session duration to 6 hours, your operation fails. To learn
147
- * how to view the maximum value for your role, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session">View the
143
+ * <p>The duration, in seconds, of the role session. The value specified can range from 900
144
+ * seconds (15 minutes) up to the maximum session duration set for the role. The maximum
145
+ * session duration setting can have a value from 1 hour to 12 hours. If you specify a value
146
+ * higher than this setting or the administrator setting (whichever is lower), the operation
147
+ * fails. For example, if you specify a session duration of 12 hours, but your administrator
148
+ * set the maximum session duration to 6 hours, your operation fails. </p>
149
+ * <p>Role chaining limits your Amazon Web Services CLI or Amazon Web Services API role session to a maximum of one hour.
150
+ * When you use the <code>AssumeRole</code> API operation to assume a role, you can specify
151
+ * the duration of your role session with the <code>DurationSeconds</code> parameter. You can
152
+ * specify a parameter value of up to 43200 seconds (12 hours), depending on the maximum
153
+ * session duration setting for your role. However, if you assume a role using role chaining
154
+ * and provide a <code>DurationSeconds</code> parameter value greater than one hour, the
155
+ * operation fails. To learn how to view the maximum value for your role, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session">View the
148
156
  * Maximum Session Duration Setting for a Role</a> in the
149
157
  * <i>IAM User Guide</i>.</p>
150
158
  * <p>By default, the value is set to <code>3600</code> seconds. </p>
@@ -154,14 +162,14 @@ export interface AssumeRoleRequest {
154
162
  * federation endpoint for a console sign-in token takes a <code>SessionDuration</code>
155
163
  * parameter that specifies the maximum length of the console session. For more
156
164
  * information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html">Creating a URL
157
- * that Enables Federated Users to Access the Management Console</a> in the
165
+ * that Enables Federated Users to Access the Amazon Web Services Management Console</a> in the
158
166
  * <i>IAM User Guide</i>.</p>
159
167
  * </note>
160
168
  */
161
169
  DurationSeconds?: number;
162
170
  /**
163
171
  * <p>A list of session tags that you want to pass. Each session tag consists of a key name
164
- * and an associated value. For more information about session tags, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Tagging STS
172
+ * and an associated value. For more information about session tags, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Tagging Amazon Web Services STS
165
173
  * Sessions</a> in the <i>IAM User Guide</i>.</p>
166
174
  * <p>This parameter is optional. You can pass up to 50 session tags. The plaintext session
167
175
  * tag keys can’t exceed 128 characters, and the values can’t exceed 256 characters. For these
@@ -176,8 +184,9 @@ export interface AssumeRoleRequest {
176
184
  * request are to the upper size limit.
177
185
  * </p>
178
186
  * </note>
179
- * <p>You can pass a session tag with the same key as a tag that is already
180
- * attached to the role. When you do, session tags override a role tag with the same key. </p>
187
+ *
188
+ * <p>You can pass a session tag with the same key as a tag that is already attached to the
189
+ * role. When you do, session tags override a role tag with the same key. </p>
181
190
  * <p>Tag key–value pairs are not case sensitive, but case is preserved. This means that you
182
191
  * cannot have separate <code>Department</code> and <code>department</code> tag keys. Assume
183
192
  * that the role has the <code>Department</code>=<code>Marketing</code> tag and you pass the
@@ -253,8 +262,7 @@ export interface AssumeRoleRequest {
253
262
  * <p>The regex used to validate this parameter is a string of characters consisting of upper-
254
263
  * and lower-case alphanumeric characters with no spaces. You can also include underscores or
255
264
  * any of the following characters: =,.@-. You cannot use a value that begins with the text
256
- * <code>aws:</code>. This prefix is reserved for Amazon Web Services internal
257
- * use.</p>
265
+ * <code>aws:</code>. This prefix is reserved for Amazon Web Services internal use.</p>
258
266
  */
259
267
  SourceIdentity?: string;
260
268
  }
@@ -300,6 +308,7 @@ export interface AssumeRoleResponse {
300
308
  /**
301
309
  * <p>The temporary security credentials, which include an access key ID, a secret access key,
302
310
  * and a security (or session) token.</p>
311
+ *
303
312
  * <note>
304
313
  * <p>The size of the security token that STS API operations return is not fixed. We
305
314
  * strongly recommend that you make no assumptions about the maximum size.</p>
@@ -381,7 +390,7 @@ export declare namespace MalformedPolicyDocumentException {
381
390
  * tags are to the upper size limit. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html">Passing Session Tags in STS</a> in
382
391
  * the <i>IAM User Guide</i>.</p>
383
392
  * <p>You could receive this error even though you meet other defined session policy and
384
- * session tag limits. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html">IAM and STS Entity
393
+ * session tag limits. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-quotas.html#reference_iam-limits-entity-length">IAM and STS Entity
385
394
  * Character Limits</a> in the <i>IAM User Guide</i>.</p>
386
395
  */
387
396
  export interface PackedPolicyTooLargeException extends __SmithyException, $MetadataBearer {
@@ -436,6 +445,7 @@ export interface AssumeRoleWithSAMLRequest {
436
445
  * plaintext that you use for both inline and managed session policies can't exceed 2,048
437
446
  * characters. For more information about ARNs, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">Amazon Resource Names (ARNs) and Amazon Web Services
438
447
  * Service Namespaces</a> in the Amazon Web Services General Reference.</p>
448
+ *
439
449
  * <note>
440
450
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
441
451
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -470,6 +480,7 @@ export interface AssumeRoleWithSAMLRequest {
470
480
  * character to the end of the valid character list (\u0020 through \u00FF). It can also
471
481
  * include the tab (\u0009), linefeed (\u000A), and carriage return (\u000D)
472
482
  * characters.</p>
483
+ *
473
484
  * <note>
474
485
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
475
486
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -499,7 +510,7 @@ export interface AssumeRoleWithSAMLRequest {
499
510
  * federation endpoint for a console sign-in token takes a <code>SessionDuration</code>
500
511
  * parameter that specifies the maximum length of the console session. For more
501
512
  * information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html">Creating a URL
502
- * that Enables Federated Users to Access the Management Console</a> in the
513
+ * that Enables Federated Users to Access the Amazon Web Services Management Console</a> in the
503
514
  * <i>IAM User Guide</i>.</p>
504
515
  * </note>
505
516
  */
@@ -519,6 +530,7 @@ export interface AssumeRoleWithSAMLResponse {
519
530
  /**
520
531
  * <p>The temporary security credentials, which include an access key ID, a secret access key,
521
532
  * and a security (or session) token.</p>
533
+ *
522
534
  * <note>
523
535
  * <p>The size of the security token that STS API operations return is not fixed. We
524
536
  * strongly recommend that you make no assumptions about the maximum size.</p>
@@ -678,6 +690,7 @@ export interface AssumeRoleWithWebIdentityRequest {
678
690
  * plaintext that you use for both inline and managed session policies can't exceed 2,048
679
691
  * characters. For more information about ARNs, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">Amazon Resource Names (ARNs) and Amazon Web Services
680
692
  * Service Namespaces</a> in the Amazon Web Services General Reference.</p>
693
+ *
681
694
  * <note>
682
695
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
683
696
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -712,6 +725,7 @@ export interface AssumeRoleWithWebIdentityRequest {
712
725
  * character to the end of the valid character list (\u0020 through \u00FF). It can also
713
726
  * include the tab (\u0009), linefeed (\u000A), and carriage return (\u000D)
714
727
  * characters.</p>
728
+ *
715
729
  * <note>
716
730
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
717
731
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -738,7 +752,7 @@ export interface AssumeRoleWithWebIdentityRequest {
738
752
  * federation endpoint for a console sign-in token takes a <code>SessionDuration</code>
739
753
  * parameter that specifies the maximum length of the console session. For more
740
754
  * information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html">Creating a URL
741
- * that Enables Federated Users to Access the Management Console</a> in the
755
+ * that Enables Federated Users to Access the Amazon Web Services Management Console</a> in the
742
756
  * <i>IAM User Guide</i>.</p>
743
757
  * </note>
744
758
  */
@@ -758,6 +772,7 @@ export interface AssumeRoleWithWebIdentityResponse {
758
772
  /**
759
773
  * <p>The temporary security credentials, which include an access key ID, a secret access key,
760
774
  * and a security token.</p>
775
+ *
761
776
  * <note>
762
777
  * <p>The size of the security token that STS API operations return is not fixed. We
763
778
  * strongly recommend that you make no assumptions about the maximum size.</p>
@@ -863,7 +878,7 @@ export declare namespace DecodeAuthorizationMessageRequest {
863
878
  */
864
879
  export interface DecodeAuthorizationMessageResponse {
865
880
  /**
866
- * <p>An XML document that contains the decoded message.</p>
881
+ * <p>The API returns a response with the decoded message.</p>
867
882
  */
868
883
  DecodedMessage?: string;
869
884
  }
@@ -892,8 +907,8 @@ export declare namespace InvalidAuthorizationMessageException {
892
907
  export interface GetAccessKeyInfoRequest {
893
908
  /**
894
909
  * <p>The identifier of an access key.</p>
895
- * <p>This parameter allows (through its regex pattern) a string of characters that can
896
- * consist of any upper- or lowercase letter or digit.</p>
910
+ * <p>This parameter allows (through its regex pattern) a string of characters that can
911
+ * consist of any upper- or lowercase letter or digit.</p>
897
912
  */
898
913
  AccessKeyId: string | undefined;
899
914
  }
@@ -985,6 +1000,7 @@ export interface GetFederationTokenRequest {
985
1000
  * character to the end of the valid character list (\u0020 through \u00FF). It can also
986
1001
  * include the tab (\u0009), linefeed (\u000A), and carriage return (\u000D)
987
1002
  * characters.</p>
1003
+ *
988
1004
  * <note>
989
1005
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
990
1006
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -1005,7 +1021,8 @@ export interface GetFederationTokenRequest {
1005
1021
  * The plaintext that you use for both inline and managed session policies can't exceed 2,048
1006
1022
  * characters. You can provide up to 10 managed policy ARNs. For more information about ARNs,
1007
1023
  * see <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">Amazon
1008
- * Resource Names (ARNs) and Amazon Web Services Service Namespaces</a> in the Amazon Web Services General Reference.</p>
1024
+ * Resource Names (ARNs) and Amazon Web Services Service Namespaces</a> in the
1025
+ * Amazon Web Services General Reference.</p>
1009
1026
  * <p>This parameter is optional. However, if you do not pass any session policies, then the
1010
1027
  * resulting federated user session has no permissions.</p>
1011
1028
  * <p>When you pass session policies, the session permissions are the intersection of the
@@ -1019,6 +1036,7 @@ export interface GetFederationTokenRequest {
1019
1036
  * <code>Principal</code> element of the policy, the session has the permissions allowed by
1020
1037
  * the policy. These permissions are granted in addition to the permissions that are granted
1021
1038
  * by the session policies.</p>
1039
+ *
1022
1040
  * <note>
1023
1041
  * <p>An Amazon Web Services conversion compresses the passed session policies and session tags into a
1024
1042
  * packed binary format that has a separate limit. Your request can fail for this limit
@@ -1055,9 +1073,9 @@ export interface GetFederationTokenRequest {
1055
1073
  * request are to the upper size limit.
1056
1074
  * </p>
1057
1075
  * </note>
1058
- * <p>You can pass a session tag with the same key as a tag that is already
1059
- * attached to the user you are federating. When you do, session tags override a user tag with
1060
- * the same key. </p>
1076
+ *
1077
+ * <p>You can pass a session tag with the same key as a tag that is already attached to the
1078
+ * user you are federating. When you do, session tags override a user tag with the same key. </p>
1061
1079
  * <p>Tag key–value pairs are not case sensitive, but case is preserved. This means that you
1062
1080
  * cannot have separate <code>Department</code> and <code>department</code> tag keys. Assume
1063
1081
  * that the role has the <code>Department</code>=<code>Marketing</code> tag and you pass the
@@ -1103,6 +1121,7 @@ export interface GetFederationTokenResponse {
1103
1121
  /**
1104
1122
  * <p>The temporary security credentials, which include an access key ID, a secret access key,
1105
1123
  * and a security (or session) token.</p>
1124
+ *
1106
1125
  * <note>
1107
1126
  * <p>The size of the security token that STS API operations return is not fixed. We
1108
1127
  * strongly recommend that you make no assumptions about the maximum size.</p>
@@ -1131,34 +1150,34 @@ export declare namespace GetFederationTokenResponse {
1131
1150
  }
1132
1151
  export interface GetSessionTokenRequest {
1133
1152
  /**
1134
- * <p>The duration, in seconds, that the credentials should remain valid. Acceptable
1135
- * durations for IAM user sessions range from 900 seconds (15 minutes) to 129,600 seconds
1136
- * (36 hours), with 43,200 seconds (12 hours) as the default. Sessions for Amazon Web Services account
1137
- * owners are restricted to a maximum of 3,600 seconds (one hour). If the duration is
1138
- * longer than one hour, the session for Amazon Web Services account owners defaults to one hour.</p>
1153
+ * <p>The duration, in seconds, that the credentials should remain valid. Acceptable durations
1154
+ * for IAM user sessions range from 900 seconds (15 minutes) to 129,600 seconds (36 hours),
1155
+ * with 43,200 seconds (12 hours) as the default. Sessions for Amazon Web Services account owners are
1156
+ * restricted to a maximum of 3,600 seconds (one hour). If the duration is longer than one
1157
+ * hour, the session for Amazon Web Services account owners defaults to one hour.</p>
1139
1158
  */
1140
1159
  DurationSeconds?: number;
1141
1160
  /**
1142
1161
  * <p>The identification number of the MFA device that is associated with the IAM user who
1143
- * is making the <code>GetSessionToken</code> call. Specify this value if the IAM user
1144
- * has a policy that requires MFA authentication. The value is either the serial number for
1145
- * a hardware device (such as <code>GAHT12345678</code>) or an Amazon Resource Name (ARN)
1146
- * for a virtual device (such as <code>arn:aws:iam::123456789012:mfa/user</code>). You can
1147
- * find the device for an IAM user by going to the Management Console and viewing the user's
1148
- * security credentials. </p>
1149
- * <p>The regex used to validate this parameter is a string of
1162
+ * is making the <code>GetSessionToken</code> call. Specify this value if the IAM user has a
1163
+ * policy that requires MFA authentication. The value is either the serial number for a
1164
+ * hardware device (such as <code>GAHT12345678</code>) or an Amazon Resource Name (ARN) for a
1165
+ * virtual device (such as <code>arn:aws:iam::123456789012:mfa/user</code>). You can find the
1166
+ * device for an IAM user by going to the Amazon Web Services Management Console and viewing the user's security
1167
+ * credentials. </p>
1168
+ * <p>The regex used to validate this parameter is a string of
1150
1169
  * characters consisting of upper- and lower-case alphanumeric characters with no spaces.
1151
1170
  * You can also include underscores or any of the following characters: =,.@:/-</p>
1152
1171
  */
1153
1172
  SerialNumber?: string;
1154
1173
  /**
1155
1174
  * <p>The value provided by the MFA device, if MFA is required. If any policy requires the
1156
- * IAM user to submit an MFA code, specify this value. If MFA authentication is required,
1157
- * the user must provide a code when requesting a set of temporary security credentials. A
1158
- * user who fails to provide the code receives an "access denied" response when requesting
1159
- * resources that require MFA authentication.</p>
1160
- * <p>The format for this parameter, as described by its regex pattern, is a sequence of six
1161
- * numeric digits.</p>
1175
+ * IAM user to submit an MFA code, specify this value. If MFA authentication is required,
1176
+ * the user must provide a code when requesting a set of temporary security credentials. A
1177
+ * user who fails to provide the code receives an "access denied" response when requesting
1178
+ * resources that require MFA authentication.</p>
1179
+ * <p>The format for this parameter, as described by its regex pattern, is a sequence of six
1180
+ * numeric digits.</p>
1162
1181
  */
1163
1182
  TokenCode?: string;
1164
1183
  }
@@ -1174,8 +1193,8 @@ export declare namespace GetSessionTokenRequest {
1174
1193
  */
1175
1194
  export interface GetSessionTokenResponse {
1176
1195
  /**
1177
- * <p>The temporary security credentials, which include an access key ID, a secret access
1178
- * key, and a security (or session) token.</p>
1196
+ * <p>The temporary security credentials, which include an access key ID, a secret access key,
1197
+ * and a security (or session) token.</p>
1179
1198
  *
1180
1199
  * <note>
1181
1200
  * <p>The size of the security token that STS API operations return is not fixed. We
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-sts",
3
3
  "description": "AWS SDK for JavaScript Sts Client for Node.js, Browser and React Native",
4
- "version": "3.42.0",
4
+ "version": "3.43.0",
5
5
  "scripts": {
6
6
  "build": "yarn build:cjs && yarn build:es && yarn build:types",
7
7
  "build:cjs": "tsc -p tsconfig.json",