aws-sdk-core 3.39.0 → 3.54.2

data/lib/aws-sdk-sts/client.rb

@@ -23,6 +23,7 @@ require 'aws-sdk-core/plugins/idempotency_token.rb'
 require 'aws-sdk-core/plugins/jsonvalue_converter.rb'
 require 'aws-sdk-core/plugins/client_metrics_plugin.rb'
 require 'aws-sdk-core/plugins/client_metrics_send_plugin.rb'
+require 'aws-sdk-core/plugins/transfer_encoding.rb'
 require 'aws-sdk-core/plugins/signature_v4.rb'
 require 'aws-sdk-core/plugins/protocols/query.rb'
 
@@ -55,6 +56,7 @@ module Aws::STS
     add_plugin(Aws::Plugins::JsonvalueConverter)
     add_plugin(Aws::Plugins::ClientMetricsPlugin)
     add_plugin(Aws::Plugins::ClientMetricsSendPlugin)
+    add_plugin(Aws::Plugins::TransferEncoding)
     add_plugin(Aws::Plugins::SignatureV4)
     add_plugin(Aws::Plugins::Protocols::Query)
 
@@ -199,46 +201,77 @@ module Aws::STS
     #     When `true`, request parameters are validated before
     #     sending the request.
     #
+    #   @option options [URI::HTTP,String] :http_proxy A proxy to send
+    #     requests through.  Formatted like 'http://proxy.com:123'.
+    #
+    #   @option options [Float] :http_open_timeout (15) The number of
+    #     seconds to wait when opening a HTTP session before rasing a
+    #     `Timeout::Error`.
+    #
+    #   @option options [Integer] :http_read_timeout (60) The default
+    #     number of seconds to wait for response data.  This value can
+    #     safely be set
+    #     per-request on the session yeidled by {#session_for}.
+    #
+    #   @option options [Float] :http_idle_timeout (5) The number of
+    #     seconds a connection is allowed to sit idble before it is
+    #     considered stale.  Stale connections are closed and removed
+    #     from the pool before making a request.
+    #
+    #   @option options [Float] :http_continue_timeout (1) The number of
+    #     seconds to wait for a 100-continue response before sending the
+    #     request body.  This option has no effect unless the request has
+    #     "Expect" header set to "100-continue".  Defaults to `nil` which
+    #     disables this behaviour.  This value can safely be set per
+    #     request on the session yeidled by {#session_for}.
+    #
+    #   @option options [Boolean] :http_wire_trace (false) When `true`,
+    #     HTTP debug output will be sent to the `:logger`.
+    #
+    #   @option options [Boolean] :ssl_verify_peer (true) When `true`,
+    #     SSL peer certificates are verified when establishing a
+    #     connection.
+    #
+    #   @option options [String] :ssl_ca_bundle Full path to the SSL
+    #     certificate authority bundle file that should be used when
+    #     verifying peer certificates.  If you do not pass
+    #     `:ssl_ca_bundle` or `:ssl_ca_directory` the the system default
+    #     will be used if available.
+    #
+    #   @option options [String] :ssl_ca_directory Full path of the
+    #     directory that contains the unbundled SSL certificate
+    #     authority files for verifying peer certificates.  If you do
+    #     not pass `:ssl_ca_bundle` or `:ssl_ca_directory` the the
+    #     system default will be used if available.
+    #
     def initialize(*args)
       super
     end
 
     # @!group API Operations
 
-    # Returns a set of temporary security credentials (consisting of an
-    # access key ID, a secret access key, and a security token) that you can
-    # use to access AWS resources that you might not normally have access
-    # to. Typically, you use `AssumeRole` for cross-account access or
-    # federation. For a comparison of `AssumeRole` with the other APIs that
-    # produce temporary credentials, see [Requesting Temporary Security
-    # Credentials][1] and [Comparing the AWS STS APIs][2] in the *IAM User
-    # Guide*.
-    #
-    # **Important:** You cannot call `AssumeRole` by using AWS root account
-    # credentials; access is denied. You must use credentials for an IAM
-    # user or an IAM role to call `AssumeRole`.
+    # Returns a set of temporary security credentials that you can use to
+    # access AWS resources that you might not normally have access to. These
+    # temporary credentials consist of an access key ID, a secret access
+    # key, and a security token. Typically, you use `AssumeRole` within your
+    # account or for cross-account access. For a comparison of `AssumeRole`
+    # with other API operations that produce temporary credentials, see
+    # [Requesting Temporary Security Credentials][1] and [Comparing the AWS
+    # STS API operations][2] in the *IAM User Guide*.
+    #
+    # You cannot use AWS account root user credentials to call `AssumeRole`.
+    # You must use credentials for an IAM user or an IAM role to call
+    # `AssumeRole`.
     #
     # For cross-account access, imagine that you own multiple accounts and
     # need to access resources in each account. You could create long-term
     # credentials in each account to access those resources. However,
     # managing all those credentials and remembering which one can access
     # which account can be time consuming. Instead, you can create one set
-    # of long-term credentials in one account and then use temporary
-    # security credentials to access all the other accounts by assuming
-    # roles in those accounts. For more information about roles, see [IAM
-    # Roles (Delegation and Federation)][3] in the *IAM User Guide*.
-    #
-    # For federation, you can, for example, grant single sign-on access to
-    # the AWS Management Console. If you already have an identity and
-    # authentication system in your corporate network, you don't have to
-    # recreate user identities in AWS in order to grant those user
-    # identities access to AWS. Instead, after a user has been
-    # authenticated, you call `AssumeRole` (and specify the role with the
-    # appropriate permissions) to get temporary security credentials for
-    # that user. With those temporary security credentials, you construct a
-    # sign-in URL that users can use to access the console. For more
-    # information, see [Common Scenarios for Temporary Credentials][4] in
-    # the *IAM User Guide*.
+    # of long-term credentials in one account. Then use temporary security
+    # credentials to access all the other accounts by assuming roles in
+    # those accounts. For more information about roles, see [IAM Roles][3]
+    # in the *IAM User Guide*.
     #
     # By default, the temporary security credentials created by `AssumeRole`
     # last for one hour. However, you can use the optional `DurationSeconds`
@@ -246,85 +279,88 @@ module Aws::STS
     # value from 900 seconds (15 minutes) up to the maximum session duration
     # setting for the role. This setting can have a value from 1 hour to 12
     # hours. To learn how to view the maximum value for your role, see [View
-    # the Maximum Session Duration Setting for a Role][5] in the *IAM User
+    # the Maximum Session Duration Setting for a Role][4] in the *IAM User
     # Guide*. The maximum session duration limit applies when you use the
-    # `AssumeRole*` API operations or the `assume-role*` CLI operations but
-    # does not apply when you use those operations to create a console URL.
-    # For more information, see [Using IAM Roles][6] in the *IAM User
-    # Guide*.
+    # `AssumeRole*` API operations or the `assume-role*` CLI commands.
+    # However the limit does not apply when you use those operations to
+    # create a console URL. For more information, see [Using IAM Roles][5]
+    # in the *IAM User Guide*.
     #
     # The temporary security credentials created by `AssumeRole` can be used
