aws-sdk-secretsmanager 1.52.0 → 1.56.0

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

@@ -27,6 +27,7 @@ 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/http_checksum.rb'
+require 'aws-sdk-core/plugins/defaults_mode.rb'
 require 'aws-sdk-core/plugins/signature_v4.rb'
 require 'aws-sdk-core/plugins/protocols/json_rpc.rb'
 
@@ -73,6 +74,7 @@ module Aws::SecretsManager
     add_plugin(Aws::Plugins::ClientMetricsSendPlugin)
     add_plugin(Aws::Plugins::TransferEncoding)
     add_plugin(Aws::Plugins::HttpChecksum)
+    add_plugin(Aws::Plugins::DefaultsMode)
     add_plugin(Aws::Plugins::SignatureV4)
     add_plugin(Aws::Plugins::Protocols::JsonRpc)
 
@@ -119,7 +121,9 @@ module Aws::SecretsManager
     #     * EC2/ECS IMDS instance profile - When used by default, the timeouts
     #       are very aggressive. Construct and pass an instance of
     #       `Aws::InstanceProfileCredentails` or `Aws::ECSCredentials` to
-    #       enable retries and extended timeouts.
+    #       enable retries and extended timeouts. Instance profile credential
+    #       fetching can be disabled by setting ENV['AWS_EC2_METADATA_DISABLED']
+    #       to true.
     #
     #   @option options [required, String] :region
     #     The AWS region to connect to.  The configured `:region` is
@@ -173,6 +177,10 @@ module Aws::SecretsManager
     #     Used only in `standard` and adaptive retry modes. Specifies whether to apply
     #     a clock skew correction and retry requests with skewed client clocks.
     #
+    #   @option options [String] :defaults_mode ("legacy")
+    #     See {Aws::DefaultsModeConfiguration} for a list of the
+    #     accepted modes and the configuration defaults that are included.
+    #
     #   @option options [Boolean] :disable_host_prefix_injection (false)
     #     Set to true to disable SDK automatically adding host prefix
     #     to default service endpoint when available.
@@ -305,7 +313,7 @@ module Aws::SecretsManager
     #     seconds to wait when opening a HTTP session before raising a
     #     `Timeout::Error`.
     #
-    #   @option options [Integer] :http_read_timeout (60) The default
+    #   @option options [Float] :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.
     #
@@ -321,6 +329,9 @@ module Aws::SecretsManager
     #     disables this behaviour.  This value can safely be set per
     #     request on the session.
     #
+    #   @option options [Float] :ssl_timeout (nil) Sets the SSL timeout
+    #     in seconds.
+    #
     #   @option options [Boolean] :http_wire_trace (false) When `true`,
     #     HTTP debug output will be sent to the `:logger`.
     #
@@ -346,60 +357,32 @@ module Aws::SecretsManager
 
     # @!group API Operations
 
-    # Disables automatic scheduled rotation and cancels the rotation of a
-    # secret if currently in progress.
-    #
-    # To re-enable scheduled rotation, call RotateSecret with
-    # `AutomaticallyRotateAfterDays` set to a value greater than 0. This
-    # immediately rotates your secret and then enables the automatic
-    # schedule.
-    #
-    # <note markdown="1"> If you cancel a rotation while in progress, it can leave the
-    # `VersionStage` labels in an unexpected state. Depending on the step of
-    # the rotation in progress, you might need to remove the staging label
-    # `AWSPENDING` from the partially created version, specified by the
-    # `VersionId` response value. You should also evaluate the partially
-    # rotated new version to see if it should be deleted, which you can do
-    # by removing all staging labels from the new version `VersionStage`
-    # field.
-    #
-    #  </note>
-    #
-    # To successfully start a rotation, the staging label `AWSPENDING` must
-    # be in one of the following states:
-    #
-    # * Not attached to any version at all
-    #
-    # * Attached to the same version as the staging label `AWSCURRENT`
+    # Turns off automatic rotation, and if a rotation is currently in
+    # progress, cancels the rotation.
     #
-    # If the staging label `AWSPENDING` attached to a different version than
-    # the version with `AWSCURRENT` then the attempt to rotate fails.
+    # To turn on automatic rotation again, call RotateSecret.
     #
-    # **Minimum permissions**
+    # <note markdown="1"> If you cancel a rotation in progress, it can leave the `VersionStage`
+    # labels in an unexpected state. Depending on the step of the rotation
+    # in progress, you might need to remove the staging label `AWSPENDING`
+    # from the partially created version, specified by the `VersionId`
+    # response value. We recommend you also evaluate the partially rotated
+    # new version to see if it should be deleted. You can delete a version
+    # by removing all staging labels from it.
     #
-    # To run this command, you must have the following permissions:
-    #
-    # * secretsmanager:CancelRotateSecret
-    #
-    # ^
-    #
-    # **Related operations**
+    #  </note>
     #
-    # * To configure rotation for a secret or to manually trigger a
-    #   rotation, use RotateSecret.
+    # <b>Required permissions: </b> `secretsmanager:CancelRotateSecret`. For
+    # more information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # * To get the rotation configuration details for a secret, use
-    #   DescribeSecret.
     #
-    # * To list all of the currently available secrets, use ListSecrets.
     #
-    # * To list all of the versions currently associated with a secret, use
-    #   ListSecretVersionIds.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret to cancel a rotation request. You can specify
-    #   either the Amazon Resource Name (ARN) or the friendly name of the
-    #   secret.
+    #   The ARN or name of the secret.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -448,119 +431,70 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Creates a new secret. A secret in Secrets Manager consists of both the
-    # protected secret data and the important information needed to manage
-    # the secret.
-    #
-    # Secrets Manager stores the encrypted secret data in one of a
-    # collection of "versions" associated with the secret. Each version
-    # contains a copy of the encrypted secret data. Each version is
-    # associated with one or more "staging labels" that identify where the
-    # version is in the rotation cycle. The `SecretVersionsToStages` field
-    # of the secret contains the mapping of staging labels to the active
-    # versions of the secret. Versions without a staging label are
-    # considered deprecated and not included in the list.
-    #
-    # You provide the secret data to be encrypted by putting text in either
-    # the `SecretString` parameter or binary data in the `SecretBinary`
+    # Creates a new secret. A *secret* is a set of credentials, such as a
+    # user name and password, that you store in an encrypted form in Secrets
+    # Manager. The secret also includes the connection information to access
+    # a database or other service, which Secrets Manager doesn't encrypt. A
+    # secret in Secrets Manager consists of both the protected secret data
+    # and the important information needed to manage the secret.
+    #
+    # For information about creating a secret in the console, see [Create a
+    # secret][1].
+    #
+    # To create a secret, you can provide the secret value to be encrypted
+    # in either the `SecretString` parameter or the `SecretBinary`
     # parameter, but not both. If you include `SecretString` or
-    # `SecretBinary` then Secrets Manager also creates an initial secret
-    # version and automatically attaches the staging label `AWSCURRENT` to
-    # the new version.
-    #
-    # <note markdown="1"> * If you call an operation to encrypt or decrypt the `SecretString` or
-    #   `SecretBinary` for a secret in the same account as the calling user
-    #   and that secret doesn't specify a Amazon Web Services KMS
-    #   encryption key, Secrets Manager uses the account's default Amazon
-    #   Web Services managed customer master key (CMK) with the alias
-    #   `aws/secretsmanager`. If this key doesn't already exist in your
-    #   account then Secrets Manager creates it for you automatically. All
-    #   users and roles in the same Amazon Web Services account
-    #   automatically have access to use the default CMK. Note that if an
-    #   Secrets Manager API call results in Amazon Web Services creating the
-    #   account's Amazon Web Services-managed CMK, it can result in a
-    #   one-time significant delay in returning the result.
-    #
-    # * If the secret resides in a different Amazon Web Services account
-    #   from the credentials calling an API that requires encryption or
-    #   decryption of the secret value then you must create and use a custom
-    #   Amazon Web Services KMS CMK because you can't access the default
-    #   CMK for the account using credentials from a different Amazon Web
-    #   Services account. Store the ARN of the CMK in the secret when you
-    #   create the secret or when you update it by including it in the
-    #   `KMSKeyId`. If you call an API that must encrypt or decrypt
-    #   `SecretString` or `SecretBinary` using credentials from a different
-    #   account then the Amazon Web Services KMS key policy must grant
-    #   cross-account access to that other account's user or role for both
-    #   the kms:GenerateDataKey and kms:Decrypt operations.
+    # `SecretBinary` then Secrets Manager creates an initial secret version
+    # and automatically attaches the staging label `AWSCURRENT` to it.
     #
-    #  </note>
-    #
-    #
-    #
-    # **Minimum permissions**
+    # If you don't specify an KMS encryption key, Secrets Manager uses the
+    # Amazon Web Services managed key `aws/secretsmanager`. If this key
+    # doesn't already exist in your account, then Secrets Manager creates
+    # it for you automatically. All users and roles in the Amazon Web
+    # Services account automatically have access to use
+    # `aws/secretsmanager`. Creating `aws/secretsmanager` can result in a
+    # one-time significant delay in returning the result.
     #
-    # To run this command, you must have the following permissions:
+    # If the secret is in a different Amazon Web Services account from the
+    # credentials calling the API, then you can't use `aws/secretsmanager`
+    # to encrypt the secret, and you must create and use a customer managed
+    # KMS key.
     #
-    # * secretsmanager:CreateSecret
+    # <b>Required permissions: </b> `secretsmanager:CreateSecret`. For more
+    # information, see [ IAM policy actions for Secrets Manager][2] and
+    # [Authentication and access control in Secrets Manager][3].
     #
-    # * kms:GenerateDataKey - needed only if you use a customer-managed
-    #   Amazon Web Services KMS key to encrypt the secret. You do not need
-    #   this permission to use the account default Amazon Web Services
-    #   managed CMK for Secrets Manager.
-    #
-    # * kms:Decrypt - needed only if you use a customer-managed Amazon Web
-    #   Services KMS key to encrypt the secret. You do not need this
-    #   permission to use the account default Amazon Web Services managed
-    #   CMK for Secrets Manager.
-    #
-    # * secretsmanager:TagResource - needed only if you include the `Tags`
-    #   parameter.
     #
-    # **Related operations**
     #
-    # * To delete a secret, use DeleteSecret.
-    #
-    # * To modify an existing secret, use UpdateSecret.
-    #
-    # * To create a new version of a secret, use PutSecretValue.
-    #
-    # * To retrieve the encrypted secure string and secure binary values,
-    #   use GetSecretValue.
-    #
-    # * To retrieve all other details for a secret, use DescribeSecret. This
-    #   does not include the encrypted secure string and secure binary
-    #   values.
-    #
-    # * To retrieve the list of secret versions associated with the current
-    #   secret, use DescribeSecret and examine the `SecretVersionsToStages`
-    #   response value.
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_create-basic-secret.html
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :name
-    #   Specifies the friendly name of the new secret.
+    #   The name of the new secret.
     #
-    #   The secret name must be ASCII letters, digits, or the following
-    #   characters : /\_+=.@-
+    #   The secret name can contain ASCII letters, numbers, and the following
+    #   characters: /\_+=.@-
     #
-    #   <note markdown="1"> Do not end your secret name with a hyphen followed by six characters.
+    #   Do not end your secret name with a hyphen followed by six characters.
     #   If you do so, you risk confusion and unexpected results when searching
     #   for a secret by partial ARN. Secrets Manager automatically adds a
