You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "The following command retrieves a set of short-term credentials you can use to unlock an S3 bucket for a member account by removing the bucket policy.",
/// secret access key, and a security token. Typically, you use <c>AssumeRole</c> within
37
37
/// your account or for cross-account access. For a comparison of <c>AssumeRole</c> with
38
38
/// other API operations that produce temporary credentials, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html">Requesting
39
-
/// Temporary Security Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing
40
-
/// the Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.
39
+
/// Temporary Security Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_sts-comparison.html">Compare
40
+
/// STS credentials</a> in the <i>IAM User Guide</i>.
/// to this operation returns new temporary credentials. The resulting session's permissions
61
-
/// are the intersection of the role's identity-based policy and the session policies.
62
-
/// You can use the role's temporary credentials in subsequent Amazon Web Services API
63
-
/// calls to access resources in the account that owns the role. You cannot use session
64
-
/// policies to grant more permissions than those allowed by the identity-based policy
65
-
/// of the role that is being assumed. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session
55
+
/// (Optional) You can pass inline or managed session policies to this operation. You
56
+
/// can pass a single JSON policy document to use as an inline session policy. You can
57
+
/// also specify up to 10 managed policy Amazon Resource Names (ARNs) to use as managed
58
+
/// session policies. The plaintext that you use for both inline and managed session policies
59
+
/// can't exceed 2,048 characters. Passing policies to this operation returns new temporary
60
+
/// credentials. The resulting session's permissions are the intersection of the role's
61
+
/// identity-based policy and the session policies. You can use the role's temporary credentials
62
+
/// in subsequent Amazon Web Services API calls to access resources in the account that
63
+
/// owns the role. You cannot use session policies to grant more permissions than those
64
+
/// allowed by the identity-based policy of the role that is being assumed. For more information,
65
+
/// see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session
66
66
/// Policies</a> in the <i>IAM User Guide</i>.
67
67
/// </para>
68
68
///
@@ -196,8 +196,8 @@ public partial class AssumeRoleRequest : AmazonSecurityTokenServiceRequest
196
196
/// on the maximum session duration setting for your role. However, if you assume a role
197
197
/// using role chaining and provide a <c>DurationSeconds</c> parameter value greater than
198
198
/// one hour, the operation fails. To learn how to view the maximum value for your role,
199
-
/// see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session">View
200
-
/// the Maximum Session Duration Setting for a Role</a> in the <i>IAM User Guide</i>.
199
+
/// see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_update-role-settings.html#id_roles_update-session-duration">Update
/// The <c>PackedPolicySize</c> response element indicates by percentage how close the
294
294
/// policies and tags for your request are to the upper size limit.
295
295
/// </para>
296
-
/// </note>
296
+
/// </note>
297
+
/// <para>
298
+
/// For more information about role session permissions, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session
299
+
/// policies</a>.
300
+
/// </para>
297
301
/// </summary>
298
302
[AWSProperty(Min=1)]
299
303
publicstringPolicy
@@ -419,6 +423,14 @@ internal bool IsSetRoleArn()
419
423
/// </para>
420
424
///
421
425
/// <para>
426
+
/// For security purposes, administrators can view this field in <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/cloudtrail-integration.html#cloudtrail-integration_signin-tempcreds">CloudTrail
427
+
/// logs</a> to help identify who performed an action in Amazon Web Services. Your administrator
428
+
/// might require that you specify your user name as the session name when you assume
429
+
/// the role. For more information, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_iam-condition-keys.html#ck_rolesessionname">
430
+
/// <c>sts:RoleSessionName</c> </a>.
431
+
/// </para>
432
+
///
433
+
/// <para>
422
434
/// The regex used to validate this parameter is a string of characters consisting of
423
435
/// upper- and lower-case alphanumeric characters with no spaces. You can also include
424
436
/// underscores or any of the following characters: =,.@-
/// The source identity specified by the principal that is calling the <c>AssumeRole</c>
473
-
/// operation.
485
+
/// operation. The source identity value persists across <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html#iam-term-role-chaining">chained
486
+
/// role</a> sessions.
474
487
/// </para>
475
488
///
476
489
/// <para>
477
490
/// You can require users to specify a source identity when they assume a role. You do
478
-
/// this by using the <c>sts:SourceIdentity</c> condition key in a role trust policy.
479
-
/// You can use source identity information in CloudTrail logs to determine who took actions
480
-
/// with a role. You can use the <c>aws:SourceIdentity</c> condition key to further control
481
-
/// access to Amazon Web Services resources based on the value of source identity. For
482
-
/// more information about using source identity, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html">Monitor
491
+
/// this by using the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceidentity">
492
+
/// <c>sts:SourceIdentity</c> </a> condition key in a role trust policy. You can use source
493
+
/// identity information in CloudTrail logs to determine who took actions with a role.
494
+
/// You can use the <c>aws:SourceIdentity</c> condition key to further control access
495
+
/// to Amazon Web Services resources based on the value of source identity. For more information
496
+
/// about using source identity, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html">Monitor
483
497
/// and control actions taken with assumed roles</a> in the <i>IAM User Guide</i>.
/// an enterprise identity store or directory to role-based Amazon Web Services access
37
37
/// without user-specific credentials or configuration. For a comparison of <c>AssumeRoleWithSAML</c>
38
38
/// 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
39
-
/// Temporary Security Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison">Comparing
40
-
/// the Amazon Web Services STS API operations</a> in the <i>IAM User Guide</i>.
39
+
/// Temporary Security Credentials</a> and <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_sts-comparison.html">Compare
40
+
/// STS credentials</a> in the <i>IAM User Guide</i>.
/// character to the end of the valid character list (\u0020 through \u00FF). It can also
276
276
/// include the tab (\u0009), linefeed (\u000A), and carriage return (\u000D) characters.
277
277
/// </para>
278
+
///
279
+
/// <para>
280
+
/// For more information about role session permissions, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session">Session
281
+
/// policies</a>.
282
+
/// </para>
278
283
/// <note>
279
284
/// <para>
280
285
/// An Amazon Web Services conversion compresses the passed inline session policy, managed
/// The value in the <c>SourceIdentity</c> attribute in the SAML assertion.
197
+
/// The value in the <c>SourceIdentity</c> attribute in the SAML assertion. The source
198
+
/// identity value persists across <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html#iam-term-role-chaining">chained
199
+
/// role</a> sessions.
198
200
/// </para>
199
201
///
200
202
/// <para>
201
203
/// You can require users to set a source identity value when they assume a role. You
202
204
/// do this by using the <c>sts:SourceIdentity</c> condition key in a role trust policy.
203
205
/// That way, actions that are taken with the role are associated with that user. After
204
206
/// the source identity is set, the value cannot be changed. It is present in the request
205
-
/// for all actions that are taken by the role and persists across <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts#iam-term-role-chaining">chained
207
+
/// for all actions that are taken by the role and persists across <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html#id_roles_terms-and-concepts">chained
206
208
/// role</a> sessions. You can configure your SAML identity provider to use an attribute
207
209
/// associated with your users, like user name or email, as the source identity when calling
208
210
/// <c>AssumeRoleWithSAML</c>. You do this by adding an attribute to the SAML assertion.
0 commit comments