-    # to make API calls to any AWS service with the following exception: you
-    # cannot call the STS service's `GetFederationToken` or
-    # `GetSessionToken` APIs.
-    #
-    # Optionally, you can pass an IAM access policy to this operation. If
-    # you choose not to pass a policy, the temporary security credentials
-    # that are returned by the operation have the permissions that are
-    # defined in the access policy of the role that is being assumed. If you
-    # pass a policy to this operation, the temporary security credentials
-    # that are returned by the operation have the permissions that are
-    # allowed by both the access policy of the role that is being assumed,
-    # <i> <b>and</b> </i> the policy that you pass. This gives you a way to
-    # further restrict the permissions for the resulting temporary security
-    # credentials. You cannot use the passed policy to grant permissions
-    # that are in excess of those allowed by the access policy of the role
-    # that is being assumed. For more information, see [Permissions for
-    # AssumeRole, AssumeRoleWithSAML, and AssumeRoleWithWebIdentity][7] in
-    # the *IAM User Guide*.
-    #
-    # To assume a role, your AWS account must be trusted by the role. The
-    # trust relationship is defined in the role's trust policy when the
-    # role is created. That trust policy states which accounts are allowed
-    # to delegate access to this account's role.
-    #
-    # The user who wants to access the role must also have permissions
-    # delegated from the role's administrator. If the user is in a
-    # different account than the role, then the user's administrator must
-    # attach a policy that allows the user to call AssumeRole on the ARN of
-    # the role in the other account. If the user is in the same account as
-    # the role, then you can either attach a policy to the user (identical
-    # to the previous different account user), or you can add the user as a
-    # principal directly in the role's trust policy. In this case, the
-    # trust policy acts as the only resource-based policy in IAM, and users
-    # in the same account as the role do not need explicit permission to
-    # assume the role. For more information about trust policies and
-    # resource-based policies, see [IAM Policies][8] in the *IAM User
+    # to make API calls to any AWS service with the following exception: You
+    # cannot call the AWS STS `GetFederationToken` or `GetSessionToken` API
+    # operations.
+    #
+    # (Optional) You can pass inline or managed [session policies][6] to
+    # this operation. You can pass a single JSON policy document to use as
+    # an inline session policy. You can also specify up to 10 managed
+    # policies to use as managed session policies. The plain text that you
+    # use for both inline and managed session policies shouldn't exceed
+    # 2048 characters. Passing policies to this operation returns new
+    # temporary credentials. The resulting session's permissions are the
+    # intersection of the role's identity-based policy and the session
+    # policies. You can use the role's temporary credentials in subsequent
+    # AWS API calls to access resources in the account that owns the role.
+    # You cannot use session policies to grant more permissions than those
+    # allowed by the identity-based policy of the role that is being
+    # assumed. For more information, see [Session Policies][6] in the *IAM
+    # User Guide*.
+    #
+    # To assume a role from a different account, your AWS account must be
+    # trusted by the role. The trust relationship is defined in the role's
+    # trust policy when the role is created. That trust policy states which
+    # accounts are allowed to delegate that access to users in the account.
+    #
+    # A user who wants to access a role in a different account must also
+    # have permissions that are delegated from the user account
+    # administrator. The administrator must attach a policy that allows the
+    # user to call `AssumeRole` for the ARN of the role in the other
+    # account. If the user is in the same account as the role, then you can
+    # do either of the following:
+    #
+    # * Attach a policy to the user (identical to the previous user in a
+    #   different account).
+    #
+    # * Add the user as a principal directly in the role's trust policy.
+    #
+    # In this case, the trust policy acts as an IAM resource-based policy.
+    # Users in the same account as the role do not need explicit permission
+    # to assume the role. For more information about trust policies and
+    # resource-based policies, see [IAM Policies][7] in the *IAM User
     # Guide*.
     #
     # **Using MFA with AssumeRole**
     #
-    # You can optionally include multi-factor authentication (MFA)
+    # (Optional) You can include multi-factor authentication (MFA)
     # information when you call `AssumeRole`. This is useful for
-    # cross-account scenarios in which you want to make sure that the user
-    # who is assuming the role has been authenticated using an AWS MFA
-    # device. In that scenario, the trust policy of the role being assumed
-    # includes a condition that tests for MFA authentication; if the caller
-    # does not include valid MFA information, the request to assume the role
-    # is denied. The condition in a trust policy that tests for MFA
-    # authentication might look like the following example.
+    # cross-account scenarios to ensure that the user that assumes the role
+    # has been authenticated with an AWS MFA device. In that scenario, the
+    # trust policy of the role being assumed includes a condition that tests
+    # for MFA authentication. If the caller does not include valid MFA
+    # information, the request to assume the role is denied. The condition
+    # in a trust policy that tests for MFA authentication might look like
+    # the following example.
     #
     # `"Condition": \{"Bool": \{"aws:MultiFactorAuthPresent": true\}\}`
     #
-    # For more information, see [Configuring MFA-Protected API Access][9] in
+    # For more information, see [Configuring MFA-Protected API Access][8] in
     # the *IAM User Guide* guide.
     #
     # To use MFA with `AssumeRole`, you pass values for the `SerialNumber`
     # and `TokenCode` parameters. The `SerialNumber` value identifies the
     # user's hardware or virtual MFA device. The `TokenCode` is the
-    # time-based one-time password (TOTP) that the MFA devices produces.
+    # time-based one-time password (TOTP) that the MFA device produces.
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
-    # [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
-    # [3]: http://docs.aws.amazon.com/IAM/latest/UserGuide/roles-toplevel.html
-    # [4]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html#sts-introduction
-    # [5]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
-    # [6]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html
-    # [7]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_assumerole.html
-    # [8]: http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html
-    # [9]: http://docs.aws.amazon.com/IAM/latest/UserGuide/MFAProtectedAPI.html
+    # [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
+    # [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
+    # [3]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html
+    # [4]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
+    # [5]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html
+    # [6]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    # [7]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html
+    # [8]: https://docs.aws.amazon.com/IAM/latest/UserGuide/MFAProtectedAPI.html
     #
     # @option params [required, String] :role_arn
     #   The Amazon Resource Name (ARN) of the role to assume.
@@ -337,47 +373,82 @@ module Aws::STS
     #   cross-account scenarios, the role session name is visible to, and can
     #   be logged by the account that owns the role. The role session name is
     #   also used in the ARN of the assumed role principal. This means that
-    #   subsequent cross-account API requests using the temporary security
+    #   subsequent cross-account API requests that use the temporary security
     #   credentials will expose the role session name to the external account
-    #   in their CloudTrail logs.
+    #   in their AWS CloudTrail logs.
     #
     #   The regex used to validate this parameter is a string of characters
     #   consisting of upper- and lower-case alphanumeric characters with no
     #   spaces. You can also include underscores or any of the following
     #   characters: =,.@-
     #
-    # @option params [String] :policy
-    #   An IAM policy in JSON format.
-    #
-    #   This parameter is optional. If you pass a policy, the temporary
-    #   security credentials that are returned by the operation have the
-    #   permissions that are allowed by both (the intersection of) the access
-    #   policy of the role that is being assumed, *and* the policy that you
-    #   pass. This gives you a way to further restrict the permissions for the
-    #   resulting temporary security credentials. You cannot use the passed
-    #   policy to grant permissions that are in excess of those allowed by the
-    #   access policy of the role that is being assumed. For more information,
-    #   see [Permissions for AssumeRole, AssumeRoleWithSAML, and
-    #   AssumeRoleWithWebIdentity][1] in the *IAM User Guide*.
+    # @option params [Array<Types::PolicyDescriptorType>] :policy_arns
+    #   The Amazon Resource Names (ARNs) of the IAM managed policies that you
+    #   want to use as managed session policies. The policies must exist in
+    #   the same account as the role.
+    #
+    #   This parameter is optional. You can provide up to 10 managed policy
+    #   ARNs. However, the plain text that you use for both inline and managed
+    #   session policies shouldn't exceed 2048 characters. For more
+    #   information about ARNs, see [Amazon Resource Names (ARNs) and AWS
+    #   Service Namespaces](general/latest/gr/aws-arns-and-namespaces.html) in
+    #   the AWS General Reference.
+    #
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
     #
-    #   The format for this parameter, as described by its regex pattern, is a
-    #   string of characters up to 2048 characters in length. The characters
+    #    </note>
+    #
+    #   Passing policies to this operation returns new temporary credentials.
+    #   The resulting session's permissions are the intersection of the
+    #   role's identity-based policy and the session policies. You can use
+    #   the role's temporary credentials in subsequent AWS API calls to
+    #   access resources in the account that owns the role. You cannot use
+    #   session policies to grant more permissions than those allowed by the
+    #   identity-based policy of the role that is being assumed. For more
+    #   information, see [Session Policies][1] in the *IAM User Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    #
+    # @option params [String] :policy
+    #   An IAM policy in JSON format that you want to use as an inline session
+    #   policy.
+    #
+    #   This parameter is optional. Passing policies to this operation returns
+    #   new temporary credentials. The resulting session's permissions are
+    #   the intersection of the role's identity-based policy and the session
+    #   policies. You can use the role's temporary credentials in subsequent
+    #   AWS API calls to access resources in the account that owns the role.
+    #   You cannot use session policies to grant more permissions than those
+    #   allowed by the identity-based policy of the role that is being
+    #   assumed. For more information, see [Session Policies][1] in the *IAM
+    #   User Guide*.
+    #
+    #   The plain text that you use for both inline and managed session
+    #   policies shouldn't exceed 2048 characters. The JSON policy characters
     #   can be any ASCII character from the space character to the end of the