-    #   hyphen and six random characters at the end of the ARN.
-    #
-    #    </note>
+    #   hyphen and six random characters after the secret name at the end of
+    #   the ARN.
     #
     # @option params [String] :client_request_token
-    #   (Optional) If you include `SecretString` or `SecretBinary`, then an
-    #   initial version is created as part of the secret, and this parameter
-    #   specifies a unique identifier for the new version.
+    #   If you include `SecretString` or `SecretBinary`, then Secrets Manager
+    #   creates an initial version for the secret, and this parameter
+    #   specifies the unique identifier for the new version.
     #
     #   <note markdown="1"> If you use the Amazon Web Services CLI or one of the Amazon Web
-    #   Services SDK to call this operation, then you can leave this parameter
-    #   empty. The CLI or SDK generates a random UUID for you and includes it
-    #   as the value for this parameter in the request. If you don't use the
-    #   SDK and instead generate a raw HTTP request to the Secrets Manager
-    #   service endpoint, then you must generate a `ClientRequestToken`
-    #   yourself for the new version and include the value in the request.
+    #   Services SDKs to call this operation, then you can leave this
+    #   parameter empty. The CLI or SDK generates a random UUID for you and
+    #   includes it as the value for this parameter in the request. If you
+    #   don't use the SDK and instead generate a raw HTTP request to the
+    #   Secrets Manager service endpoint, then you must generate a
+    #   `ClientRequestToken` yourself for the new version and include the
+    #   value in the request.
     #
     #    </note>
     #
@@ -593,99 +527,79 @@ module Aws::SecretsManager
     #   [1]: https://wikipedia.org/wiki/Universally_unique_identifier
     #
     # @option params [String] :description
-    #   (Optional) Specifies a user-provided description of the secret.
+    #   The description of the secret.
     #
     # @option params [String] :kms_key_id
-    #   (Optional) Specifies the ARN, Key ID, or alias of the Amazon Web
-    #   Services KMS customer master key (CMK) to be used to encrypt the
-    #   `SecretString` or `SecretBinary` values in the versions stored in this
-    #   secret.
+    #   The ARN, key ID, or alias of the KMS key that Secrets Manager uses to
+    #   encrypt the secret value in the secret.
     #
-    #   You can specify any of the supported ways to identify a Amazon Web
-    #   Services KMS key ID. If you need to reference a CMK in a different
-    #   account, you can use only the key ARN or the alias ARN.
+    #   To use a KMS key in a different account, use the key ARN or the alias
+    #   ARN.
     #
-    #   If you don't specify this value, then Secrets Manager defaults to
-    #   using the Amazon Web Services account's default CMK (the one named
-    #   `aws/secretsmanager`). If a Amazon Web Services KMS CMK with that name
-    #   doesn't yet exist, then Secrets Manager creates it for you
-    #   automatically the first time it needs to encrypt a version's
-    #   `SecretString` or `SecretBinary` fields.
+    #   If you don't specify this value, then Secrets Manager uses the key
+    #   `aws/secretsmanager`. If that key doesn't yet exist, then Secrets
+    #   Manager creates it for you automatically the first time it encrypts
+    #   the secret value.
     #
-    #   You can use the account default CMK to encrypt and decrypt only if you
-    #   call this operation using credentials from the same account that owns
-    #   the secret. If the secret resides in a different account, then you
-    #   must create a custom CMK and specify the ARN in this field.
+    #   If the secret is in a different Amazon Web Services account from the
+    #   credentials calling the API, then you can't use `aws/secretsmanager`
+    #   to encrypt the secret, and you must create and use a customer managed
+    #   KMS key.
     #
     # @option params [String, StringIO, File] :secret_binary
-    #   (Optional) Specifies binary data that you want to encrypt and store in
-    #   the new version of the secret. To use this parameter in the
-    #   command-line tools, we recommend that you store your binary data in a
-    #   file and then use the appropriate technique for your tool to pass the
-    #   contents of the file as a parameter.
+    #   The binary data to encrypt and store in the new version of the secret.
+    #   We recommend that you store your binary data in a file and then pass
+    #   the contents of the file as a parameter.
     #
     #   Either `SecretString` or `SecretBinary` must have a value, but not
-    #   both. They cannot both be empty.
+    #   both.
     #
-    #   This parameter is not available using the Secrets Manager console. It
-    #   can be accessed only by using the Amazon Web Services CLI or one of
-    #   the Amazon Web Services SDKs.
+    #   This parameter is not available in the Secrets Manager console.
     #
     # @option params [String] :secret_string
-    #   (Optional) Specifies text data that you want to encrypt and store in
-    #   this new version of the secret.
+    #   The text data to encrypt and store in this new version of the secret.
+    #   We recommend you use a JSON structure of key/value pairs for your
+    #   secret value.
     #
     #   Either `SecretString` or `SecretBinary` must have a value, but not
-    #   both. They cannot both be empty.
+    #   both.
     #
     #   If you create a secret by using the Secrets Manager console then
     #   Secrets Manager puts the protected secret text in only the
     #   `SecretString` parameter. The Secrets Manager console stores the
-    #   information as a JSON structure of key/value pairs that the Lambda
-    #   rotation function knows how to parse.
-    #
-    #   For storing multiple values, we recommend that you use a JSON text
-    #   string argument and specify key/value pairs. For more information, see
-    #   [Specifying parameter values for the Amazon Web Services CLI][1] in
-    #   the Amazon Web Services CLI User Guide.
-    #
-    #
-    #
-    #   [1]: https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters.html
+    #   information as a JSON structure of key/value pairs that a Lambda
+    #   rotation function can parse.
     #
     # @option params [Array<Types::Tag>] :tags
-    #   (Optional) Specifies a list of user-defined tags that are attached to
-    #   the secret. Each tag is a "Key" and "Value" pair of strings. This
-    #   operation only appends tags to the existing list of tags. To remove
-    #   tags, you must use UntagResource.
-    #
-    #   * Secrets Manager tag key names are case sensitive. A tag with the key
-    #     "ABC" is a different tag from one with key "abc".
+    #   A list of tags to attach to the secret. Each tag is a key and value
+    #   pair of strings in a JSON text string, for example:
     #
-    #   * If you check tags in IAM policy `Condition` elements as part of your
-    #     security strategy, then adding or removing a tag can change
-    #     permissions. If the successful completion of this operation would
-    #     result in you losing your permissions for this secret, then this
-    #     operation is blocked and returns an `Access Denied` error.
+    #   `[\{"Key":"CostCenter","Value":"12345"\},\{"Key":"environment","Value":"production"\}]`
     #
-    #   This parameter requires a JSON text string argument. For information
-    #   on how to format a JSON parameter for the various command line tool
-    #   environments, see [Using JSON for Parameters][1] in the *CLI User
-    #   Guide*. For example:
+    #   Secrets Manager tag key names are case sensitive. A tag with the key
+    #   "ABC" is a different tag from one with key "abc".
     #
-    #   `[\{"Key":"CostCenter","Value":"12345"\},\{"Key":"environment","Value":"production"\}]`
+    #   If you check tags in permissions policies as part of your security
+    #   strategy, then adding or removing a tag can change permissions. If the
+    #   completion of this operation would result in you losing your
+    #   permissions for this secret, then Secrets Manager blocks the operation
+    #   and returns an `Access Denied` error. For more information, see
+    #   [Control access to secrets using tags][1] and [Limit access to
+    #   identities with tags that match secrets' tags][2].
     #
-    #   If your command-line tool or SDK requires quotation marks around the
+    #   For information about how to format a JSON parameter for the various
+    #   command line tool environments, see [Using JSON for Parameters][3]. If
+    #   your command-line tool or SDK requires quotation marks around the
     #   parameter, you should use single quotes to avoid confusion with the
     #   double quotes required in the JSON text.
     #
-    #   The following basic restrictions apply to tags:
+    #   The following restrictions apply to tags:
     #
-    #   * Maximum number of tags per secret—50
+    #   * Maximum number of tags per secret: 50
     #
-    #   * Maximum key length—127 Unicode characters in UTF-8
+    #   * Maximum key length: 127 Unicode characters in UTF-8
     #
-    #   * Maximum value length—255 Unicode characters in UTF-8
+    #   * Maximum value length: 255 Unicode characters in UTF-8
     #
     #   * Tag keys and values are case sensitive.
     #
@@ -695,23 +609,23 @@ module Aws::SecretsManager
     #     with this prefix do not count against your tags per secret limit.
     #
     #   * If you use your tagging schema across multiple services and
-    #     resources, remember other services might have restrictions on
-    #     allowed characters. Generally allowed characters: letters, spaces,
-    #     and numbers representable in UTF-8, plus the following special
+    #     resources, other services might have restrictions on allowed
+    #     characters. Generally allowed characters: letters, spaces, and
+    #     numbers representable in UTF-8, plus the following special
     #     characters: + - = . \_ : / @.
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/cli/latest/userguide/cli-using-param.html#cli-using-param-json
+    #   [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_examples.html#tag-secrets-abac
+    #   [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_examples.html#auth-and-access_tags2
+    #   [3]: https://docs.aws.amazon.com/cli/latest/userguide/cli-using-param.html#cli-using-param-json
     #
     # @option params [Array<Types::ReplicaRegionType>] :add_replica_regions
-    #   (Optional) Add a list of regions to replicate secrets. Secrets Manager
-    #   replicates the KMSKeyID objects to the list of regions specified in
-    #   the parameter.
+    #   A list of Regions and KMS keys to replicate secrets.
     #
     # @option params [Boolean] :force_overwrite_replica_secret
-    #   (Optional) If set, the replication overwrites a secret with the same
-    #   name in the destination region.
+    #   Specifies whether to overwrite a secret with the same name in the
+    #   destination Region.
     #
     # @return [Types::CreateSecretResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -786,28 +700,20 @@ module Aws::SecretsManager
     end
 
     # Deletes the resource-based permission policy attached to the secret.
+    # To attach a policy to a secret, use PutResourcePolicy.
     #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
-    #
-    # * secretsmanager:DeleteResourcePolicy
+    # <b>Required permissions: </b> `secretsmanager:DeleteResourcePolicy`.
+    # For more information, see [ IAM policy actions for Secrets Manager][1]
+    # and [Authentication and access control in Secrets Manager][2].
     #
-    # ^
     #
-    # **Related operations**
     #
-    # * To attach a resource policy to a secret, use PutResourcePolicy.
-    #
-    # * To retrieve the current resource-based policy attached to a secret,
-    #   use GetResourcePolicy.
-    #
-    # * To list all of the currently available secrets, use ListSecrets.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret that you want to delete the attached
-    #   resource-based policy for. You can specify either the Amazon Resource
-    #   Name (ARN) or the friendly name of the secret.
+    #   The ARN or name of the secret to delete the attached resource-based
+    #   policy for.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -852,86 +758,68 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Deletes an entire secret and all of the versions. You can optionally
-    # include a recovery window during which you can restore the secret. If
-    # you don't specify a recovery window value, the operation defaults to
-    # 30 days. Secrets Manager attaches a `DeletionDate` stamp to the secret
-    # that specifies the end of the recovery window. At the end of the
-    # recovery window, Secrets Manager deletes the secret permanently.
+    # Deletes a secret and all of its versions. You can specify a recovery
+    # window during which you can restore the secret. The minimum recovery
+    # window is 7 days. The default recovery window is 30 days. Secrets
+    # Manager attaches a `DeletionDate` stamp to the secret that specifies
+    # the end of the recovery window. At the end of the recovery window,
+    # Secrets Manager deletes the secret permanently.
     #