-    #   valid character list (\\u0020-\\u00FF). It can also include the tab
-    #   (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
+    #   valid character list (\\u0020 through \\u00FF). It can also include
+    #   the tab (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
     #   characters.
     #
-    #   <note markdown="1"> The policy plain text must be 2048 bytes or shorter. However, an
-    #   internal conversion compresses it into a packed binary format with a
-    #   separate limit. The PackedPolicySize response element indicates by
-    #   percentage how close to the upper size limit the policy is, with 100%
-    #   equaling the maximum allowed size.
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
     #
     #    </note>
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_assumerole.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
     #
     # @option params [Integer] :duration_seconds
     #   The duration, in seconds, of the role session. The value can range
@@ -390,7 +461,7 @@ module Aws::STS
     #   see [View the Maximum Session Duration Setting for a Role][1] in the
     #   *IAM User Guide*.
     #
-    #   By default, the value is set to 3600 seconds.
+    #   By default, the value is set to `3600` seconds.
     #
     #   <note markdown="1"> The `DurationSeconds` parameter is separate from the duration of a
     #   console session that you might request using the returned credentials.
@@ -404,29 +475,30 @@ module Aws::STS
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
-    #   [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
+    #   [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html
     #
     # @option params [String] :external_id
-    #   A unique identifier that is used by third parties when assuming roles
-    #   in their customers' accounts. For each role that the third party can
-    #   assume, they should instruct their customers to ensure the role's
-    #   trust policy checks for the external ID that the third party
-    #   generated. Each time the third party assumes the role, they should
-    #   pass the customer's external ID. The external ID is useful in order
-    #   to help third parties bind a role to the customer who created it. For
-    #   more information about the external ID, see [How to Use an External ID
-    #   When Granting Access to Your AWS Resources to a Third Party][1] in the
-    #   *IAM User Guide*.
+    #   A unique identifier that might be required when you assume a role in
+    #   another account. If the administrator of the account to which the role
+    #   belongs provided you with an external ID, then provide that value in
+    #   the `ExternalId` parameter. This value can be any string, such as a
+    #   passphrase or account number. A cross-account role is usually set up
+    #   to trust everyone in an account. Therefore, the administrator of the
+    #   trusting account might send an external ID to the administrator of the
+    #   trusted account. That way, only someone with the ID can assume the
+    #   role, rather than everyone in the account. For more information about
+    #   the external ID, see [How to Use an External ID When Granting Access
+    #   to Your AWS Resources to a Third Party][1] in the *IAM User Guide*.
     #
-    #   The regex used to validated this parameter is a string of characters
+    #   The regex used to validate this parameter is a string of characters
     #   consisting of upper- and lower-case alphanumeric characters with no
     #   spaces. You can also include underscores or any of the following
     #   characters: =,.@:/-
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html
     #
     # @option params [String] :serial_number
     #   The identification number of the MFA device that is associated with
@@ -464,7 +536,7 @@ module Aws::STS
     #   resp = client.assume_role({
     #     duration_seconds: 3600, 
     #     external_id: "123ABC", 
-    #     policy: "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"Stmt1\",\"Effect\":\"Allow\",\"Action\":\"s3:*\",\"Resource\":\"*\"}]}", 
+    #     policy: "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"Stmt1\",\"Effect\":\"Allow\",\"Action\":\"s3:ListAllMyBuckets\",\"Resource\":\"*\"}]}", 
     #     role_arn: "arn:aws:iam::123456789012:role/demo", 
     #     role_session_name: "Bob", 
     #   })
@@ -489,6 +561,11 @@ module Aws::STS
     #   resp = client.assume_role({
     #     role_arn: "arnType", # required
     #     role_session_name: "roleSessionNameType", # required
+    #     policy_arns: [
+    #       {
+    #         arn: "arnType",
+    #       },
+    #     ],
     #     policy: "sessionPolicyDocumentType",
     #     duration_seconds: 1,
     #     external_id: "externalIdType",
@@ -520,9 +597,9 @@ module Aws::STS
     # provides a mechanism for tying an enterprise identity store or
     # directory to role-based AWS access without user-specific credentials
     # or configuration. For a comparison of `AssumeRoleWithSAML` with the
-    # other APIs that produce temporary credentials, see [Requesting
-    # Temporary Security Credentials][1] and [Comparing the AWS STS APIs][2]
-    # in the *IAM User Guide*.
+    # other API operations that produce temporary credentials, see
+    # [Requesting Temporary Security Credentials][1] and [Comparing the AWS
+    # STS API operations][2] in the *IAM User Guide*.
     #
     # The temporary security credentials returned by this operation consist
     # of an access key ID, a secret access key, and a security token.
@@ -541,37 +618,36 @@ module Aws::STS
     # for your role, see [View the Maximum Session Duration Setting for a
     # Role][3] in the *IAM User Guide*. The maximum session duration limit
     # applies when you use the `AssumeRole*` API operations or the
-    # `assume-role*` CLI operations but does not apply when you use those
-    # operations to create a console URL. For more information, see [Using
-    # IAM Roles][4] in the *IAM User Guide*.
+    # `assume-role*` CLI commands. However the limit does not apply when you
+    # use those operations to create a console URL. For more information,
+    # see [Using IAM Roles][4] in the *IAM User Guide*.
     #
     # The temporary security credentials created by `AssumeRoleWithSAML` can
     # be used to make API calls to any AWS service with the following
-    # exception: you cannot call the STS service's `GetFederationToken` or
-    # `GetSessionToken` APIs.
-    #
-    # Optionally, you can pass an IAM access policy to this operation. If
-    # you choose not to pass a policy, the temporary security credentials
-    # that are returned by the operation have the permissions that are
-    # defined in the access policy of the role that is being assumed. If you
-    # pass a policy to this operation, the temporary security credentials
-    # that are returned by the operation have the permissions that are
-    # allowed by the intersection of both the access policy of the role that
-    # is being assumed, <i> <b>and</b> </i> the policy that you pass. This
-    # means that both policies must grant the permission for the action to
-    # be allowed. This gives you a way to further restrict the permissions
-    # for the resulting temporary security credentials. You cannot use the
-    # passed policy to grant permissions that are in excess of those allowed
-    # by the access policy of the role that is being assumed. For more
-    # information, see [Permissions for AssumeRole, AssumeRoleWithSAML, and
-    # AssumeRoleWithWebIdentity][5] in the *IAM User Guide*.
+    # exception: you cannot call the STS `GetFederationToken` or
+    # `GetSessionToken` API operations.
+    #
+    # (Optional) You can pass inline or managed [session policies][5] to
+    # this operation. You can pass a single JSON policy document to use as
+    # an inline session policy. You can also specify up to 10 managed
+    # policies to use as managed session policies. The plain text that you
+    # use for both inline and managed session policies shouldn't exceed
+    # 2048 characters. Passing policies to this operation returns new
+    # temporary credentials. The resulting session's permissions are the
+    # intersection of the role's identity-based policy and the session
+    # policies. You can use the role's temporary credentials in subsequent
+    # AWS API calls to access resources in the account that owns the role.
+    # You cannot use session policies to grant more permissions than those
+    # allowed by the identity-based policy of the role that is being
+    # assumed. For more information, see [Session Policies][5] in the *IAM
+    # User Guide*.
     #
     # Before your application can call `AssumeRoleWithSAML`, you must
     # configure your SAML identity provider (IdP) to issue the claims
     # required by AWS. Additionally, you must use AWS Identity and Access
     # Management (IAM) to create a SAML provider entity in your AWS account
-    # that represents your identity provider, and create an IAM role that
-    # specifies this SAML provider in its trust policy.
+    # that represents your identity provider. You must also create an IAM
+    # role that specifies this SAML provider in its trust policy.
     #
     # Calling `AssumeRoleWithSAML` does not require the use of AWS security
     # credentials. The identity of the caller is validated by using keys in
@@ -580,9 +656,9 @@ module Aws::STS
     #
     # Calling `AssumeRoleWithSAML` can result in an entry in your AWS
     # CloudTrail logs. The entry includes the value in the `NameID` element
-    # of the SAML assertion. We recommend that you use a NameIDType that is
-    # not associated with any personally identifiable information (PII). For
-    # example, you could instead use the Persistent Identifier
+    # of the SAML assertion. We recommend that you use a `NameIDType` that
+    # is not associated with any personally identifiable information (PII).
+    # For example, you could instead use the Persistent Identifier
     # (`urn:oasis:names:tc:SAML:2.0:nameid-format:persistent`).
     #
     # For more information, see the following resources:
@@ -598,15 +674,15 @@ module Aws::STS
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
-    # [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
-    # [3]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
-    # [4]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html
-    # [5]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_assumerole.html
-    # [6]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_saml.html
-    # [7]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml.html
-    # [8]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml_relying-party.html
-    # [9]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_saml.html
+    # [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
+    # [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
+    # [3]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
+    # [4]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html
+    # [5]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    # [6]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_saml.html
+    # [7]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml.html
+    # [8]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_saml_relying-party.html
+    # [9]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_saml.html
     #
     # @option params [required, String] :role_arn
     #   The Amazon Resource Name (ARN) of the role that the caller is
@@ -620,44 +696,79 @@ module Aws::STS
     #   The base-64 encoded SAML authentication response provided by the IdP.
     #
     #   For more information, see [Configuring a Relying Party and Adding
-    #   Claims][1] in the *Using IAM* guide.
+    #   Claims][1] in the *IAM User Guide*.
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/create-role-saml-IdP-tasks.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/create-role-saml-IdP-tasks.html
     #
-    # @option params [String] :policy
-    #   An IAM policy in JSON format.
-    #
-    #   The policy parameter is optional. If you pass a policy, the temporary
-    #   security credentials that are returned by the operation have the
-    #   permissions that are allowed by both the access policy of the role
-    #   that is being assumed, <i> <b>and</b> </i> the policy that you pass.
-    #   This gives you a way to further restrict the permissions for the
-    #   resulting temporary security credentials. You cannot use the passed
-    #   policy to grant permissions that are in excess of those allowed by the
-    #   access policy of the role that is being assumed. For more information,
-    #   [Permissions for AssumeRole, AssumeRoleWithSAML, and
-    #   AssumeRoleWithWebIdentity][1] in the *IAM User Guide*.
+    # @option params [Array<Types::PolicyDescriptorType>] :policy_arns
+    #   The Amazon Resource Names (ARNs) of the IAM managed policies that you
+    #   want to use as managed session policies. The policies must exist in
+    #   the same account as the role.
     #
-    #   The format for this parameter, as described by its regex pattern, is a
-    #   string of characters up to 2048 characters in length. The characters
+    #   This parameter is optional. You can provide up to 10 managed policy
+    #   ARNs. However, the plain text that you use for both inline and managed
+    #   session policies shouldn't exceed 2048 characters. For more
+    #   information about ARNs, see [Amazon Resource Names (ARNs) and AWS
+    #   Service Namespaces](general/latest/gr/aws-arns-and-namespaces.html) in
+    #   the AWS General Reference.
+    #
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
+    #
+    #    </note>
+    #
+    #   Passing policies to this operation returns new temporary credentials.
+    #   The resulting session's permissions are the intersection of the
+    #   role's identity-based policy and the session policies. You can use
+    #   the role's temporary credentials in subsequent AWS API calls to
+    #   access resources in the account that owns the role. You cannot use
+    #   session policies to grant more permissions than those allowed by the
+    #   identity-based policy of the role that is being assumed. For more
+    #   information, see [Session Policies][1] in the *IAM User Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    #
+    # @option params [String] :policy
+    #   An IAM policy in JSON format that you want to use as an inline session
+    #   policy.
+    #
+    #   This parameter is optional. Passing policies to this operation returns
+    #   new temporary credentials. The resulting session's permissions are
+    #   the intersection of the role's identity-based policy and the session
+    #   policies. You can use the role's temporary credentials in subsequent
+    #   AWS API calls to access resources in the account that owns the role.
+    #   You cannot use session policies to grant more permissions than those
+    #   allowed by the identity-based policy of the role that is being
+    #   assumed. For more information, see [Session Policies][1] in the *IAM
+    #   User Guide*.
+    #
+    #   The plain text that you use for both inline and managed session
+    #   policies shouldn't exceed 2048 characters. The JSON policy characters
     #   can be any ASCII character from the space character to the end of the
-    #   valid character list (\\u0020-\\u00FF). It can also include the tab
-    #   (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
+    #   valid character list (\\u0020 through \\u00FF). It can also include
+    #   the tab (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
     #   characters.
     #
-    #   <note markdown="1"> The policy plain text must be 2048 bytes or shorter. However, an
-    #   internal conversion compresses it into a packed binary format with a
-    #   separate limit. The PackedPolicySize response element indicates by
-    #   percentage how close to the upper size limit the policy is, with 100%
-    #   equaling the maximum allowed size.
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
     #
     #    </note>
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_assumerole.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
     #
     # @option params [Integer] :duration_seconds
     #   The duration, in seconds, of the role session. Your role session lasts
@@ -673,7 +784,7 @@ module Aws::STS
     #   maximum value for your role, see [View the Maximum Session Duration
     #   Setting for a Role][1] in the *IAM User Guide*.
     #
-    #   By default, the value is set to 3600 seconds.
+    #   By default, the value is set to `3600` seconds.
     #
     #   <note markdown="1"> The `DurationSeconds` parameter is separate from the duration of a
     #   console session that you might request using the returned credentials.
@@ -687,8 +798,8 @@ module Aws::STS
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
-    #   [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
+    #   [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html
     #
     # @return [Types::AssumeRoleWithSAMLResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -707,6 +818,11 @@ module Aws::STS
     #     role_arn: "arnType", # required
     #     principal_arn: "arnType", # required
     #     saml_assertion: "SAMLAssertionType", # required
+    #     policy_arns: [
+    #       {
+    #         arn: "arnType",
+    #       },
+    #     ],
     #     policy: "sessionPolicyDocumentType",
     #     duration_seconds: 1,
     #   })
@@ -737,16 +853,17 @@ module Aws::STS
 
     # Returns a set of temporary security credentials for users who have
     # been authenticated in a mobile or web application with a web identity
-    # provider, such as Amazon Cognito, Login with Amazon, Facebook, Google,
-    # or any OpenID Connect-compatible identity provider.
+    # provider. Example providers include Amazon Cognito, Login with Amazon,
+    # Facebook, Google, or any OpenID Connect-compatible identity provider.
     #
     # <note markdown="1"> For mobile applications, we recommend that you use Amazon Cognito. You
-    # can use Amazon Cognito with the [AWS SDK for iOS][1] and the [AWS SDK
-    # for Android][2] to uniquely identify a user and supply the user with a
-    # consistent identity throughout the lifetime of an application.
+    # can use Amazon Cognito with the [AWS SDK for iOS Developer Guide][1]
+    # and the [AWS SDK for Android Developer Guide][2] to uniquely identify
+    # a user. You can also supply the user with a consistent identity
+    # throughout the lifetime of an application.
     #
     #  To learn more about Amazon Cognito, see [Amazon Cognito Overview][3]
-    # in the *AWS SDK for Android Developer Guide* guide and [Amazon Cognito
+    # in *AWS SDK for Android Developer Guide* and [Amazon Cognito
     # Overview][4] in the *AWS SDK for iOS Developer Guide*.
     #
     #  </note>
@@ -755,18 +872,18 @@ module Aws::STS
     # security credentials. Therefore, you can distribute an application
     # (for example, on mobile devices) that requests temporary security
     # credentials without including long-term AWS credentials in the
-    # application, and without deploying server-based proxy services that
-    # use long-term AWS credentials. Instead, the identity of the caller is
-    # validated by using a token from the web identity provider. For a
-    # comparison of `AssumeRoleWithWebIdentity` with the other APIs that
-    # produce temporary credentials, see [Requesting Temporary Security
-    # Credentials][5] and [Comparing the AWS STS APIs][6] in the *IAM User
-    # Guide*.
+    # application. You also don't need to deploy server-based proxy
+    # services that use long-term AWS credentials. Instead, the identity of
+    # the caller is validated by using a token from the web identity
+    # provider. For a comparison of `AssumeRoleWithWebIdentity` with the
+    # other API operations that produce temporary credentials, see
+    # [Requesting Temporary Security Credentials][5] and [Comparing the AWS
+    # STS API operations][6] in the *IAM User Guide*.
     #
     # The temporary security credentials returned by this API consist of an
     # access key ID, a secret access key, and a security token. Applications
     # can use these temporary security credentials to sign calls to AWS