-    # At any time before recovery window ends, you can use RestoreSecret to
-    # remove the `DeletionDate` and cancel the deletion of the secret.
-    #
-    # You cannot access the encrypted secret information in any secret
-    # scheduled for deletion. If you need to access that information, you
-    # must cancel the deletion with RestoreSecret and then retrieve the
-    # information.
-    #
-    # <note markdown="1"> * There is no explicit operation to delete a version of a secret.
-    #   Instead, remove all staging labels from the `VersionStage` field of
-    #   a version. That marks the version as deprecated and allows Secrets
-    #   Manager to delete it as needed. Versions without any staging labels
-    #   do not show up in ListSecretVersionIds unless you specify
-    #   `IncludeDeprecated`.
-    #
-    # * The permanent secret deletion at the end of the waiting period is
-    #   performed as a background task with low priority. There is no
-    #   guarantee of a specific time after the recovery window for the
-    #   actual delete operation to occur.
-    #
-    #  </note>
+    # For information about deleting a secret in the console, see
+    # [https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage\_delete-secret.html][1].
     #
-    # **Minimum permissions**
+    # Secrets Manager performs the permanent secret deletion at the end of
+    # the waiting period as a background task with low priority. There is no
+    # guarantee of a specific time after the recovery window for the
+    # permanent delete to occur.
     #
-    # To run this command, you must have the following permissions:
+    # At any time before recovery window ends, you can use RestoreSecret to
+    # remove the `DeletionDate` and cancel the deletion of the secret.
     #
-    # * secretsmanager:DeleteSecret
+    # In a secret scheduled for deletion, you cannot access the encrypted
+    # secret value. To access that information, first cancel the deletion
+    # with RestoreSecret and then retrieve the information.
     #
-    # ^
+    # <b>Required permissions: </b> `secretsmanager:DeleteSecret`. For more
+    # information, see [ IAM policy actions for Secrets Manager][2] and
+    # [Authentication and access control in Secrets Manager][3].
     #
-    # **Related operations**
     #
-    # * To create a secret, use CreateSecret.
     #
-    # * To cancel deletion of a version of a secret before the recovery
-    #   window has expired, use RestoreSecret.
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_delete-secret.html
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret to delete. You can specify either the Amazon
-    #   Resource Name (ARN) or the friendly name of the secret.
+    #   The ARN or name of the secret to delete.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [Integer] :recovery_window_in_days
-    #   (Optional) Specifies the number of days that Secrets Manager waits
-    #   before Secrets Manager can delete the secret. You can't use both this
-    #   parameter and the `ForceDeleteWithoutRecovery` parameter in the same
-    #   API call.
-    #
-    #   This value can range from 7 to 30 days with a default value of 30.
+    #   The number of days from 7 to 30 that Secrets Manager waits before
+    #   permanently deleting the secret. You can't use both this parameter
+    #   and `ForceDeleteWithoutRecovery` in the same call. If you don't use
+    #   either, then Secrets Manager defaults to a 30 day recovery window.
     #
     # @option params [Boolean] :force_delete_without_recovery
-    #   (Optional) Specifies that the secret is to be deleted without any
-    #   recovery window. You can't use both this parameter and the
-    #   `RecoveryWindowInDays` parameter in the same API call.
+    #   Specifies whether to delete the secret without any recovery window.
+    #   You can't use both this parameter and `RecoveryWindowInDays` in the
+    #   same call. If you don't use either, then Secrets Manager defaults to
+    #   a 30 day recovery window.
     #
-    #   An asynchronous background process performs the actual deletion, so
-    #   there can be a short delay before the operation completes. If you
-    #   write code to delete and then immediately recreate a secret with the
-    #   same name, ensure that your code includes appropriate back off and
-    #   retry logic.
+    #   Secrets Manager performs the actual deletion with an asynchronous
+    #   background process, so there might be a short delay before the secret
+    #   is permanently deleted. If you delete a secret and then immediately
+    #   create a secret with the same name, use appropriate back off and retry
+    #   logic.
     #
     #   Use this parameter with caution. This parameter causes the operation
-    #   to skip the normal waiting period before the permanent deletion that
-    #   Amazon Web Services would normally impose with the
-    #   `RecoveryWindowInDays` parameter. If you delete a secret with the
-    #   `ForceDeleteWithouRecovery` parameter, then you have no opportunity to
-    #   recover the secret. You lose the secret permanently.
-    #
-    #   If you use this parameter and include a previously deleted or
-    #   nonexistent secret, the operation does not return the error
-    #   `ResourceNotFoundException` in order to correctly handle retries.
+    #   to skip the normal recovery window before the permanent deletion that
+    #   Secrets Manager would normally impose with the `RecoveryWindowInDays`
+    #   parameter. If you delete a secret with the `ForceDeleteWithouRecovery`
+    #   parameter, then you have no opportunity to recover the secret. You
+    #   lose the secret permanently.
     #
     # @return [Types::DeleteSecretResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -982,33 +870,20 @@ module Aws::SecretsManager
     end
 
     # Retrieves the details of a secret. It does not include the encrypted
-    # fields. Secrets Manager only returns fields populated with a value in
+    # secret value. Secrets Manager only returns fields that have a value in
     # the response.
     #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
-    #
-    # * secretsmanager:DescribeSecret
-    #
-    # ^
+    # <b>Required permissions: </b> `secretsmanager:DescribeSecret`. For
+    # more information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # **Related operations**
     #
-    # * To create a secret, use CreateSecret.
     #
-    # * To modify a secret, use UpdateSecret.
-    #
-    # * To retrieve the encrypted secret information in a version of the
-    #   secret, use GetSecretValue.
-    #
-    # * To list all of the secrets in the Amazon Web Services account, use
-    #   ListSecrets.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   The identifier of the secret whose details you want to retrieve. You
-    #   can specify either the Amazon Resource Name (ARN) or the friendly name
-    #   of the secret.
+    #   The ARN or name of the secret.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -1091,6 +966,8 @@ module Aws::SecretsManager
     #   resp.rotation_enabled #=> Boolean
     #   resp.rotation_lambda_arn #=> String
     #   resp.rotation_rules.automatically_after_days #=> Integer
+    #   resp.rotation_rules.duration #=> String
+    #   resp.rotation_rules.schedule_expression #=> String
     #   resp.last_rotated_date #=> Time
     #   resp.last_changed_date #=> Time
     #   resp.last_accessed_date #=> Time
@@ -1120,66 +997,54 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Generates a random password of the specified complexity. This
-    # operation is intended for use in the Lambda rotation function. Per
-    # best practice, we recommend that you specify the maximum length and
-    # include every character type that the system you are generating a
-    # password for can support.
+    # Generates a random password. We recommend that you specify the maximum
+    # length and include every character type that the system you are
+    # generating a password for can support.
     #
-    # **Minimum permissions**
+    # <b>Required permissions: </b> `secretsmanager:GetRandomPassword`. For
+    # more information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # To run this command, you must have the following permissions:
     #
-    # * secretsmanager:GetRandomPassword
     #
-    # ^
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [Integer] :password_length
-    #   The desired length of the generated password. The default value if you
-    #   do not include this parameter is 32 characters.
+    #   The length of the password. If you don't include this parameter, the
+    #   default length is 32 characters.
     #
     # @option params [String] :exclude_characters
-    #   A string that includes characters that should not be included in the
-    #   generated password. The default is that all characters from the
-    #   included sets can be used.
+    #   A string of the characters that you don't want in the password.
     #
     # @option params [Boolean] :exclude_numbers
-    #   Specifies that the generated password should not include digits. The
-    #   default if you do not include this switch parameter is that digits can
-    #   be included.
+    #   Specifies whether to exclude numbers from the password. If you don't
+    #   include this switch, the password can contain numbers.
     #
     # @option params [Boolean] :exclude_punctuation
-    #   Specifies that the generated password should not include punctuation
-    #   characters. The default if you do not include this switch parameter is
-    #   that punctuation characters can be included.
-    #
-    #   The following are the punctuation characters that *can* be included in
-    #   the generated password if you don't explicitly exclude them with
-    #   `ExcludeCharacters` or `ExcludePunctuation`\:
-    #
-    #   `` ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` \{ | \} ~
-    #   ``
+    #   Specifies whether to exclude the following punctuation characters from
+    #   the password: `` ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _
+    #   ` \{ | \} ~ ``. If you don't include this switch, the password can
+    #   contain punctuation.
     #
     # @option params [Boolean] :exclude_uppercase
-    #   Specifies that the generated password should not include uppercase
-    #   letters. The default if you do not include this switch parameter is
-    #   that uppercase letters can be included.
+    #   Specifies whether to exclude uppercase letters from the password. If
+    #   you don't include this switch, the password can contain uppercase
+    #   letters.
     #
     # @option params [Boolean] :exclude_lowercase
-    #   Specifies that the generated password should not include lowercase
-    #   letters. The default if you do not include this switch parameter is
-    #   that lowercase letters can be included.
+    #   Specifies whether to exclude lowercase letters from the password. If
+    #   you don't include this switch, the password can contain lowercase
+    #   letters.
     #
     # @option params [Boolean] :include_space
-    #   Specifies that the generated password can include the space character.
-    #   The default if you do not include this switch parameter is that the
-    #   space character is not included.
+    #   Specifies whether to include the space character. If you include this
+    #   switch, the password can contain space characters.
     #
     # @option params [Boolean] :require_each_included_type
-    #   A boolean value that specifies whether the generated password must
-    #   include at least one of every allowed character type. The default
-    #   value is `True` and the operation requires at least one of every
-    #   character type.
+    #   Specifies whether to include at least one upper and lowercase letter,
+    #   one number, and one punctuation. If you don't include this switch,
+    #   the password contains at least one of every character type.
     #
     # @return [Types::GetRandomPasswordResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -1229,31 +1094,23 @@ module Aws::SecretsManager
     end
 
     # Retrieves the JSON text of the resource-based policy document attached
-    # to the specified secret. The JSON request string input and response
-    # output displays formatted code with white space and line breaks for
-    # better readability. Submit your input as a single line JSON string.
-    #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
+    # to the secret. For more information about permissions policies
+    # attached to a secret, see [Permissions policies attached to a
+    # secret][1].
     #
-    # * secretsmanager:GetResourcePolicy
+    # <b>Required permissions: </b> `secretsmanager:GetResourcePolicy`. For
+    # more information, see [ IAM policy actions for Secrets Manager][2] and
+    # [Authentication and access control in Secrets Manager][3].
     #
-    # ^
     #
-    # **Related operations**
     #
-    # * To attach a resource policy to a secret, use PutResourcePolicy.
-    #
-    # * To delete the resource-based policy attached to a secret, use
-    #   DeleteResourcePolicy.
-    #
-    # * To list all of the currently available secrets, use ListSecrets.
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_resource-policies.html
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret that you want to retrieve the attached
-    #   resource-based policy for. You can specify either the Amazon Resource
-    #   Name (ARN) or the friendly name of the secret.
+    #   The ARN or name of the secret to retrieve the attached resource-based
+    #   policy for.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -1305,40 +1162,35 @@ module Aws::SecretsManager
     # `SecretBinary` from the specified version of a secret, whichever
     # contains content.
     #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
-    #
-    # * secretsmanager:GetSecretValue
+    # We recommend that you cache your secret values by using client-side
+    # caching. Caching secrets improves speed and reduces your costs. For
+    # more information, see [Cache secrets for your applications][1].
     #
-    # * kms:Decrypt - required only if you use a customer-managed Amazon Web
-    #   Services KMS key to encrypt the secret. You do not need this
-    #   permission to use the account's default Amazon Web Services managed
-    #   CMK for Secrets Manager.
+    # <b>Required permissions: </b> `secretsmanager:GetSecretValue`. If the
+    # secret is encrypted using a customer-managed key instead of the Amazon
+    # Web Services managed key `aws/secretsmanager`, then you also need
+    # `kms:Decrypt` permissions for that key. For more information, see [
+    # IAM policy actions for Secrets Manager][2] and [Authentication and
+    # access control in Secrets Manager][3].
     #
-    # **Related operations**
     #
-    # * To create a new version of the secret with different encrypted
-    #   information, use PutSecretValue.
     #
-    # * To retrieve the non-encrypted details for the secret, use
-    #   DescribeSecret.
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieving-secrets.html
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret containing the version that you want to retrieve.
-    #   You can specify either the Amazon Resource Name (ARN) or the friendly
-    #   name of the secret.
+    #   The ARN or name of the secret to retrieve.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [String] :version_id
-    #   Specifies the unique identifier of the version of the secret that you
-    #   want to retrieve. If you specify both this parameter and
-    #   `VersionStage`, the two parameters must refer to the same secret
-    #   version. If you don't specify either a `VersionStage` or `VersionId`
-    #   then the default is to perform the operation on the version with the
-    #   `VersionStage` value of `AWSCURRENT`.
+    #   The unique identifier of the version of the secret to retrieve. If you
+    #   include both this parameter and `VersionStage`, the two parameters
+    #   must refer to the same secret version. If you don't specify either a
+    #   `VersionStage` or `VersionId`, then Secrets Manager returns the
+    #   `AWSCURRENT` version.
     #
     #   This value is typically a [UUID-type][1] value with 32 hexadecimal
     #   digits.
@@ -1348,15 +1200,13 @@ module Aws::SecretsManager
     #   [1]: https://wikipedia.org/wiki/Universally_unique_identifier
     #
     # @option params [String] :version_stage
-    #   Specifies the secret version that you want to retrieve by the staging
-    #   label attached to the version.
+    #   The staging label of the version of the secret to retrieve.
     #
-    #   Staging labels are used to keep track of different versions during the
-    #   rotation process. If you specify both this parameter and `VersionId`,
-    #   the two parameters must refer to the same secret version . If you
-    #   don't specify either a `VersionStage` or `VersionId`, then the
-    #   default is to perform the operation on the version with the
-    #   `VersionStage` value of `AWSCURRENT`.
+    #   Secrets Manager uses staging labels to keep track of different
+    #   versions during the rotation process. If you include both this
+    #   parameter and `VersionId`, the two parameters must refer to the same
+    #   secret version. If you don't specify either a `VersionStage` or
+    #   `VersionId`, Secrets Manager returns the `AWSCURRENT` version.
     #
     # @return [Types::GetSecretValueResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -1420,66 +1270,44 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Lists all of the versions attached to the specified secret. The output
-    # does not include the `SecretString` or `SecretBinary` fields. By
-    # default, the list includes only versions that have at least one
-    # staging label in `VersionStage` attached.
-    #
-    # <note markdown="1"> Always check the `NextToken` response parameter when calling any of
-    # the `List*` operations. These operations can occasionally return an
-    # empty or shorter than expected list of results even when there more
-    # results become available. When this happens, the `NextToken` response
-    # parameter contains a value to pass to the next call to the same API to
-    # request the next part of the list.
-    #
-    #  </note>
-    #
-    # **Minimum permissions**
+    # Lists the versions for a secret.
     #
-    # To run this command, you must have the following permissions:
+    # To list the secrets in the account, use ListSecrets.
     #
-    # * secretsmanager:ListSecretVersionIds
+    # To get the secret value from `SecretString` or `SecretBinary`, call
+    # GetSecretValue.
     #
-    # ^
+    # <b>Required permissions: </b> `secretsmanager:ListSecretVersionIds`.
+    # For more information, see [ IAM policy actions for Secrets Manager][1]
+    # and [Authentication and access control in Secrets Manager][2].
     #
-    # **Related operations**
     #
-    # * To list the secrets in an account, use ListSecrets.
     #
-    # ^
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   The identifier for the secret containing the versions you want to
-    #   list. You can specify either the Amazon Resource Name (ARN) or the
-    #   friendly name of the secret.
+    #   The ARN or name of the secret whose versions you want to list.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [Integer] :max_results
-    #   (Optional) Limits the number of results you want to include in the
-    #   response. If you don't include this parameter, it defaults to a value
-    #   that's specific to the operation. If additional items exist beyond
-    #   the maximum you specify, the `NextToken` response element is present
-    #   and has a value (isn't null). Include that value as the `NextToken`
-    #   request parameter in the next call to the operation to get the next
-    #   part of the results. Note that Secrets Manager might return fewer
-    #   results than the maximum even when there are more results available.
-    #   You should check `NextToken` after every operation to ensure that you
-    #   receive all of the results.
+    #   The number of results to include in the response.
+    #
+    #   If there are more results available, in the response, Secrets Manager
+    #   includes `NextToken`. To get the next results, call
+    #   `ListSecretVersionIds` again with the value from `NextToken`.
     #
     # @option params [String] :next_token
-    #   (Optional) Use this parameter in a request if you receive a
-    #   `NextToken` response in a previous request indicating there's more
-    #   output available. In a subsequent call, set it to the value of the
-    #   previous call `NextToken` response to indicate where the output should
-    #   continue from.
+    #   A token that indicates where the output should continue from, if a
+    #   previous call did not show all results. To get the next results, call
+    #   `ListSecretVersionIds` again with this value.
     #
     # @option params [Boolean] :include_deprecated
-    #   (Optional) Specifies that you want the results to include versions
-    #   that do not have any staging labels attached to them. Such versions
-    #   are considered deprecated and are subject to deletion by Secrets
-    #   Manager as needed.
+    #   Specifies whether to include versions of secrets that don't have any
+    #   staging labels attached to them. Versions without staging labels are
+    #   considered deprecated and are subject to deletion by Secrets Manager.
     #
     # @return [Types::ListSecretVersionIdsResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -1559,56 +1387,41 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Lists all of the secrets that are stored by Secrets Manager in the
-    # Amazon Web Services account. To list the versions currently stored for
-    # a specific secret, use ListSecretVersionIds. The encrypted fields
-    # `SecretString` and `SecretBinary` are not included in the output. To
-    # get that information, call the GetSecretValue operation.
-    #
-    # <note markdown="1"> Always check the `NextToken` response parameter when calling any of
-    # the `List*` operations. These operations can occasionally return an
-    # empty or shorter than expected list of results even when there more
-    # results become available. When this happens, the `NextToken` response
-    # parameter contains a value to pass to the next call to the same API to
-    # request the next part of the list.
-    #
-    #  </note>
+    # Lists the secrets that are stored by Secrets Manager in the Amazon Web
+    # Services account.
     #
-    # **Minimum permissions**
+    # To list the versions of a secret, use ListSecretVersionIds.
     #
-    # To run this command, you must have the following permissions:
+    # To get the secret value from `SecretString` or `SecretBinary`, call
+    # GetSecretValue.
     #
-    # * secretsmanager:ListSecrets
+    # For information about finding secrets in the console, see [Enhanced
+    # search capabilities for secrets in Secrets Manager][1].
     #
-    # ^
+    # <b>Required permissions: </b> `secretsmanager:ListSecrets`. For more
+    # information, see [ IAM policy actions for Secrets Manager][2] and
+    # [Authentication and access control in Secrets Manager][3].
     #
-    # **Related operations**
     #
-    # * To list the versions attached to a secret, use ListSecretVersionIds.
     #
-    # ^
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_search-secret.html
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [Integer] :max_results
-    #   (Optional) Limits the number of results you want to include in the
-    #   response. If you don't include this parameter, it defaults to a value
-    #   that's specific to the operation. If additional items exist beyond
-    #   the maximum you specify, the `NextToken` response element is present
-    #   and has a value (isn't null). Include that value as the `NextToken`
-    #   request parameter in the next call to the operation to get the next
-    #   part of the results. Note that Secrets Manager might return fewer
-    #   results than the maximum even when there are more results available.
-    #   You should check `NextToken` after every operation to ensure that you
-    #   receive all of the results.
+    #   The number of results to include in the response.
+    #
+    #   If there are more results available, in the response, Secrets Manager
+    #   includes `NextToken`. To get the next results, call `ListSecrets`
+    #   again with the value from `NextToken`.
     #
     # @option params [String] :next_token
-    #   (Optional) Use this parameter in a request if you receive a
-    #   `NextToken` response in a previous request indicating there's more
-    #   output available. In a subsequent call, set it to the value of the
-    #   previous call `NextToken` response to indicate where the output should
-    #   continue from.
+    #   A token that indicates where the output should continue from, if a
+    #   previous call did not show all results. To get the next results, call
+    #   `ListSecrets` again with this value.
     #
     # @option params [Array<Types::Filter>] :filters
-    #   Lists the secret request filters.
+    #   The filters to apply to the list of secrets.
     #
     # @option params [String] :sort_order
     #   Lists secrets in the requested order.
@@ -1680,6 +1493,8 @@ module Aws::SecretsManager
     #   resp.secret_list[0].rotation_enabled #=> Boolean
     #   resp.secret_list[0].rotation_lambda_arn #=> String
     #   resp.secret_list[0].rotation_rules.automatically_after_days #=> Integer
+    #   resp.secret_list[0].rotation_rules.duration #=> String
+    #   resp.secret_list[0].rotation_rules.schedule_expression #=> String
     #   resp.secret_list[0].last_rotated_date #=> Time
     #   resp.secret_list[0].last_changed_date #=> Time
     #   resp.secret_list[0].last_accessed_date #=> Time
@@ -1704,65 +1519,42 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Attaches the contents of the specified resource-based permission
-    # policy to a secret. A resource-based policy is optional.
-    # Alternatively, you can use IAM identity-based policies that specify
-    # the secret's Amazon Resource Name (ARN) in the policy statement's
-    # `Resources` element. You can also use a combination of both
-    # identity-based and resource-based policies. The affected users and
-    # roles receive the permissions that are permitted by all of the
-    # relevant policies. For more information, see [Using Resource-Based
-    # Policies for Amazon Web Services Secrets Manager][1]. For the complete
-    # description of the Amazon Web Services policy syntax and grammar, see
-    # [IAM JSON Policy Reference][2] in the *IAM User Guide*.
-    #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
+    # Attaches a resource-based permission policy to a secret. A
+    # resource-based policy is optional. For more information, see
+    # [Authentication and access control for Secrets Manager][1]
     #
-    # * secretsmanager:PutResourcePolicy
+    # For information about attaching a policy in the console, see [Attach a
+    # permissions policy to a secret][2].
     #
-    # ^
+    # <b>Required permissions: </b> `secretsmanager:PutResourcePolicy`. For
+    # more information, see [ IAM policy actions for Secrets Manager][3] and
+    # [Authentication and access control in Secrets Manager][1].
     #
-    # **Related operations**
     #
-    # * To retrieve the resource policy attached to a secret, use
-    #   GetResourcePolicy.
     #