-    # service APIs.
+    # service API operations.
     #
     # By default, the temporary security credentials created by
     # `AssumeRoleWithWebIdentity` last for one hour. However, you can use
@@ -777,29 +894,29 @@ module Aws::STS
     # value for your role, see [View the Maximum Session Duration Setting
     # for a Role][7] in the *IAM User Guide*. The maximum session duration
     # limit applies when you use the `AssumeRole*` API operations or the
-    # `assume-role*` CLI operations but does not apply when you use those
-    # operations to create a console URL. For more information, see [Using
-    # IAM Roles][8] in the *IAM User Guide*.
+    # `assume-role*` CLI commands. However the limit does not apply when you
+    # use those operations to create a console URL. For more information,
+    # see [Using IAM Roles][8] in the *IAM User Guide*.
     #
     # The temporary security credentials created by
     # `AssumeRoleWithWebIdentity` can be used to make API calls to any AWS
     # service with the following exception: you cannot call the STS
-    # service's `GetFederationToken` or `GetSessionToken` APIs.
-    #
-    # Optionally, you can pass an IAM access policy to this operation. If
-    # you choose not to pass a policy, the temporary security credentials
-    # that are returned by the operation have the permissions that are
-    # defined in the access policy of the role that is being assumed. If you
-    # pass a policy to this operation, the temporary security credentials
-    # that are returned by the operation have the permissions that are
-    # allowed by both the access policy of the role that is being assumed,
-    # <i> <b>and</b> </i> the policy that you pass. This gives you a way to
-    # further restrict the permissions for the resulting temporary security
-    # credentials. You cannot use the passed policy to grant permissions
-    # that are in excess of those allowed by the access policy of the role
-    # that is being assumed. For more information, see [Permissions for
-    # AssumeRole, AssumeRoleWithSAML, and AssumeRoleWithWebIdentity][9] in
-    # the *IAM User Guide*.
+    # `GetFederationToken` or `GetSessionToken` API operations.
+    #
+    # (Optional) You can pass inline or managed [session policies][9] to
+    # this operation. You can pass a single JSON policy document to use as
+    # an inline session policy. You can also specify up to 10 managed
+    # policies to use as managed session policies. The plain text that you
+    # use for both inline and managed session policies shouldn't exceed
+    # 2048 characters. Passing policies to this operation returns new
+    # temporary credentials. The resulting session's permissions are the
+    # intersection of the role's identity-based policy and the session
+    # policies. You can use the role's temporary credentials in subsequent
+    # AWS API calls to access resources in the account that owns the role.
+    # You cannot use session policies to grant more permissions than those
+    # allowed by the identity-based policy of the role that is being
+    # assumed. For more information, see [Session Policies][9] in the *IAM
+    # User Guide*.
     #
     # Before your application can call `AssumeRoleWithWebIdentity`, you must
     # have an identity token from a supported identity provider and create a
@@ -818,18 +935,19 @@ module Aws::STS
     # For more information about how to use web identity federation and the
     # `AssumeRoleWithWebIdentity` API, see the following resources:
     #
-    # * [Using Web Identity Federation APIs for Mobile Apps][12] and
-    #   [Federation Through a Web-based Identity Provider][13].
+    # * [Using Web Identity Federation API Operations for Mobile Apps][12]
+    #   and [Federation Through a Web-based Identity Provider][13].
     #
-    # * [ Web Identity Federation Playground][14]. This interactive website
-    #   lets you walk through the process of authenticating via Login with
-    #   Amazon, Facebook, or Google, getting temporary security credentials,
-    #   and then using those credentials to make a request to AWS.
+    # * [ Web Identity Federation Playground][14]. Walk through the process
+    #   of authenticating through Login with Amazon, Facebook, or Google,
+    #   getting temporary security credentials, and then using those
+    #   credentials to make a request to AWS.
     #
-    # * [AWS SDK for iOS][1] and [AWS SDK for Android][2]. These toolkits
-    #   contain sample apps that show how to invoke the identity providers,
-    #   and then how to use the information from these providers to get and
-    #   use temporary security credentials.
+    # * [AWS SDK for iOS Developer Guide][1] and [AWS SDK for Android
+    #   Developer Guide][2]. These toolkits contain sample apps that show
+    #   how to invoke the identity providers, and then how to use the
+    #   information from these providers to get and use temporary security
+    #   credentials.
     #
     # * [Web Identity Federation with Mobile Applications][15]. This article
     #   discusses web identity federation and shows an example of how to use
@@ -839,17 +957,17 @@ module Aws::STS
     #
     # [1]: http://aws.amazon.com/sdkforios/
     # [2]: http://aws.amazon.com/sdkforandroid/
-    # [3]: http://docs.aws.amazon.com/mobile/sdkforandroid/developerguide/cognito-auth.html#d0e840
-    # [4]: http://docs.aws.amazon.com/mobile/sdkforios/developerguide/cognito-auth.html#d0e664
-    # [5]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
-    # [6]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
-    # [7]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
-    # [8]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html
-    # [9]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_assumerole.html
+    # [3]: https://docs.aws.amazon.com/mobile/sdkforandroid/developerguide/cognito-auth.html#d0e840
+    # [4]: https://docs.aws.amazon.com/mobile/sdkforios/developerguide/cognito-auth.html#d0e664
+    # [5]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
+    # [6]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
+    # [7]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
+    # [8]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html
+    # [9]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
     # [10]: http://openid.net/specs/openid-connect-core-1_0.html#Claims
     # [11]: http://openid.net/specs/openid-connect-core-1_0.html#SubjectIDTypes
-    # [12]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_oidc_manual.html
-    # [13]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity
+    # [12]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_oidc_manual.html
+    # [13]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity
     # [14]: https://web-identity-federation-playground.s3.amazonaws.com/index.html
     # [15]: http://aws.amazon.com/articles/web-identity-federation-with-mobile-applications
     #
@@ -888,38 +1006,73 @@ module Aws::STS
     #
     #   Do not specify this value for OpenID Connect ID tokens.
     #
-    # @option params [String] :policy
-    #   An IAM policy in JSON format.
-    #
-    #   The policy parameter is optional. If you pass a policy, the temporary
-    #   security credentials that are returned by the operation have the
-    #   permissions that are allowed by both the access policy of the role
-    #   that is being assumed, <i> <b>and</b> </i> the policy that you pass.
-    #   This gives you a way to further restrict the permissions for the
-    #   resulting temporary security credentials. You cannot use the passed
-    #   policy to grant permissions that are in excess of those allowed by the
-    #   access policy of the role that is being assumed. For more information,
-    #   see [Permissions for AssumeRoleWithWebIdentity][1] in the *IAM User
-    #   Guide*.
+    # @option params [Array<Types::PolicyDescriptorType>] :policy_arns
+    #   The Amazon Resource Names (ARNs) of the IAM managed policies that you
+    #   want to use as managed session policies. The policies must exist in
+    #   the same account as the role.
+    #
+    #   This parameter is optional. You can provide up to 10 managed policy
+    #   ARNs. However, the plain text that you use for both inline and managed
+    #   session policies shouldn't exceed 2048 characters. For more
+    #   information about ARNs, see [Amazon Resource Names (ARNs) and AWS
+    #   Service Namespaces](general/latest/gr/aws-arns-and-namespaces.html) in
+    #   the AWS General Reference.
+    #
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
     #
-    #   The format for this parameter, as described by its regex pattern, is a
-    #   string of characters up to 2048 characters in length. The characters
+    #    </note>
+    #
+    #   Passing policies to this operation returns new temporary credentials.
+    #   The resulting session's permissions are the intersection of the
+    #   role's identity-based policy and the session policies. You can use
+    #   the role's temporary credentials in subsequent AWS API calls to
+    #   access resources in the account that owns the role. You cannot use
+    #   session policies to grant more permissions than those allowed by the
+    #   identity-based policy of the role that is being assumed. For more
+    #   information, see [Session Policies][1] in the *IAM User Guide*.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    #
+    # @option params [String] :policy
+    #   An IAM policy in JSON format that you want to use as an inline session
+    #   policy.
+    #
+    #   This parameter is optional. Passing policies to this operation returns
+    #   new temporary credentials. The resulting session's permissions are
+    #   the intersection of the role's identity-based policy and the session
+    #   policies. You can use the role's temporary credentials in subsequent
+    #   AWS API calls to access resources in the account that owns the role.
+    #   You cannot use session policies to grant more permissions than those
+    #   allowed by the identity-based policy of the role that is being
+    #   assumed. For more information, see [Session Policies][1] in the *IAM
+    #   User Guide*.
+    #
+    #   The plain text that you use for both inline and managed session
+    #   policies shouldn't exceed 2048 characters. The JSON policy characters
     #   can be any ASCII character from the space character to the end of the
-    #   valid character list (\\u0020-\\u00FF). It can also include the tab
-    #   (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
+    #   valid character list (\\u0020 through \\u00FF). It can also include
+    #   the tab (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
     #   characters.
     #
-    #   <note markdown="1"> The policy plain text must be 2048 bytes or shorter. However, an
-    #   internal conversion compresses it into a packed binary format with a
-    #   separate limit. The PackedPolicySize response element indicates by
-    #   percentage how close to the upper size limit the policy is, with 100%
-    #   equaling the maximum allowed size.
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
     #
     #    </note>
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_assumerole.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
     #
     # @option params [Integer] :duration_seconds
     #   The duration, in seconds, of the role session. The value can range
@@ -932,7 +1085,7 @@ module Aws::STS
     #   see [View the Maximum Session Duration Setting for a Role][1] in the
     #   *IAM User Guide*.
     #
-    #   By default, the value is set to 3600 seconds.
+    #   By default, the value is set to `3600` seconds.
     #
     #   <note markdown="1"> The `DurationSeconds` parameter is separate from the duration of a
     #   console session that you might request using the returned credentials.
@@ -946,8 +1099,8 @@ module Aws::STS
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
-    #   [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use.html#id_roles_use_view-role-max-session
+    #   [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html
     #
     # @return [Types::AssumeRoleWithWebIdentityResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -963,6 +1116,7 @@ module Aws::STS
     #
     #   resp = client.assume_role_with_web_identity({
     #     duration_seconds: 3600, 
+    #     policy: "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"Stmt1\",\"Effect\":\"Allow\",\"Action\":\"s3:ListAllMyBuckets\",\"Resource\":\"*\"}]}", 
     #     provider_id: "www.amazon.com", 
     #     role_arn: "arn:aws:iam::123456789012:role/FederatedWebIdentityRole", 
     #     role_session_name: "app1", 
@@ -994,6 +1148,11 @@ module Aws::STS
     #     role_session_name: "roleSessionNameType", # required
     #     web_identity_token: "clientTokenType", # required
     #     provider_id: "urlType",
+    #     policy_arns: [
+    #       {
+    #         arn: "arnType",
+    #       },
+    #     ],
     #     policy: "sessionPolicyDocumentType",
     #     duration_seconds: 1,
     #   })
@@ -1024,21 +1183,22 @@ module Aws::STS
     # request from an encoded message returned in response to an AWS
     # request.
     #
-    # For example, if a user is not authorized to perform an action that he
-    # or she has requested, the request returns a
+    # For example, if a user is not authorized to perform an operation that
+    # he or she has requested, the request returns a
     # `Client.UnauthorizedOperation` response (an HTTP 403 response). Some
-    # AWS actions additionally return an encoded message that can provide
+    # AWS operations additionally return an encoded message that can provide
     # details about this authorization failure.
     #
-    # <note markdown="1"> Only certain AWS actions return an encoded authorization message. The
-    # documentation for an individual action indicates whether that action
-    # returns an encoded message in addition to returning an HTTP code.
+    # <note markdown="1"> Only certain AWS operations return an encoded authorization message.
+    # The documentation for an individual operation indicates whether that
+    # operation returns an encoded message in addition to returning an HTTP
+    # code.
     #
     #  </note>
     #
     # The message is encoded because the details of the authorization status
     # can constitute privileged information that the user who requested the
-    # action should not see. To decode an authorization status message, a
+    # operation should not see. To decode an authorization status message, a
     # user must be granted permissions via an IAM policy to request the
     # `DecodeAuthorizationMessage` (`sts:DecodeAuthorizationMessage`)
     # action.
@@ -1059,7 +1219,7 @@ module Aws::STS
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html#policy-eval-denyallow
+    # [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html#policy-eval-denyallow
     #
     # @option params [required, String] :encoded_message
     #   The encoded message that was returned with the response.
@@ -1173,97 +1333,79 @@ module Aws::STS
     # access key ID, a secret access key, and a security token) for a
     # federated user. A typical use is in a proxy application that gets
     # temporary security credentials on behalf of distributed applications
-    # inside a corporate network. Because you must call the
-    # `GetFederationToken` action using the long-term security credentials
-    # of an IAM user, this call is appropriate in contexts where those
-    # credentials can be safely stored, usually in a server-based
-    # application. For a comparison of `GetFederationToken` with the other
-    # APIs that produce temporary credentials, see [Requesting Temporary
-    # Security Credentials][1] and [Comparing the AWS STS APIs][2] in the
+    # inside a corporate network. You must call the `GetFederationToken`
+    # operation using the long-term security credentials of an IAM user. As
+    # a result, this call is appropriate in contexts where those credentials
+    # can be safely stored, usually in a server-based application. For a
+    # comparison of `GetFederationToken` with the other API operations that
+    # produce temporary credentials, see [Requesting Temporary Security
+    # Credentials][1] and [Comparing the AWS STS API operations][2] in the
     # *IAM User Guide*.
     #
-    # <note markdown="1"> If you are creating a mobile-based or browser-based app that can
+    # <note markdown="1"> You can create a mobile-based or browser-based app that can
     # authenticate users using a web identity provider like Login with
     # Amazon, Facebook, Google, or an OpenID Connect-compatible identity
-    # provider, we recommend that you use [Amazon Cognito][3] or
-    # `AssumeRoleWithWebIdentity`. For more information, see [Federation
+    # provider. In this case, we recommend that you use [Amazon Cognito][3]
+    # or `AssumeRoleWithWebIdentity`. For more information, see [Federation
     # Through a Web-based Identity Provider][4].
     #
     #  </note>
     #
-    # The `GetFederationToken` action must be called by using the long-term
-    # AWS security credentials of an IAM user. You can also call
-    # `GetFederationToken` using the security credentials of an AWS root
-    # account, but we do not recommended it. Instead, we recommend that you
-    # create an IAM user for the purpose of the proxy application and then
-    # attach a policy to the IAM user that limits federated users to only
-    # the actions and resources that they need access to. For more
-    # information, see [IAM Best Practices][5] in the *IAM User Guide*.
-    #
-    # The temporary security credentials that are obtained by using the
-    # long-term credentials of an IAM user are valid for the specified
-    # duration, from 900 seconds (15 minutes) up to a maximium of 129600
-    # seconds (36 hours). The default is 43200 seconds (12 hours). Temporary
-    # credentials that are obtained by using AWS root account credentials
-    # have a maximum duration of 3600 seconds (1 hour).
+    # You can also call `GetFederationToken` using the security credentials
+    # of an AWS account root user, but we do not recommend it. Instead, we
+    # recommend that you create an IAM user for the purpose of the proxy
+    # application. Then attach a policy to the IAM user that limits
+    # federated users to only the actions and resources that they need to
+    # access. For more information, see [IAM Best Practices][5] in the *IAM
+    # User Guide*.
+    #
+    # The temporary credentials are valid for the specified duration, from
+    # 900 seconds (15 minutes) up to a maximum of 129,600 seconds (36
+    # hours). The default is 43,200 seconds (12 hours). Temporary
+    # credentials that are obtained by using AWS account root user
+    # credentials have a maximum duration of 3,600 seconds (1 hour).
     #
     # The temporary security credentials created by `GetFederationToken` can
     # be used to make API calls to any AWS service with the following
     # exceptions:
     #
-    # * You cannot use these credentials to call any IAM APIs.
+    # * You cannot use these credentials to call any IAM API operations.
     #
-    # * You cannot call any STS APIs except `GetCallerIdentity`.
+    # * You cannot call any STS API operations except `GetCallerIdentity`.
     #
     # **Permissions**
     #