-    # * To delete the resource-based policy attached to a secret, use
-    #   DeleteResourcePolicy.
-    #
-    # * To list all of the currently available secrets, use ListSecrets.
-    #
-    #
-    #
-    # [1]: http://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_resource-based-policies.html
-    # [2]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_resource-based-policies.html
+    # [3]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret that you want to attach the resource-based
-    #   policy. You can specify either the ARN or the friendly name of the
-    #   secret.
+    #   The ARN or name of the secret to attach the resource-based policy.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [required, String] :resource_policy
-    #   A JSON-formatted string constructed according to the grammar and
-    #   syntax for an Amazon Web Services resource-based policy. The policy in
-    #   the string identifies who can access or manage this secret and its
-    #   versions. For information on how to format a JSON parameter for the
-    #   various command line tool environments, see [Using JSON for
-    #   Parameters][1] in the *CLI User Guide*.
+    #   A JSON-formatted string for an Amazon Web Services resource-based
+    #   policy. For example policies, see [Permissions policy examples][1].
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/cli/latest/userguide/cli-using-param.html#cli-using-param-json
+    #   [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_examples.html
     #
     # @option params [Boolean] :block_public_policy
-    #   (Optional) If you set the parameter, `BlockPublicPolicy` to true, then
-    #   you block resource-based policies that allow broad access to the
-    #   secret.
+    #   Specifies whether to block resource-based policies that allow broad
+    #   access to the secret. By default, Secrets Manager blocks policies that
+    #   allow broad access, for example those that use a wildcard for the
+    #   principal.
     #
     # @return [Types::PutResourcePolicyResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -1807,11 +1599,9 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Stores a new encrypted secret value in the specified secret. To do
-    # this, the operation creates a new version and attaches it to the
-    # secret. The version can contain a new `SecretString` value or a new
-    # `SecretBinary` value. You can also specify the staging labels that are
-    # initially attached to the new version.
+    # Creates a new version with a new encrypted secret value and attaches
+    # it to the secret. The version can contain a new `SecretString` value
+    # or a new `SecretBinary` value.
     #
     # We recommend you avoid calling `PutSecretValue` at a sustained rate of
     # more than once every 10 minutes. When you update the secret value,
@@ -1822,116 +1612,73 @@ module Aws::SecretsManager
     # versions than Secrets Manager removes, and you will reach the quota
     # for secret versions.
     #
-    # * If this operation creates the first version for the secret then
-    #   Secrets Manager automatically attaches the staging label
-    #   `AWSCURRENT` to the new version.
-    #
-    # * If you do not specify a value for VersionStages then Secrets Manager
-    #   automatically moves the staging label `AWSCURRENT` to this new
-    #   version.
-    #
-    # * If this operation moves the staging label `AWSCURRENT` from another
-    #   version to this version, then Secrets Manager also automatically
-    #   moves the staging label `AWSPREVIOUS` to the version that
-    #   `AWSCURRENT` was removed from.
-    #
-    # * This operation is idempotent. If a version with a `VersionId` with
-    #   the same value as the `ClientRequestToken` parameter already exists
-    #   and you specify the same secret data, the operation succeeds but
-    #   does nothing. However, if the secret data is different, then the
-    #   operation fails because you cannot modify an existing version; you
-    #   can only create new ones.
-    #
-    # <note markdown="1"> * If you call an operation to encrypt or decrypt the `SecretString` or
-    #   `SecretBinary` for a secret in the same account as the calling user
-    #   and that secret doesn't specify a Amazon Web Services KMS
-    #   encryption key, Secrets Manager uses the account's default Amazon
-    #   Web Services managed customer master key (CMK) with the alias
-    #   `aws/secretsmanager`. If this key doesn't already exist in your
-    #   account then Secrets Manager creates it for you automatically. All
-    #   users and roles in the same Amazon Web Services account
-    #   automatically have access to use the default CMK. Note that if an
-    #   Secrets Manager API call results in Amazon Web Services creating the
-    #   account's Amazon Web Services-managed CMK, it can result in a
-    #   one-time significant delay in returning the result.
-    #
-    # * If the secret resides in a different Amazon Web Services account
-    #   from the credentials calling an API that requires encryption or
-    #   decryption of the secret value then you must create and use a custom
-    #   Amazon Web Services KMS CMK because you can't access the default
-    #   CMK for the account using credentials from a different Amazon Web
-    #   Services account. Store the ARN of the CMK in the secret when you
-    #   create the secret or when you update it by including it in the
-    #   `KMSKeyId`. If you call an API that must encrypt or decrypt
-    #   `SecretString` or `SecretBinary` using credentials from a different
-    #   account then the Amazon Web Services KMS key policy must grant
-    #   cross-account access to that other account's user or role for both
-    #   the kms:GenerateDataKey and kms:Decrypt operations.
-    #
-    #  </note>
-    #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
+    # You can specify the staging labels to attach to the new version in
+    # `VersionStages`. If you don't include `VersionStages`, then Secrets
+    # Manager automatically moves the staging label `AWSCURRENT` to this
+    # version. If this operation creates the first version for the secret,
+    # then Secrets Manager automatically attaches the staging label
+    # `AWSCURRENT` to it .
     #
-    # * secretsmanager:PutSecretValue
+    # If this operation moves the staging label `AWSCURRENT` from another
+    # version to this version, then Secrets Manager also automatically moves
+    # the staging label `AWSPREVIOUS` to the version that `AWSCURRENT` was
+    # removed from.
     #
-    # * kms:GenerateDataKey - needed only if you use a customer-managed
-    #   Amazon Web Services KMS key to encrypt the secret. You do not need
-    #   this permission to use the account's default Amazon Web Services
-    #   managed CMK for Secrets Manager.
+    # This operation is idempotent. If a version with a `VersionId` with the
+    # same value as the `ClientRequestToken` parameter already exists, and
+    # you specify the same secret data, the operation succeeds but does
+    # nothing. However, if the secret data is different, then the operation
+    # fails because you can't modify an existing version; you can only
+    # create new ones.
     #
-    # **Related operations**
+    # <b>Required permissions: </b> `secretsmanager:PutSecretValue`. For
+    # more information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # * To retrieve the encrypted value you store in the version of a
-    #   secret, use GetSecretValue.
     #
-    # * To create a secret, use CreateSecret.
     #
-    # * To get the details for a secret, use DescribeSecret.
-    #
-    # * To list the versions attached to a secret, use ListSecretVersionIds.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret to which you want to add a new version. You can
-    #   specify either the Amazon Resource Name (ARN) or the friendly name of
-    #   the secret. The secret must already exist.
+    #   The ARN or name of the secret to add a new version to.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
+    #   If the secret doesn't already exist, use `CreateSecret` instead.
+    #
     # @option params [String] :client_request_token
-    #   (Optional) Specifies a unique identifier for the new version of the
-    #   secret.
+    #   A unique identifier for the new version of the secret.
     #
     #   <note markdown="1"> If you use the Amazon Web Services CLI or one of the Amazon Web
-    #   Services SDK to call this operation, then you can leave this parameter
-    #   empty. The CLI or SDK generates a random UUID for you and includes
-    #   that in the request. If you don't use the SDK and instead generate a
-    #   raw HTTP request to the Secrets Manager service endpoint, then you
-    #   must generate a `ClientRequestToken` yourself for new versions and
-    #   include that value in the request.
+    #   Services SDKs to call this operation, then you can leave this
+    #   parameter empty because they generate a random UUID for you. If you
+    #   don't use the SDK and instead generate a raw HTTP request to the
+    #   Secrets Manager service endpoint, then you must generate a
+    #   `ClientRequestToken` yourself for new versions and include that value
+    #   in the request.
     #
     #    </note>
     #
     #   This value helps ensure idempotency. Secrets Manager uses this value
     #   to prevent the accidental creation of duplicate versions if there are
-    #   failures and retries during the Lambda rotation function's
-    #   processing. We recommend that you generate a [UUID-type][1] value to
-    #   ensure uniqueness within the specified secret.
+    #   failures and retries during the Lambda rotation function processing.
+    #   We recommend that you generate a [UUID-type][1] value to ensure
+    #   uniqueness within the specified secret.
     #
     #   * If the `ClientRequestToken` value isn't already associated with a
     #     version of the secret then a new version of the secret is created.
     #
     #   * If a version with this value already exists and that version's
     #     `SecretString` or `SecretBinary` values are the same as those in the
-    #     request then the request is ignored (the operation is idempotent).
+    #     request then the request is ignored. The operation is idempotent.
     #
     #   * If a version with this value already exists and the version of the
     #     `SecretString` and `SecretBinary` values are different from those in
-    #     the request then the request fails because you cannot modify an
-    #     existing secret version. You can only create new versions to store
-    #     new secret values.
+    #     the request, then the request fails because you can't modify a
+    #     secret version. You can only create new versions to store new secret
+    #     values.
     #
     #   This value becomes the `VersionId` of the new version.
     #
@@ -1943,52 +1690,37 @@ module Aws::SecretsManager
     #   [1]: https://wikipedia.org/wiki/Universally_unique_identifier
     #
     # @option params [String, StringIO, File] :secret_binary
-    #   (Optional) Specifies binary data that you want to encrypt and store in
-    #   the new version of the secret. To use this parameter in the
-    #   command-line tools, we recommend that you store your binary data in a
-    #   file and then use the appropriate technique for your tool to pass the
-    #   contents of the file as a parameter. Either `SecretBinary` or
-    #   `SecretString` must have a value, but not both. They cannot both be
-    #   empty.
+    #   The binary data to encrypt and store in the new version of the secret.
+    #   To use this parameter in the command-line tools, we recommend that you
+    #   store your binary data in a file and then pass the contents of the
+    #   file as a parameter.
     #
-    #   This parameter is not accessible if the secret using the Secrets
-    #   Manager console.
+    #   You must include `SecretBinary` or `SecretString`, but not both.
     #
-    # @option params [String] :secret_string
-    #   (Optional) Specifies text data that you want to encrypt and store in
-    #   this new version of the secret. Either `SecretString` or
-    #   `SecretBinary` must have a value, but not both. They cannot both be
-    #   empty.
-    #
-    #   If you create this secret by using the Secrets Manager console then
-    #   Secrets Manager puts the protected secret text in only the
-    #   `SecretString` parameter. The Secrets Manager console stores the
-    #   information as a JSON structure of key/value pairs that the default
-    #   Lambda rotation function knows how to parse.
-    #
-    #   For storing multiple values, we recommend that you use a JSON text
-    #   string argument and specify key/value pairs. For more information, see
-    #   [Specifying parameter values for the Amazon Web Services CLI][1] in
-    #   the Amazon Web Services CLI User Guide.
+    #   You can't access this value from the Secrets Manager console.
     #
+    # @option params [String] :secret_string
+    #   The text to encrypt and store in the new version of the secret.
     #
+    #   You must include `SecretBinary` or `SecretString`, but not both.
     #
-    #   [1]: https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters.html
+    #   We recommend you create the secret string as JSON key/value pairs, as
+    #   shown in the example.
     #
     # @option params [Array<String>] :version_stages
-    #   (Optional) Specifies a list of staging labels that are attached to
-    #   this version of the secret. These staging labels are used to track the
-    #   versions through the rotation process by the Lambda rotation function.
-    #
-    #   A staging label must be unique to a single version of the secret. If
-    #   you specify a staging label that's already associated with a
-    #   different version of the same secret then that staging label is
-    #   automatically removed from the other version and attached to this
-    #   version.
+    #   A list of staging labels to attach to this version of the secret.
+    #   Secrets Manager uses staging labels to track versions of a secret
+    #   through the rotation process.
     #