-    # The permissions for the temporary security credentials returned by
-    # `GetFederationToken` are determined by a combination of the following:
-    #
-    # * The policy or policies that are attached to the IAM user whose
-    #   credentials are used to call `GetFederationToken`.
-    #
-    # * The policy that is passed as a parameter in the call.
-    #
-    # The passed policy is attached to the temporary security credentials
-    # that result from the `GetFederationToken` API call--that is, to the
-    # *federated user*. When the federated user makes an AWS request, AWS
-    # evaluates the policy attached to the federated user in combination
-    # with the policy or policies attached to the IAM user whose credentials
-    # were used to call `GetFederationToken`. AWS allows the federated
-    # user's request only when both the federated user <i> <b>and</b> </i>
-    # the IAM user are explicitly allowed to perform the requested action.
-    # The passed policy cannot grant more permissions than those that are
-    # defined in the IAM user policy.
-    #
-    # A typical use case is that the permissions of the IAM user whose
-    # credentials are used to call `GetFederationToken` are designed to
-    # allow access to all the actions and resources that any federated user
-    # will need. Then, for individual users, you pass a policy to the
-    # operation that scopes down the permissions to a level that's
-    # appropriate to that individual user, using a policy that allows only a
-    # subset of permissions that are granted to the IAM user.
-    #
-    # If you do not pass a policy, the resulting temporary security
-    # credentials have no effective permissions. The only exception is when
-    # the temporary security credentials are used to access a resource that
-    # has a resource-based policy that specifically allows the federated
-    # user to access the resource.
-    #
-    # For more information about how permissions work, see [Permissions for
-    # GetFederationToken][6]. For information about using
+    # You must pass an inline or managed [session policy][6] to this
+    # operation. You can pass a single JSON policy document to use as an
+    # inline session policy. You can also specify up to 10 managed policies
+    # to use as managed session policies. The plain text that you use for
+    # both inline and managed session policies shouldn't exceed 2048
+    # characters.
+    #
+    # Though the session policy parameters are optional, if you do not pass
+    # a policy, then the resulting federated user session has no
+    # permissions. The only exception is when the credentials are used to
+    # access a resource that has a resource-based policy that specifically
+    # references the federated user session in the `Principal` element of
+    # the policy. When you pass session policies, the session permissions
+    # are the intersection of the IAM user policies and the session policies
+    # that you pass. This gives you a way to further restrict the
+    # permissions for a federated user. You cannot use session policies to
+    # grant more permissions than those that are defined in the permissions
+    # policy of the IAM user. For more information, see [Session
+    # Policies][6] in the *IAM User Guide*. For information about using
     # `GetFederationToken` to create temporary security credentials, see
     # [GetFederationToken—Federation Through a Custom Identity Broker][7].
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
-    # [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
+    # [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
+    # [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
     # [3]: http://aws.amazon.com/cognito/
-    # [4]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity
-    # [5]: http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
-    # [6]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_getfederationtoken.html
-    # [7]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getfederationtoken
+    # [4]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_assumerolewithwebidentity
+    # [5]: https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
+    # [6]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    # [7]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getfederationtoken
     #
     # @option params [required, String] :name
     #   The name of the federated user. The name is used as an identifier for
@@ -1277,53 +1419,100 @@ module Aws::STS
     #   characters: =,.@-
     #
     # @option params [String] :policy
-    #   An IAM policy in JSON format that is passed with the
-    #   `GetFederationToken` call and evaluated along with the policy or
-    #   policies that are attached to the IAM user whose credentials are used
-    #   to call `GetFederationToken`. The passed policy is used to scope down
-    #   the permissions that are available to the IAM user, by allowing only a
-    #   subset of the permissions that are granted to the IAM user. The passed
-    #   policy cannot grant more permissions than those granted to the IAM
-    #   user. The final permissions for the federated user are the most
-    #   restrictive set based on the intersection of the passed policy and the
-    #   IAM user policy.
-    #
-    #   If you do not pass a policy, the resulting temporary security
-    #   credentials have no effective permissions. The only exception is when
-    #   the temporary security credentials are used to access a resource that
-    #   has a resource-based policy that specifically allows the federated
-    #   user to access the resource.
+    #   An IAM policy in JSON format that you want to use as an inline session
+    #   policy.
+    #
+    #   You must pass an inline or managed [session policy][1] to this
+    #   operation. You can pass a single JSON policy document to use as an
+    #   inline session policy. You can also specify up to 10 managed policies
+    #   to use as managed session policies.
+    #
+    #   This parameter is optional. However, if you do not pass any session
+    #   policies, then the resulting federated user session has no
+    #   permissions. The only exception is when the credentials are used to
+    #   access a resource that has a resource-based policy that specifically
+    #   references the federated user session in the `Principal` element of
+    #   the policy.
+    #
+    #   When you pass session policies, the session permissions are the
+    #   intersection of the IAM user policies and the session policies that
+    #   you pass. This gives you a way to further restrict the permissions for
+    #   a federated user. You cannot use session policies to grant more
+    #   permissions than those that are defined in the permissions policy of
+    #   the IAM user. For more information, see [Session Policies][1] in the
+    #   *IAM User Guide*.
     #
-    #   The format for this parameter, as described by its regex pattern, is a
-    #   string of characters up to 2048 characters in length. The characters
+    #   The plain text that you use for both inline and managed session
+    #   policies shouldn't exceed 2048 characters. The JSON policy characters
     #   can be any ASCII character from the space character to the end of the
-    #   valid character list (\\u0020-\\u00FF). It can also include the tab
-    #   (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
+    #   valid character list (\\u0020 through \\u00FF). It can also include
+    #   the tab (\\u0009), linefeed (\\u000A), and carriage return (\\u000D)
     #   characters.
     #
-    #   <note markdown="1"> The policy plain text must be 2048 bytes or shorter. However, an
-    #   internal conversion compresses it into a packed binary format with a
-    #   separate limit. The PackedPolicySize response element indicates by
-    #   percentage how close to the upper size limit the policy is, with 100%
-    #   equaling the maximum allowed size.
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
     #
     #    </note>
     #
-    #   For more information about how permissions work, see [Permissions for
-    #   GetFederationToken][1].
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
+    #
+    # @option params [Array<Types::PolicyDescriptorType>] :policy_arns
+    #   The Amazon Resource Names (ARNs) of the IAM managed policies that you
+    #   want to use as a managed session policy. The policies must exist in
+    #   the same account as the IAM user that is requesting federated access.
+    #
+    #   You must pass an inline or managed [session policy][1] to this
+    #   operation. You can pass a single JSON policy document to use as an
+    #   inline session policy. You can also specify up to 10 managed policies
+    #   to use as managed session policies. The plain text that you use for
+    #   both inline and managed session policies shouldn't exceed 2048
+    #   characters. You can provide up to 10 managed policy ARNs. For more
+    #   information about ARNs, see [Amazon Resource Names (ARNs) and AWS
+    #   Service Namespaces](general/latest/gr/aws-arns-and-namespaces.html) in
+    #   the AWS General Reference.
+    #
+    #   This parameter is optional. However, if you do not pass any session
+    #   policies, then the resulting federated user session has no
+    #   permissions. The only exception is when the credentials are used to
+    #   access a resource that has a resource-based policy that specifically
+    #   references the federated user session in the `Principal` element of
+    #   the policy.
+    #
+    #   When you pass session policies, the session permissions are the
+    #   intersection of the IAM user policies and the session policies that
+    #   you pass. This gives you a way to further restrict the permissions for
+    #   a federated user. You cannot use session policies to grant more
+    #   permissions than those that are defined in the permissions policy of
+    #   the IAM user. For more information, see [Session Policies][1] in the
+    #   *IAM User Guide*.
+    #
+    #   <note markdown="1"> The characters in this parameter count towards the 2048 character
+    #   session policy guideline. However, an AWS conversion compresses the
+    #   session policies into a packed binary format that has a separate
+    #   limit. This is the enforced limit. The `PackedPolicySize` response
+    #   element indicates by percentage how close the policy is to the upper
+    #   size limit.
+    #
+    #    </note>
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_getfederationtoken.html
+    #   [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session
     #
     # @option params [Integer] :duration_seconds
     #   The duration, in seconds, that the session should last. Acceptable
     #   durations for federation sessions range from 900 seconds (15 minutes)