-    #   If you do not specify a value for `VersionStages` then Secrets Manager
-    #   automatically moves the staging label `AWSCURRENT` to this new
-    #   version.
+    #   If you specify a staging label that's already associated with a
+    #   different version of the same secret, then Secrets Manager removes the
+    #   label from the other version and attaches it to this version. If you
+    #   specify `AWSCURRENT`, and it is already attached to another version,
+    #   then Secrets Manager also moves the staging label `AWSPREVIOUS` to the
+    #   version that `AWSCURRENT` was removed from.
+    #
+    #   If you don't include `VersionStages`, then Secrets Manager
+    #   automatically moves the staging label `AWSCURRENT` to this version.
     #
     # @return [Types::PutSecretValueResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -2046,13 +1778,24 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Remove regions from replication.
+    # For a secret that is replicated to other Regions, deletes the secret
+    # replicas from the Regions you specify.
+    #
+    # <b>Required permissions: </b>
+    # `secretsmanager:RemoveRegionsFromReplication`. For more information,
+    # see [ IAM policy actions for Secrets Manager][1] and [Authentication
+    # and access control in Secrets Manager][2].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Remove a secret by `SecretId` from replica Regions.
+    #   The ARN or name of the secret.
     #
     # @option params [required, Array<String>] :remove_replica_regions
-    #   Remove replication from specific Regions.
+    #   The Regions of the replicas to remove.
     #
     # @return [Types::RemoveRegionsFromReplicationResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -2085,18 +1828,28 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Converts an existing secret to a multi-Region secret and begins
-    # replication the secret to a list of new regions.
+    # Replicates the secret to a new Regions. See [Multi-Region secrets][1].
+    #
+    # <b>Required permissions: </b>
+    # `secretsmanager:ReplicateSecretToRegions`. For more information, see [
+    # IAM policy actions for Secrets Manager][2] and [Authentication and
+    # access control in Secrets Manager][3].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/create-manage-multi-region-secrets.html
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Use the `Secret Id` to replicate a secret to regions.
+    #   The ARN or name of the secret to replicate.
     #
     # @option params [required, Array<Types::ReplicaRegionType>] :add_replica_regions
-    #   Add Regions to replicate the secret.
+    #   A list of Regions in which to replicate the secret.
     #
     # @option params [Boolean] :force_overwrite_replica_secret
-    #   (Optional) If set, Secrets Manager replication overwrites a secret
-    #   with the same name in the destination region.
+    #   Specifies whether to overwrite a secret with the same name in the
+    #   destination Region.
     #
     # @return [Types::ReplicateSecretToRegionsResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -2136,27 +1889,20 @@ module Aws::SecretsManager
     end
 
     # Cancels the scheduled deletion of a secret by removing the
-    # `DeletedDate` time stamp. This makes the secret accessible to query
-    # once again.
-    #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
+    # `DeletedDate` time stamp. You can access a secret again after it has
+    # been restored.
     #
-    # * secretsmanager:RestoreSecret
+    # <b>Required permissions: </b> `secretsmanager:RestoreSecret`. For more
+    # information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # ^
     #
-    # **Related operations**
     #
-    # * To delete a secret, use DeleteSecret.
-    #
-    # ^
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret that you want to restore from a previously
-    #   scheduled deletion. You can specify either the Amazon Resource Name
-    #   (ARN) or the friendly name of the secret.
+    #   The ARN or name of the secret to restore.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -2201,82 +1947,57 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Configures and starts the asynchronous process of rotating this
-    # secret. If you include the configuration parameters, the operation
-    # sets those values for the secret and then immediately starts a
-    # rotation. If you do not include the configuration parameters, the
-    # operation starts a rotation with the values already stored in the
-    # secret. After the rotation completes, the protected service and its
-    # clients all use the new version of the secret.
-    #
-    # This required configuration information includes the ARN of an Amazon
-    # Web Services Lambda function and optionally, the time between
-    # scheduled rotations. The Lambda rotation function creates a new
-    # version of the secret and creates or updates the credentials on the
-    # protected service to match. After testing the new credentials, the
-    # function marks the new secret with the staging label `AWSCURRENT` so
-    # that your clients all immediately begin to use the new version. For
-    # more information about rotating secrets and how to configure a Lambda
-    # function to rotate the secrets for your protected service, see
-    # [Rotating Secrets in Amazon Web Services Secrets Manager][1] in the
-    # *Amazon Web Services Secrets Manager User Guide*.
-    #
-    # Secrets Manager schedules the next rotation when the previous one
-    # completes. Secrets Manager schedules the date by adding the rotation
-    # interval (number of days) to the actual date of the last rotation. The
-    # service chooses the hour within that 24-hour date window randomly. The
-    # minute is also chosen somewhat randomly, but weighted towards the top
-    # of the hour and influenced by a variety of factors that help
-    # distribute load.
-    #
-    # The rotation function must end with the versions of the secret in one
-    # of two states:
-    #
-    # * The `AWSPENDING` and `AWSCURRENT` staging labels are attached to the
-    #   same version of the secret, or
-    #
-    # * The `AWSPENDING` staging label is not attached to any version of the
-    #   secret.
+    # Configures and starts the asynchronous process of rotating the secret.
+    #
+    # If you include the configuration parameters, the operation sets the
+    # values for the secret and then immediately starts a rotation. If you
+    # don't include the configuration parameters, the operation starts a
+    # rotation with the values already stored in the secret. For more
+    # information about rotation, see [Rotate secrets][1].
+    #
+    # To configure rotation, you include the ARN of an Amazon Web Services
+    # Lambda function and the schedule for the rotation. The Lambda rotation
+    # function creates a new version of the secret and creates or updates
+    # the credentials on the database or service to match. After testing the
+    # new credentials, the function marks the new secret version with the
+    # staging label `AWSCURRENT`. Then anyone who retrieves the secret gets
+    # the new version. For more information, see [How rotation works][2].
+    #
+    # When rotation is successful, the `AWSPENDING` staging label might be
+    # attached to the same version as the `AWSCURRENT` version, or it might
+    # not be attached to any version.
     #
     # If the `AWSPENDING` staging label is present but not attached to the
-    # same version as `AWSCURRENT` then any later invocation of
+    # same version as `AWSCURRENT`, then any later invocation of
     # `RotateSecret` assumes that a previous rotation request is still in
     # progress and returns an error.
     #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
-    #
-    # * secretsmanager:RotateSecret
-    #
-    # * lambda:InvokeFunction (on the function specified in the secret's
-    #   metadata)
-    #
-    # **Related operations**
-    #
-    # * To list the secrets in your account, use ListSecrets.
-    #
-    # * To get the details for a version of a secret, use DescribeSecret.
-    #
-    # * To create a new version of a secret, use CreateSecret.
-    #
-    # * To attach staging labels to or remove staging labels from a version
-    #   of a secret, use UpdateSecretVersionStage.
+    # <b>Required permissions: </b> `secretsmanager:RotateSecret`. For more
+    # information, see [ IAM policy actions for Secrets Manager][3] and
+    # [Authentication and access control in Secrets Manager][4]. You also
+    # need `lambda:InvokeFunction` permissions on the rotation function. For
+    # more information, see [ Permissions for rotation][5].
     #
     #
     #
     # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotating-secrets.html
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotate-secrets_how.html
+    # [3]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [4]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
+    # [5]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotating-secrets-required-permissions-function.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret that you want to rotate. You can specify either
-    #   the Amazon Resource Name (ARN) or the friendly name of the secret.
+    #   The ARN or name of the secret to rotate.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [String] :client_request_token
-    #   (Optional) Specifies a unique identifier for the new version of the
-    #   secret that helps ensure idempotency.
+    #   A unique identifier for the new version of the secret that helps
+    #   ensure idempotency. Secrets Manager uses this value to prevent the
+    #   accidental creation of duplicate versions if there are failures and
+    #   retries during rotation. This value becomes the `VersionId` of the new
+    #   version.
     #
     #   If you use the Amazon Web Services CLI or one of the Amazon Web
     #   Services SDK to call this operation, then you can leave this parameter
@@ -2286,15 +2007,10 @@ module Aws::SecretsManager
     #   endpoint, then you must generate a `ClientRequestToken` yourself for
     #   new versions and include that value in the request.
     #
-    #   You only need to specify your own value if you implement your own
-    #   retry logic and want to ensure that a given secret is not created
-    #   twice. We recommend that you generate a [UUID-type][1] value to ensure
-    #   uniqueness within the specified secret.
-    #
-    #   Secrets Manager uses this value to prevent the accidental creation of
-    #   duplicate versions if there are failures and retries during the
-    #   function's processing. This value becomes the `VersionId` of the new
-    #   version.
+    #   You only need to specify this value if you implement your own retry
+    #   logic and you want to ensure that Secrets Manager doesn't attempt to
+    #   create a secret version twice. We recommend that you generate a
+    #   [UUID-type][1] value to ensure uniqueness within the specified secret.
     #
     #   **A suitable default value is auto-generated.** You should normally
     #   not need to pass this option.**
@@ -2304,12 +2020,28 @@ module Aws::SecretsManager
     #   [1]: https://wikipedia.org/wiki/Universally_unique_identifier
     #
     # @option params [String] :rotation_lambda_arn
-    #   (Optional) Specifies the ARN of the Lambda function that can rotate
-    #   the secret.
+    #   The ARN of the Lambda rotation function that can rotate the secret.
     #
     # @option params [Types::RotationRulesType] :rotation_rules
     #   A structure that defines the rotation configuration for this secret.
     #
+    # @option params [Boolean] :rotate_immediately
+    #   Specifies whether to rotate the secret immediately or wait until the
+    #   next scheduled rotation window. The rotation schedule is defined in
+    #   RotateSecretRequest$RotationRules.
+    #
+    #   If you don't immediately rotate the secret, Secrets Manager tests the
+    #   rotation configuration by running the [ `testSecret` step][1] of the
+    #   Lambda rotation function. The test creates an `AWSPENDING` version of
+    #   the secret and then removes it.
+    #
+    #   If you don't specify this value, then by default, Secrets Manager
+    #   rotates the secret immediately.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotate-secrets_how.html
+    #
     # @return [Types::RotateSecretResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::RotateSecretResponse#arn #arn} => String
@@ -2324,7 +2056,10 @@ module Aws::SecretsManager
     #     rotation_lambda_arn: "RotationLambdaARNType",
     #     rotation_rules: {
     #       automatically_after_days: 1,
+    #       duration: "DurationType",
+    #       schedule_expression: "ScheduleExpressionType",
     #     },
+    #     rotate_immediately: false,
     #   })
     #
     # @example Response structure
@@ -2342,12 +2077,24 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Removes the secret from replication and promotes the secret to a
-    # regional secret in the replica Region.
+    # Removes the link between the replica secret and the primary secret and
+    # promotes the replica to a primary secret in the replica Region.
+    #
+    # You must call this operation from the Region in which you want to
+    # promote the replica to a primary secret.
+    #
+    # <b>Required permissions: </b>
+    # `secretsmanager:StopReplicationToReplica`. For more information, see [
+    # IAM policy actions for Secrets Manager][1] and [Authentication and
+    # access control in Secrets Manager][2].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Response to `StopReplicationToReplica` of a secret, based on the
-    #   `SecretId`.
+    #   The ARN of the primary secret.
     #
     # @return [Types::StopReplicationToReplicaResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -2372,19 +2119,18 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Attaches one or more tags, each consisting of a key name and a value,
-    # to the specified secret. Tags are part of the secret's overall
-    # metadata, and are not associated with any specific version of the
-    # secret. This operation only appends tags to the existing list of tags.
-    # To remove tags, you must use UntagResource.
+    # Attaches tags to a secret. Tags consist of a key name and a value.
+    # Tags are part of the secret's metadata. They are not associated with
+    # specific versions of the secret. This operation appends tags to the
+    # existing list of tags.
     #
-    # The following basic restrictions apply to tags:
+    # The following restrictions apply to tags:
     #
-    # * Maximum number of tags per secret—50
+    # * Maximum number of tags per secret: 50
     #
-    # * Maximum key length—127 Unicode characters in UTF-8
+    # * Maximum key length: 127 Unicode characters in UTF-8
     #
-    # * Maximum value length—255 Unicode characters in UTF-8
+    # * Maximum value length: 255 Unicode characters in UTF-8
     #
     # * Tag keys and values are case sensitive.
     #
@@ -2394,9 +2140,9 @@ module Aws::SecretsManager
     #   with this prefix do not count against your tags per secret limit.
     #
     # * If you use your tagging schema across multiple services and
-    #   resources, remember other services might have restrictions on
-    #   allowed characters. Generally allowed characters: letters, spaces,
-    #   and numbers representable in UTF-8, plus the following special
+    #   resources, other services might have restrictions on allowed
+    #   characters. Generally allowed characters: letters, spaces, and
+    #   numbers representable in UTF-8, plus the following special
     #   characters: + - = . \_ : / @.
     #
     # If you use tags as part of your security strategy, then adding or
@@ -2404,34 +2150,26 @@ module Aws::SecretsManager
     # operation would result in you losing your permissions for this secret,
     # then the operation is blocked and returns an Access Denied error.
     #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
+    # <b>Required permissions: </b> `secretsmanager:TagResource`. For more
+    # information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # * secretsmanager:TagResource
     #
-    # ^
     #
-    # **Related operations**
-    #
-    # * To remove one or more tags from the collection attached to a secret,
-    #   use UntagResource.
-    #
-    # * To view the list of tags attached to a secret, use DescribeSecret.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   The identifier for the secret that you want to attach tags to. You can
-    #   specify either the Amazon Resource Name (ARN) or the friendly name of
-    #   the secret.
+    #   The identifier for the secret to attach tags to. You can specify
+    #   either the Amazon Resource Name (ARN) or the friendly name of the
+    #   secret.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [required, Array<Types::Tag>] :tags
-    #   The tags to attach to the secret. Each element in the list consists of
-    #   a `Key` and a `Value`.
-    #
-    #   This parameter to the API requires a JSON text string argument.
+    #   The tags to attach to the secret as a JSON text string argument. Each
+    #   element in the list consists of a `Key` and a `Value`.
     #
     #   For storing multiple values, we recommend that you use a JSON text
     #   string argument and specify key/value pairs. For more information, see
@@ -2485,7 +2223,7 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Removes one or more tags from the specified secret.
+    # Removes specific tags from a secret.
     #
     # This operation is idempotent. If a requested tag is not attached to
     # the secret, no error is returned and the secret metadata is unchanged.
@@ -2495,25 +2233,17 @@ module Aws::SecretsManager
     # would result in you losing your permissions for this secret, then the
     # operation is blocked and returns an Access Denied error.
     #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
+    # <b>Required permissions: </b> `secretsmanager:UntagResource`. For more
+    # information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2].
     #
-    # * secretsmanager:UntagResource
     #
-    # ^
     #
-    # **Related operations**
-    #
-    # * To add one or more tags to the collection attached to a secret, use
-    #   TagResource.
-    #
-    # * To view the list of tags attached to a secret, use DescribeSecret.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   The identifier for the secret that you want to remove tags from. You
-    #   can specify either the Amazon Resource Name (ARN) or the friendly name
-    #   of the secret.
+    #   The ARN or name of the secret.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -2522,7 +2252,7 @@ module Aws::SecretsManager
     #   A list of tag key names to remove from the secret. You don't specify
     #   the value. Both the key and its associated value are removed.
     #
-    #   This parameter to the API requires a JSON text string argument.
+    #   This parameter requires a JSON text string argument.
     #
     #   For storing multiple values, we recommend that you use a JSON text
     #   string argument and specify key/value pairs. For more information, see
@@ -2565,9 +2295,8 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Modifies many of the details of the specified secret.
-    #
-    # To change the secret value, you can also use PutSecretValue.
+    # Modifies the details of a secret, including metadata and the secret
+    # value. To change the secret value, you can also use PutSecretValue.
     #
     # To change the rotation configuration of a secret, use RotateSecret
     # instead.
@@ -2581,185 +2310,108 @@ module Aws::SecretsManager
     # you create more versions than Secrets Manager removes, and you will
     # reach the quota for secret versions.
     #
-    # <note markdown="1"> The Secrets Manager console uses only the `SecretString` parameter and
-    # therefore limits you to encrypting and storing only a text string. To
-    # encrypt and store binary data as part of the version of a secret, you
-    # must use either the Amazon Web Services CLI or one of the Amazon Web
-    # Services SDKs.
+    # If you include `SecretString` or `SecretBinary` to create a new secret
+    # version, Secrets Manager automatically attaches the staging label
+    # `AWSCURRENT` to the new version.
     #
-    #  </note>
-    #
-    # * If a version with a `VersionId` with the same value as the
-    #   `ClientRequestToken` parameter already exists, the operation results
-    #   in an error. You cannot modify an existing version, you can only
-    #   create a new version.
-    #
-    # * If you include `SecretString` or `SecretBinary` to create a new
-    #   secret version, Secrets Manager automatically attaches the staging
-    #   label `AWSCURRENT` to the new version.
-    #
-    # <note markdown="1"> * If you call an operation to encrypt or decrypt the `SecretString` or
-    #   `SecretBinary` for a secret in the same account as the calling user
-    #   and that secret doesn't specify a Amazon Web Services KMS
-    #   encryption key, Secrets Manager uses the account's default Amazon
-    #   Web Services managed customer master key (CMK) with the alias
-    #   `aws/secretsmanager`. If this key doesn't already exist in your
-    #   account then Secrets Manager creates it for you automatically. All
-    #   users and roles in the same Amazon Web Services account
-    #   automatically have access to use the default CMK. Note that if an
-    #   Secrets Manager API call results in Amazon Web Services creating the
-    #   account's Amazon Web Services-managed CMK, it can result in a
-    #   one-time significant delay in returning the result.
-    #
-    # * If the secret resides in a different Amazon Web Services account
-    #   from the credentials calling an API that requires encryption or
-    #   decryption of the secret value then you must create and use a custom
-    #   Amazon Web Services KMS CMK because you can't access the default
-    #   CMK for the account using credentials from a different Amazon Web
-    #   Services account. Store the ARN of the CMK in the secret when you
-    #   create the secret or when you update it by including it in the
-    #   `KMSKeyId`. If you call an API that must encrypt or decrypt
-    #   `SecretString` or `SecretBinary` using credentials from a different
-    #   account then the Amazon Web Services KMS key policy must grant
-    #   cross-account access to that other account's user or role for both
-    #   the kms:GenerateDataKey and kms:Decrypt operations.
-    #
-    #  </note>
-    #
-    # **Minimum permissions**
-    #
-    # To run this command, you must have the following permissions:
-    #
-    # * secretsmanager:UpdateSecret
+    # If you call this operation with a `VersionId` that matches an existing
+    # version's `ClientRequestToken`, the operation results in an error.
+    # You can't modify an existing version, you can only create a new
+    # version. To remove a version, remove all staging labels from it. See
+    # UpdateSecretVersionStage.
     #
-    # * kms:GenerateDataKey - needed only if you use a custom Amazon Web
-    #   Services KMS key to encrypt the secret. You do not need this
-    #   permission to use the account's Amazon Web Services managed CMK for
-    #   Secrets Manager.
+    # If you don't specify an KMS encryption key, Secrets Manager uses the
+    # Amazon Web Services managed key `aws/secretsmanager`. If this key
+    # doesn't already exist in your account, then Secrets Manager creates
+    # it for you automatically. All users and roles in the Amazon Web
+    # Services account automatically have access to use
+    # `aws/secretsmanager`. Creating `aws/secretsmanager` can result in a
+    # one-time significant delay in returning the result.
     #
-    # * kms:Decrypt - needed only if you use a custom Amazon Web Services
-    #   KMS key to encrypt the secret. You do not need this permission to
-    #   use the account's Amazon Web Services managed CMK for Secrets
-    #   Manager.
+    # If the secret is in a different Amazon Web Services account from the
+    # credentials calling the API, then you can't use `aws/secretsmanager`
+    # to encrypt the secret, and you must create and use a customer managed
+    # key.
     #
-    # **Related operations**
+    # <b>Required permissions: </b> `secretsmanager:UpdateSecret`. For more
+    # information, see [ IAM policy actions for Secrets Manager][1] and
+    # [Authentication and access control in Secrets Manager][2]. If you use
+    # a customer managed key, you must also have `kms:GenerateDataKey` and
+    # `kms:Decrypt` permissions on the key. For more information, see [
+    # Secret encryption and decryption][3].
     #
-    # * To create a new secret, use CreateSecret.
     #
-    # * To add only a new version to an existing secret, use PutSecretValue.
     #
-    # * To get the details for a secret, use DescribeSecret.
-    #
-    # * To list the versions contained in a secret, use
-    #   ListSecretVersionIds.
+    # [1]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/security-encryption.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret that you want to modify or to which you want to
-    #   add a new version. You can specify either the Amazon Resource Name
-    #   (ARN) or the friendly name of the secret.
+    #   The ARN or name of the secret.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
     #
     # @option params [String] :client_request_token
-    #   (Optional) If you want to add a new version to the secret, this
-    #   parameter specifies a unique identifier for the new version that helps
-    #   ensure idempotency.
-    #
-    #   If you use the Amazon Web Services CLI or one of the Amazon Web
-    #   Services SDK to call this operation, then you can leave this parameter
-    #   empty. The CLI or SDK generates a random UUID for you and includes
-    #   that in the request. If you don't use the SDK and instead generate a
-    #   raw HTTP request to the Secrets Manager service endpoint, then you
-    #   must generate a `ClientRequestToken` yourself for new versions and
-    #   include that value in the request.
-    #
-    #   You typically only need to interact with this value if you implement
-    #   your own retry logic and want to ensure that a given secret is not
-    #   created twice. We recommend that you generate a [UUID-type][1] value
-    #   to ensure uniqueness within the specified secret.
+    #   If you include `SecretString` or `SecretBinary`, then Secrets Manager
+    #   creates a new version for the secret, and this parameter specifies the
+    #   unique identifier for the new version.
     #
-    #   Secrets Manager uses this value to prevent the accidental creation of
-    #   duplicate versions if there are failures and retries during the Lambda
-    #   rotation function's processing.
-    #
-    #   * If the `ClientRequestToken` value isn't already associated with a
-    #     version of the secret then a new version of the secret is created.
-    #
-    #   * If a version with this value already exists and that version's
-    #     `SecretString` and `SecretBinary` values are the same as those in
-    #     the request then the request is ignored (the operation is
-    #     idempotent).
+    #   <note markdown="1"> If you use the Amazon Web Services CLI or one of the Amazon Web
+    #   Services SDKs to call this operation, then you can leave this
+    #   parameter empty. The CLI or SDK generates a random UUID for you and
+    #   includes it as the value for this parameter in the request. If you
+    #   don't use the SDK and instead generate a raw HTTP request to the
+    #   Secrets Manager service endpoint, then you must generate a
+    #   `ClientRequestToken` yourself for the new version and include the
+    #   value in the request.
     #