-    #   to 129600 seconds (36 hours), with 43200 seconds (12 hours) as the
-    #   default. Sessions obtained using AWS account (root) credentials are
-    #   restricted to a maximum of 3600 seconds (one hour). If the specified
-    #   duration is longer than one hour, the session obtained by using AWS
-    #   account (root) credentials defaults to one hour.
+    #   to 129,600 seconds (36 hours), with 43,200 seconds (12 hours) as the
+    #   default. Sessions obtained using AWS account root user credentials are
+    #   restricted to a maximum of 3,600 seconds (one hour). If the specified
+    #   duration is longer than one hour, the session obtained by using root
+    #   user credentials defaults to one hour.
     #
     # @return [Types::GetFederationTokenResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -1337,7 +1526,7 @@ module Aws::STS
     #   resp = client.get_federation_token({
     #     duration_seconds: 3600, 
     #     name: "Bob", 
-    #     policy: "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"Stmt1\",\"Effect\":\"Allow\",\"Action\":\"s3:*\",\"Resource\":\"*\"}]}", 
+    #     policy: "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"Stmt1\",\"Effect\":\"Allow\",\"Action\":\"s3:ListAllMyBuckets\",\"Resource\":\"*\"}]}", 
     #   })
     #
     #   resp.to_h outputs the following:
@@ -1360,6 +1549,11 @@ module Aws::STS
     #   resp = client.get_federation_token({
     #     name: "userNameType", # required
     #     policy: "sessionPolicyDocumentType",
+    #     policy_arns: [
+    #       {
+    #         arn: "arnType",
+    #       },
+    #     ],
     #     duration_seconds: 1,
     #   })
     #
@@ -1385,50 +1579,51 @@ module Aws::STS
     # Returns a set of temporary credentials for an AWS account or IAM user.
     # The credentials consist of an access key ID, a secret access key, and
     # a security token. Typically, you use `GetSessionToken` if you want to
-    # use MFA to protect programmatic calls to specific AWS APIs like Amazon
-    # EC2 `StopInstances`. MFA-enabled IAM users would need to call
-    # `GetSessionToken` and submit an MFA code that is associated with their
-    # MFA device. Using the temporary security credentials that are returned
-    # from the call, IAM users can then make programmatic calls to APIs that
-    # require MFA authentication. If you do not supply a correct MFA code,
-    # then the API returns an access denied error. For a comparison of
-    # `GetSessionToken` with the other APIs that produce temporary
-    # credentials, see [Requesting Temporary Security Credentials][1] and
-    # [Comparing the AWS STS APIs][2] in the *IAM User Guide*.
-    #
-    # The `GetSessionToken` action must be called by using the long-term AWS
-    # security credentials of the AWS account or an IAM user. Credentials
-    # that are created by IAM users are valid for the duration that you
-    # specify, from 900 seconds (15 minutes) up to a maximum of 129600
-    # seconds (36 hours), with a default of 43200 seconds (12 hours);
-    # credentials that are created by using account credentials can range
-    # from 900 seconds (15 minutes) up to a maximum of 3600 seconds (1
-    # hour), with a default of 1 hour.
+    # use MFA to protect programmatic calls to specific AWS API operations
+    # like Amazon EC2 `StopInstances`. MFA-enabled IAM users would need to
+    # call `GetSessionToken` and submit an MFA code that is associated with
+    # their MFA device. Using the temporary security credentials that are
+    # returned from the call, IAM users can then make programmatic calls to
+    # API operations that require MFA authentication. If you do not supply a
+    # correct MFA code, then the API returns an access denied error. For a
+    # comparison of `GetSessionToken` with the other API operations that
+    # produce temporary credentials, see [Requesting Temporary Security
+    # Credentials][1] and [Comparing the AWS STS API operations][2] in the
+    # *IAM User Guide*.
+    #
+    # The `GetSessionToken` operation must be called by using the long-term
+    # AWS security credentials of the AWS account root user or an IAM user.
+    # Credentials that are created by IAM users are valid for the duration
+    # that you specify. This duration can range from 900 seconds (15
+    # minutes) up to a maximum of 129,600 seconds (36 hours), with a default
+    # of 43,200 seconds (12 hours). Credentials based on account credentials
+    # can range from 900 seconds (15 minutes) up to 3,600 seconds (1 hour),
+    # with a default of 1 hour.
     #
     # The temporary security credentials created by `GetSessionToken` can be
     # used to make API calls to any AWS service with the following
     # exceptions:
     #
-    # * You cannot call any IAM APIs unless MFA authentication information
-    #   is included in the request.
+    # * You cannot call any IAM API operations unless MFA authentication
+    #   information is included in the request.
     #
     # * You cannot call any STS API *except* `AssumeRole` or
     #   `GetCallerIdentity`.
     #
-    # <note markdown="1"> We recommend that you do not call `GetSessionToken` with root account
-    # credentials. Instead, follow our [best practices][3] by creating one
-    # or more IAM users, giving them the necessary permissions, and using
-    # IAM users for everyday interaction with AWS.
+    # <note markdown="1"> We recommend that you do not call `GetSessionToken` with AWS account
+    # root user credentials. Instead, follow our [best practices][3] by
+    # creating one or more IAM users, giving them the necessary permissions,
+    # and using IAM users for everyday interaction with AWS.
     #
     #  </note>
     #
-    # The permissions associated with the temporary security credentials
-    # returned by `GetSessionToken` are based on the permissions associated
-    # with account or IAM user whose credentials are used to call the
-    # action. If `GetSessionToken` is called using root account credentials,
-    # the temporary credentials have root account permissions. Similarly, if
-    # `GetSessionToken` is called using the credentials of an IAM user, the
-    # temporary credentials have the same permissions as the IAM user.
+    # The credentials that are returned by `GetSessionToken` are based on
+    # permissions associated with the user whose credentials were used to
+    # call the operation. If `GetSessionToken` is called using AWS account
+    # root user credentials, the temporary credentials have root user
+    # permissions. Similarly, if `GetSessionToken` is called using the
+    # credentials of an IAM user, the temporary credentials have the same
+    # permissions as the IAM user.
     #
     # For more information about using `GetSessionToken` to create temporary
     # credentials, go to [Temporary Credentials for Users in Untrusted
@@ -1436,18 +1631,18 @@ module Aws::STS
     #
     #
     #
-    # [1]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
-    # [2]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
-    # [3]: http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#create-iam-users
-    # [4]: http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getsessiontoken
+    # [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
+    # [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison
+    # [3]: https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#create-iam-users
+    # [4]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#api_getsessiontoken
     #
     # @option params [Integer] :duration_seconds
     #   The duration, in seconds, that the credentials should remain valid.
     #   Acceptable durations for IAM user sessions range from 900 seconds (15
-    #   minutes) to 129600 seconds (36 hours), with 43200 seconds (12 hours)
+    #   minutes) to 129,600 seconds (36 hours), with 43,200 seconds (12 hours)
     #   as the default. Sessions for AWS account owners are restricted to a
-    #   maximum of 3600 seconds (one hour). If the duration is longer than one
-    #   hour, the session for AWS account owners defaults to one hour.
+    #   maximum of 3,600 seconds (one hour). If the duration is longer than
+    #   one hour, the session for AWS account owners defaults to one hour.
     #
     # @option params [String] :serial_number
     #   The identification number of the MFA device that is associated with
@@ -1459,7 +1654,7 @@ module Aws::STS
     #   device for an IAM user by going to the AWS Management Console and
     #   viewing the user's security credentials.
     #
-    #   The regex used to validated this parameter is a string of characters
+    #   The regex used to validate this parameter is a string of characters
     #   consisting of upper- and lower-case alphanumeric characters with no
     #   spaces. You can also include underscores or any of the following
     #   characters: =,.@:/-
@@ -1467,9 +1662,9 @@ module Aws::STS
     # @option params [String] :token_code
     #   The value provided by the MFA device, if MFA is required. If any
     #   policy requires the IAM user to submit an MFA code, specify this
-    #   value. If MFA authentication is required, and the user does not
-    #   provide a code when requesting a set of temporary security
-    #   credentials, the user will receive an "access denied" response when
+    #   value. If MFA authentication is required, the user must provide a code
+    #   when requesting a set of temporary security credentials. A user who
+    #   fails to provide the code receives an "access denied" response when
     #   requesting resources that require MFA authentication.
     #
     #   The format for this parameter, as described by its regex pattern, is a
@@ -1535,7 +1730,7 @@ module Aws::STS
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-core'
-      context[:gem_version] = '3.39.0'
+      context[:gem_version] = '3.54.2'
       Seahorse::Client::Request.new(handlers, context)
     end