-    #   * If a version with this value already exists and that version's
-    #     `SecretString` and `SecretBinary` values are different from the
-    #     request then an error occurs because you cannot modify an existing
-    #     secret value.
+    #    </note>
     #
     #   This value becomes the `VersionId` of the new version.
     #
     #   **A suitable default value is auto-generated.** You should normally
     #   not need to pass this option.**
     #
-    #
-    #
-    #   [1]: https://wikipedia.org/wiki/Universally_unique_identifier
-    #
     # @option params [String] :description
-    #   (Optional) Specifies an updated user-provided description of the
-    #   secret.
+    #   The description of the secret.
     #
     # @option params [String] :kms_key_id
-    #   (Optional) Specifies an updated ARN or alias of the Amazon Web
-    #   Services KMS customer master key (CMK) that Secrets Manager uses to
-    #   encrypt the protected text in new versions of this secret as well as
-    #   any existing versions of this secret that have the staging labels
-    #   AWSCURRENT, AWSPENDING, or AWSPREVIOUS. For more information about
-    #   staging labels, see [Staging Labels][1] in the *Amazon Web Services
-    #   Secrets Manager User Guide*.
+    #   The ARN, key ID, or alias of the KMS key that Secrets Manager uses to
+    #   encrypt new secret versions as well as any existing versions the
+    #   staging labels `AWSCURRENT`, `AWSPENDING`, or `AWSPREVIOUS`. For more
+    #   information about versions and staging labels, see [Concepts:
+    #   Version][1].
     #
-    #   You can only use the account's default CMK to encrypt and decrypt if
-    #   you call this operation using credentials from the same account that
-    #   owns the secret. If the secret is in a different account, then you
-    #   must create a custom CMK and provide the ARN of that CMK in this
-    #   field. The user making the call must have permissions to both the
-    #   secret and the CMK in their respective accounts.
+    #   You can only use the Amazon Web Services managed key
+    #   `aws/secretsmanager` if you call this operation using credentials from
+    #   the same Amazon Web Services account that owns the secret. If the
+    #   secret is in a different account, then you must use a customer managed
+    #   key and provide the ARN of that KMS key in this field. The user making
+    #   the call must have permissions to both the secret and the KMS key in
+    #   their respective accounts.
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/terms-concepts.html#term_staging-label
+    #   [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/getting-started.html#term_version
     #
     # @option params [String, StringIO, File] :secret_binary
-    #   (Optional) Specifies updated binary data that you want to encrypt and
-    #   store in the new version of the secret. To use this parameter in the
-    #   command-line tools, we recommend that you store your binary data in a
-    #   file and then use the appropriate technique for your tool to pass the
-    #   contents of the file as a parameter. Either `SecretBinary` or
-    #   `SecretString` must have a value, but not both. They cannot both be
-    #   empty.
+    #   The binary data to encrypt and store in the new version of the secret.
+    #   We recommend that you store your binary data in a file and then pass
+    #   the contents of the file as a parameter.
     #
-    #   This parameter is not accessible using the Secrets Manager console.
-    #
-    # @option params [String] :secret_string
-    #   (Optional) Specifies updated text data that you want to encrypt and
-    #   store in this new version of the secret. Either `SecretBinary` or
-    #   `SecretString` must have a value, but not both. They cannot both be
-    #   empty.
-    #
-    #   If you create this secret by using the Secrets Manager console then
-    #   Secrets Manager puts the protected secret text in only the
-    #   `SecretString` parameter. The Secrets Manager console stores the
-    #   information as a JSON structure of key/value pairs that the default
-    #   Lambda rotation function knows how to parse.
-    #
-    #   For storing multiple values, we recommend that you use a JSON text
-    #   string argument and specify key/value pairs. For more information, see
-    #   [Specifying parameter values for the Amazon Web Services CLI][1] in
-    #   the Amazon Web Services CLI User Guide.
+    #   Either `SecretBinary` or `SecretString` must have a value, but not
+    #   both.
     #
+    #   You can't access this parameter in the Secrets Manager console.
     #
+    # @option params [String] :secret_string
+    #   The text data to encrypt and store in the new version of the secret.
+    #   We recommend you use a JSON structure of key/value pairs for your
+    #   secret value.
     #
-    #   [1]: https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters.html
+    #   Either `SecretBinary` or `SecretString` must have a value, but not
+    #   both.
     #
     # @return [Types::UpdateSecretResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -2843,18 +2495,17 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Modifies the staging labels attached to a version of a secret. Staging
-    # labels are used to track a version as it progresses through the secret
-    # rotation process. You can attach a staging label to only one version
-    # of a secret at a time. If a staging label to be added is already
-    # attached to another version, then it is moved--removed from the other
-    # version first and then attached to this one. For more information
-    # about staging labels, see [Staging Labels][1] in the *Amazon Web
-    # Services Secrets Manager User Guide*.
+    # Modifies the staging labels attached to a version of a secret. Secrets
+    # Manager uses staging labels to track a version as it progresses
+    # through the secret rotation process. Each staging label can be
+    # attached to only one version at a time. To add a staging label to a
+    # version when it is already attached to another version, Secrets
+    # Manager first removes it from the other version first and then
+    # attaches it to this one. For more information about versions and
+    # staging labels, see [Concepts: Version][1].
     #
     # The staging labels that you specify in the `VersionStage` parameter
-    # are added to the existing list of staging labels--they don't replace
-    # it.
+    # are added to the existing list of staging labels for the version.
     #
     # You can move the `AWSCURRENT` staging label to this version by
     # including it in this call.
@@ -2869,30 +2520,20 @@ module Aws::SecretsManager
     # then the version is considered to be 'deprecated' and can be deleted
     # by Secrets Manager.
     #
-    # **Minimum permissions**
+    # <b>Required permissions: </b>
+    # `secretsmanager:UpdateSecretVersionStage`. For more information, see [
+    # IAM policy actions for Secrets Manager][2] and [Authentication and
+    # access control in Secrets Manager][3].
     #
-    # To run this command, you must have the following permissions:
     #
-    # * secretsmanager:UpdateSecretVersionStage
     #
-    # ^
-    #
-    # **Related operations**
-    #
-    # * To get the list of staging labels that are currently associated with
-    #   a version of a secret, use ` DescribeSecret ` and examine the
-    #   `SecretVersionsToStages` response value.
-    #
-    # ^
-    #
-    #
-    #
-    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/terms-concepts.html#term_staging-label
+    # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/getting-started.html#term_version
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [required, String] :secret_id
-    #   Specifies the secret with the version with the list of staging labels
-    #   you want to modify. You can specify either the Amazon Resource Name
-    #   (ARN) or the friendly name of the secret.
+    #   The ARN or the name of the secret with the version and staging
+    #   labelsto modify.
     #
     #   For an ARN, we recommend that you specify a complete ARN rather than a
     #   partial ARN.
@@ -2901,18 +2542,16 @@ module Aws::SecretsManager
     #   The staging label to add to this version.
     #
     # @option params [String] :remove_from_version_id
-    #   Specifies the secret version ID of the version that the staging label
-    #   is to be removed from. If the staging label you are trying to attach
-    #   to one version is already attached to a different version, then you
-    #   must include this parameter and specify the version that the label is
-    #   to be removed from. If the label is attached and you either do not
-    #   specify this parameter, or the version ID does not match, then the
-    #   operation fails.
+    #   The ID of the version that the staging label is to be removed from. If
+    #   the staging label you are trying to attach to one version is already
+    #   attached to a different version, then you must include this parameter
+    #   and specify the version that the label is to be removed from. If the
+    #   label is attached and you either do not specify this parameter, or the
+    #   version ID does not match, then the operation fails.
     #
     # @option params [String] :move_to_version_id
-    #   (Optional) The secret version ID that you want to add the staging
-    #   label. If you want to remove a label from a version, then do not
-    #   specify this parameter.
+    #   The ID of the version to add the staging label to. To remove a label
+    #   from a version, then do not specify this parameter.
     #
     #   If the staging label is already attached to a different version of the
     #   secret, then you must also specify the `RemoveFromVersionId`
@@ -3001,53 +2640,42 @@ module Aws::SecretsManager
       req.send_request(options)
     end
 
-    # Validates that the resource policy does not grant a wide range of IAM
-    # principals access to your secret. The JSON request string input and
-    # response output displays formatted code with white space and line
-    # breaks for better readability. Submit your input as a single line JSON
-    # string. A resource-based policy is optional for secrets.
+    # Validates that a resource policy does not grant a wide range of
+    # principals access to your secret. A resource-based policy is optional
+    # for secrets.
     #
-    # The API performs three checks when validating the secret:
+    # The API performs three checks when validating the policy:
     #
     # * Sends a call to [Zelkova][1], an automated reasoning engine, to
-    #   ensure your Resource Policy does not allow broad access to your
-    #   secret.
+    #   ensure your resource policy does not allow broad access to your
+    #   secret, for example policies that use a wildcard for the principal.
     #
     # * Checks for correct syntax in a policy.
     #
     # * Verifies the policy does not lock out a caller.
     #
-    # **Minimum Permissions**
-    #
-    # You must have the permissions required to access the following APIs:
-    #
-    # * `secretsmanager:PutResourcePolicy`
-    #
-    # * `secretsmanager:ValidateResourcePolicy`
+    # <b>Required permissions: </b> `secretsmanager:ValidateResourcePolicy`.
+    # For more information, see [ IAM policy actions for Secrets Manager][2]
+    # and [Authentication and access control in Secrets Manager][3].
     #
     #
     #
     # [1]: https://aws.amazon.com/blogs/security/protect-sensitive-data-in-the-cloud-with-automated-reasoning-zelkova/
+    # [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awssecretsmanager.html#awssecretsmanager-actions-as-permissions
+    # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
     #
     # @option params [String] :secret_id
-    #   (Optional) The identifier of the secret with the resource-based policy
-    #   you want to validate. You can specify either the Amazon Resource Name
-    #   (ARN) or the friendly name of the secret.
-    #
-    #   For an ARN, we recommend that you specify a complete ARN rather than a
-    #   partial ARN.
+    #   This field is reserved for internal use.
     #
     # @option params [required, String] :resource_policy
-    #   A JSON-formatted string constructed according to the grammar and
-    #   syntax for an Amazon Web Services resource-based policy. The policy in
-    #   the string identifies who can access or manage this secret and its
-    #   versions. For information on how to format a JSON parameter for the
-    #   various command line tool environments, see [Using JSON for
-    #   Parameters][1] in the *CLI User Guide*.publi
+    #   A JSON-formatted string that contains an Amazon Web Services
+    #   resource-based policy. The policy in the string identifies who can
+    #   access or manage this secret and its versions. For example policies,
+    #   see [Permissions policy examples][1].
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/cli/latest/userguide/cli-using-param.html#cli-using-param-json
+    #   [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_examples.html
     #
     # @return [Types::ValidateResourcePolicyResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -3107,7 +2735,7 @@ module Aws::SecretsManager
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-secretsmanager'
-      context[:gem_version] = '1.52.0'
+      context[:gem_version] = '1.56.0'
       Seahorse::Client::Request.new(handlers, context)
     end