Amazon Web Services Secrets Manager provides a service to enable you to store, manage, and retrieve, secrets.
This guide provides descriptions of the Secrets Manager API. For more information about using this service, see the Amazon Web Services Secrets Manager User Guide.
API Version
This version of the Secrets Manager API Reference documents the Secrets Manager API version 2017-10-17.
For a list of endpoints, see Amazon Web Services Secrets Manager endpoints.
Support and Feedback for Amazon Web Services Secrets Manager
We welcome your feedback. Send your comments to awssecretsmanager-feedback@amazon.com, or post your feedback and questions in the Amazon Web Services Secrets Manager Discussion Forum. For more information about the Amazon Web Services Discussion Forums, see Forums Help.
Logging API Requests
Amazon Web Services Secrets Manager supports Amazon Web Services CloudTrail, a service that records Amazon Web Services API calls for your Amazon Web Services account and delivers log files to an Amazon S3 bucket. By using information that\'s collected by Amazon Web Services CloudTrail, you can determine the requests successfully made to Secrets Manager, who made the request, when it was made, and so on. For more about Amazon Web Services Secrets Manager and support for Amazon Web Services CloudTrail, see Logging Amazon Web Services Secrets Manager Events with Amazon Web Services CloudTrail in the Amazon Web Services Secrets Manager User Guide. To learn more about CloudTrail, including enabling it and find your log files, see the Amazon Web Services CloudTrail User Guide.
', 'operations' => [ 'CancelRotateSecret' => 'Turns off automatic rotation, and if a rotation is currently in progress, cancels the rotation.
If you cancel a rotation in progress, it can leave the VersionStage labels in an unexpected state. You might need to remove the staging label AWSPENDING from the partially created version. You also need to determine whether to roll back to the previous version of the secret by moving the staging label AWSCURRENT to the version that has AWSPENDING. To determine which version has a specific staging label, call ListSecretVersionIds. Then use UpdateSecretVersionStage to change staging labels. For more information, see How rotation works.
To turn on automatic rotation again, call RotateSecret.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:CancelRotateSecret. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Creates a new secret. A secret can be a password, a set of credentials such as a user name and password, an OAuth token, or other secret information 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 secrets that use managed rotation, you need to create the secret through the managing service. For more information, see Secrets Manager secrets managed by other Amazon Web Services services.
For information about creating a secret in the console, see Create a secret.
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 creates an initial secret version and automatically attaches the staging label AWSCURRENT to it.
For database credentials you want to rotate, for Secrets Manager to be able to rotate the secret, you must make sure the JSON you store in the SecretString matches the JSON structure of a database secret.
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.
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.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters except SecretBinary or SecretString because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:CreateSecret. If you include tags in the secret, you also need secretsmanager:TagResource. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
To encrypt the secret with a KMS key other than aws/secretsmanager, you need kms:GenerateDataKey and kms:Decrypt permission to the key.
Deletes the resource-based permission policy attached to the secret. To attach a policy to a secret, use PutResourcePolicy.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:DeleteResourcePolicy. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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.
You can\'t delete a primary secret that is replicated to other Regions. You must first delete the replicas using RemoveRegionsFromReplication, and then delete the primary secret. When you delete a replica, it is deleted immediately.
You can\'t directly delete a version of a secret. Instead, you remove all staging labels from the version using UpdateSecretVersionStage. This marks the version as deprecated, and then Secrets Manager can automatically delete the version in the background.
To determine whether an application still uses a secret, you can create an Amazon CloudWatch alarm to alert you to any attempts to access a secret during the recovery window. For more information, see Monitor secrets scheduled for deletion.
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.
At any time before recovery window ends, you can use RestoreSecret to remove the DeletionDate and cancel the deletion of the secret.
When a secret is scheduled for deletion, you cannot retrieve the secret value. You must first cancel the deletion with RestoreSecret and then you can retrieve the secret.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:DeleteSecret. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Retrieves the details of a secret. It does not include the encrypted secret value. Secrets Manager only returns fields that have a value in the response.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:DescribeSecret. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:GetRandomPassword. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Retrieves the JSON text of the resource-based policy document attached to the secret. For more information about permissions policies attached to a secret, see Permissions policies attached to a secret.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:GetResourcePolicy. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Retrieves the contents of the encrypted fields SecretString or SecretBinary from the specified version of a secret, whichever contains content.
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.
To retrieve the previous version of a secret, use VersionStage and specify AWSPREVIOUS. To revert to the previous version of a secret, call UpdateSecretVersionStage.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: 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 and Authentication and access control in Secrets Manager.
Lists the versions of a secret. Secrets Manager uses staging labels to indicate the different versions of a secret. For more information, see Secrets Manager concepts: Versions.
To list the secrets in the account, use ListSecrets.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:ListSecretVersionIds. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Lists the secrets that are stored by Secrets Manager in the Amazon Web Services account, not including secrets that are marked for deletion. To see secrets marked for deletion, use the Secrets Manager console.
ListSecrets is eventually consistent, however it might not reflect changes from the last five minutes. To get the latest information for a specific secret, use DescribeSecret.
To list the versions of a secret, use ListSecretVersionIds.
To get the secret value from SecretString or SecretBinary, call GetSecretValue.
For information about finding secrets in the console, see Find secrets in Secrets Manager.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:ListSecrets. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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
For information about attaching a policy in the console, see Attach a permissions policy to a secret.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:PutResourcePolicy. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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, Secrets Manager creates a new version of the secret. Secrets Manager removes outdated versions when there are more than 100, but it does not remove versions created less than 24 hours ago. If you call PutSecretValue more than once every 10 minutes, you create more versions than Secrets Manager removes, and you will reach the quota for secret versions.
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. 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 you call this operation with a ClientRequestToken that matches an existing version\'s VersionId, 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.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters except SecretBinary or SecretString because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:PutSecretValue. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
For a secret that is replicated to other Regions, deletes the secret replicas from the Regions you specify.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:RemoveRegionsFromReplication. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Replicates the secret to a new Regions. See Multi-Region secrets.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:ReplicateSecretToRegions. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Cancels the scheduled deletion of a secret by removing the DeletedDate time stamp. You can access a secret again after it has been restored.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:RestoreSecret. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
Configures and starts the asynchronous process of rotating the secret. For information about rotation, see Rotate secrets in the Secrets Manager User Guide. 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.
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 RotateSecret assumes that a previous rotation request is still in progress and returns an error. When rotation is unsuccessful, the AWSPENDING staging label might be attached to an empty secret version. For more information, see Troubleshoot rotation in the Secrets Manager User Guide.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:RotateSecret. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager. You also need lambda:InvokeFunction permissions on the rotation function. For more information, see Permissions for rotation.
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.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:StopReplicationToReplica. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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 restrictions apply to tags:
Maximum number of tags per secret: 50
Maximum key length: 127 Unicode characters in UTF-8
Maximum value length: 255 Unicode characters in UTF-8
Tag keys and values are case sensitive.
Do not use the aws: prefix in your tag names or values because Amazon Web Services reserves it for Amazon Web Services use. You can\'t edit or delete tag names or values with this prefix. Tags with this prefix do not count against your tags per secret limit.
If you use your tagging schema across multiple services and 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 removing a tag can change permissions. If successfully completing this operation would result in you losing your permissions for this secret, then the operation is blocked and returns an Access Denied error.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:TagResource. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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.
If you use tags as part of your security strategy, then removing a tag can change permissions. If successfully completing this operation would result in you losing your permissions for this secret, then the operation is blocked and returns an Access Denied error.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:UntagResource. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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.
To change a secret so that it is managed by another service, you need to recreate the secret in that service. See Secrets Manager secrets managed by other Amazon Web Services services.
We recommend you avoid calling UpdateSecret at a sustained rate of more than once every 10 minutes. When you call UpdateSecret to update the secret value, Secrets Manager creates a new version of the secret. Secrets Manager removes outdated versions when there are more than 100, but it does not remove versions created less than 24 hours ago. If you update the secret value more than once every 10 minutes, you create more versions than Secrets Manager removes, and you will reach the quota for secret versions.
If you include SecretString or SecretBinary to create a new secret version, Secrets Manager automatically moves the staging label AWSCURRENT to the new version. Then it attaches the label AWSPREVIOUS to the version that AWSCURRENT was removed from.
If you call this operation with a ClientRequestToken that matches an existing version\'s VersionId, 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.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters except SecretBinary or SecretString because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:UpdateSecret. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager. If you use a customer managed key, you must also have kms:GenerateDataKey, kms:Encrypt, and kms:Decrypt permissions on the key. If you change the KMS key and you don\'t have kms:Encrypt permission to the new key, Secrets Manager does not re-ecrypt existing secret versions with the new key. For more information, see Secret encryption and decryption.
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.
The staging labels that you specify in the VersionStage parameter 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.
Whenever you move AWSCURRENT, Secrets Manager automatically moves the label AWSPREVIOUS to the version that AWSCURRENT was removed from.
If this action results in the last label being removed from a version, then the version is considered to be \'deprecated\' and can be deleted by Secrets Manager.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:UpdateSecretVersionStage. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
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 policy:
Sends a call to Zelkova, an automated reasoning engine, to 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.
Secrets Manager generates a CloudTrail log entry when you call this action. Do not include sensitive information in request parameters because it might be logged. For more information, see Logging Secrets Manager events with CloudTrail.
Required permissions: secretsmanager:ValidateResourcePolicy and secretsmanager:PutResourcePolicy. For more information, see IAM policy actions for Secrets Manager and Authentication and access control in Secrets Manager.
A list of Regions and KMS keys to replicate secrets.
', 'ReplicateSecretToRegionsRequest$AddReplicaRegions' => 'A list of Regions in which to replicate the secret.
', ], ], 'AutomaticallyRotateAfterDaysType' => [ 'base' => NULL, 'refs' => [ 'RotationRulesType$AutomaticallyAfterDays' => 'The number of days between rotations of the secret. You can use this value to check that your secret meets your compliance guidelines for how often secrets must be rotated. If you use this field to set the rotation schedule, Secrets Manager calculates the next rotation date based on the previous rotation. Manually updating the secret value by calling PutSecretValue or UpdateSecret is considered a valid rotation.
In DescribeSecret and ListSecrets, this value is calculated from the rotation schedule after every successful rotation. In RotateSecret, you can set the rotation schedule in RotationRules with AutomaticallyAfterDays or ScheduleExpression, but not both. To set a rotation schedule in hours, use ScheduleExpression.
Specifies whether to overwrite a secret with the same name in the destination Region. By default, secrets aren\'t overwritten.
', 'DeleteSecretRequest$ForceDeleteWithoutRecovery' => '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 by default Secrets Manager uses a 30 day recovery window.
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.
If you forcibly delete an already deleted or nonexistent secret, the operation does not return ResourceNotFoundException.
Use this parameter with caution. This parameter causes the operation 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 ForceDeleteWithoutRecovery parameter, then you have no opportunity to recover the secret. You lose the secret permanently.
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. By default, versions without staging labels aren\'t included.
', 'ListSecretsRequest$IncludePlannedDeletion' => 'Specifies whether to include secrets scheduled for deletion. By default, secrets scheduled for deletion aren\'t included.
', 'PutResourcePolicyRequest$BlockPublicPolicy' => 'Specifies whether to block resource-based policies that allow broad access to the secret, for example those that use a wildcard for the principal. By default, public policies aren\'t blocked.
', 'ReplicateSecretToRegionsRequest$ForceOverwriteReplicaSecret' => 'Specifies whether to overwrite a secret with the same name in the destination Region. By default, secrets aren\'t overwritten.
', 'RotateSecretRequest$RotateImmediately' => 'Specifies whether to rotate the secret immediately or wait until the next scheduled rotation window. The rotation schedule is defined in RotateSecretRequest$RotationRules.
For secrets that use a Lambda rotation function to rotate, if you don\'t immediately rotate the secret, Secrets Manager tests the rotation configuration by running the testSecret step of the Lambda rotation function. The test creates an AWSPENDING version of the secret and then removes it.
By default, Secrets Manager rotates the secret immediately.
', 'ValidateResourcePolicyResponse$PolicyValidationPassed' => 'True if your policy passes validation, otherwise false.
', ], ], 'CancelRotateSecretRequest' => [ 'base' => NULL, 'refs' => [], ], 'CancelRotateSecretResponse' => [ 'base' => NULL, 'refs' => [], ], 'ClientRequestTokenType' => [ 'base' => NULL, 'refs' => [ 'CreateSecretRequest$ClientRequestToken' => '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.
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.
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 a rotation. We recommend that you generate a UUID-type value to ensure uniqueness of your versions 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 the version SecretString and SecretBinary values are the same as those in the request, then the request is ignored.
If a version with this value already exists and that version\'s SecretString and SecretBinary values are different from those in the request, then the request fails because you cannot modify an existing version. Instead, use PutSecretValue to create a new version.
This value becomes the VersionId of the new version.
A unique identifier for the new version of the secret.
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 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.
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 processing. We recommend that you generate a UUID-type 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.
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 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.
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 empty. The CLI or SDK generates a random UUID for you and includes that in the request for this parameter. 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 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 value to ensure uniqueness within the specified secret.
', 'UpdateSecretRequest$ClientRequestToken' => '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.
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.
This value becomes the VersionId of the new version.
The date and time that this version of the secret was created. If you don\'t specify which version in VersionId or VersionStage, then Secrets Manager uses the AWSCURRENT version.
The date and time this version of the secret was created.
', ], ], 'DecryptionFailure' => [ 'base' => 'Secrets Manager can\'t decrypt the protected secret text using the provided KMS key.
', 'refs' => [], ], 'DeleteResourcePolicyRequest' => [ 'base' => NULL, 'refs' => [], ], 'DeleteResourcePolicyResponse' => [ 'base' => NULL, 'refs' => [], ], 'DeleteSecretRequest' => [ 'base' => NULL, 'refs' => [], ], 'DeleteSecretResponse' => [ 'base' => NULL, 'refs' => [], ], 'DeletedDateType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$DeletedDate' => 'The date the secret is scheduled for deletion. If it is not scheduled for deletion, this field is omitted. When you delete a secret, Secrets Manager requires a recovery window of at least 7 days before deleting the secret. Some time after the deleted date, Secrets Manager deletes the secret, including all of its versions.
If a secret is scheduled for deletion, then its details, including the encrypted secret value, is not accessible. To cancel a scheduled deletion and restore access to the secret, use RestoreSecret.
', 'SecretListEntry$DeletedDate' => 'The date and time the deletion of the secret occurred. Not present on active secrets. The secret can be recovered until the number of days in the recovery window has passed, as specified in the RecoveryWindowInDays parameter of the DeleteSecret operation.
The date and time after which this secret Secrets Manager can permanently delete this secret, and it can no longer be restored. This value is the date and time of the delete request plus the number of days in RecoveryWindowInDays.
The description of the secret.
', 'DescribeSecretResponse$Description' => 'The description of the secret.
', 'SecretListEntry$Description' => 'The user-provided description of the secret.
', 'UpdateSecretRequest$Description' => 'The description of the secret.
', ], ], 'DurationType' => [ 'base' => NULL, 'refs' => [ 'RotationRulesType$Duration' => 'The length of the rotation window in hours, for example 3h for a three hour window. Secrets Manager rotates your secret at any time during this window. The window must not extend into the next rotation window or the next UTC day. The window starts according to the ScheduleExpression. If you don\'t specify a Duration, for a ScheduleExpression in hours, the window automatically closes after one hour. For a ScheduleExpression in days, the window automatically closes at the end of the UTC day. For more information, including examples, see Schedule expressions in Secrets Manager rotation in the Secrets Manager Users Guide.
Secrets Manager can\'t encrypt the protected secret text using the provided KMS key. Check that the KMS key is available, enabled, and not in an invalid state. For more information, see Key state: Effect on your KMS key.
', 'refs' => [], ], 'ErrorMessage' => [ 'base' => NULL, 'refs' => [ 'DecryptionFailure$Message' => NULL, 'EncryptionFailure$Message' => NULL, 'InternalServiceError$Message' => NULL, 'InvalidNextTokenException$Message' => NULL, 'InvalidParameterException$Message' => NULL, 'InvalidRequestException$Message' => NULL, 'LimitExceededException$Message' => NULL, 'MalformedPolicyDocumentException$Message' => NULL, 'PreconditionNotMetException$Message' => NULL, 'PublicPolicyException$Message' => NULL, 'ResourceExistsException$Message' => NULL, 'ResourceNotFoundException$Message' => NULL, 'ValidationErrorsEntry$ErrorMessage' => 'Displays error messages if validation encounters problems during validation of the resource policy.
', ], ], 'ExcludeCharactersType' => [ 'base' => NULL, 'refs' => [ 'GetRandomPasswordRequest$ExcludeCharacters' => 'A string of the characters that you don\'t want in the password.
', ], ], 'ExcludeLowercaseType' => [ 'base' => NULL, 'refs' => [ 'GetRandomPasswordRequest$ExcludeLowercase' => 'Specifies whether to exclude lowercase letters from the password. If you don\'t include this switch, the password can contain lowercase letters.
', ], ], 'ExcludeNumbersType' => [ 'base' => NULL, 'refs' => [ 'GetRandomPasswordRequest$ExcludeNumbers' => 'Specifies whether to exclude numbers from the password. If you don\'t include this switch, the password can contain numbers.
', ], ], 'ExcludePunctuationType' => [ 'base' => NULL, 'refs' => [ 'GetRandomPasswordRequest$ExcludePunctuation' => 'Specifies whether to exclude the following punctuation characters from the password: ! " # $ % & \' ( ) * + , - . / : ; < = > ? @ [ \\ ] ^ _ ` { | } ~. If you don\'t include this switch, the password can contain punctuation.
Specifies whether to exclude uppercase letters from the password. If you don\'t include this switch, the password can contain uppercase letters.
', ], ], 'Filter' => [ 'base' => 'Allows you to add filters when you use the search function in Secrets Manager. For more information, see Find secrets in Secrets Manager.
', 'refs' => [ 'FiltersListType$member' => NULL, ], ], 'FilterNameStringType' => [ 'base' => NULL, 'refs' => [ 'Filter$Key' => 'The following are keys you can use:
description: Prefix match, not case-sensitive.
name: Prefix match, case-sensitive.
tag-key: Prefix match, case-sensitive.
tag-value: Prefix match, case-sensitive.
primary-region: Prefix match, case-sensitive.
owning-service: Prefix match, case-sensitive.
all: Breaks the filter value string into words and then searches all attributes for matches. Not case-sensitive.
The keyword to filter for.
You can prefix your search value with an exclamation mark (!) in order to perform negation filters.
The filters to apply to the list of secrets.
', ], ], 'GetRandomPasswordRequest' => [ 'base' => NULL, 'refs' => [], ], 'GetRandomPasswordResponse' => [ 'base' => NULL, 'refs' => [], ], 'GetResourcePolicyRequest' => [ 'base' => NULL, 'refs' => [], ], 'GetResourcePolicyResponse' => [ 'base' => NULL, 'refs' => [], ], 'GetSecretValueRequest' => [ 'base' => NULL, 'refs' => [], ], 'GetSecretValueResponse' => [ 'base' => NULL, 'refs' => [], ], 'IncludeSpaceType' => [ 'base' => NULL, 'refs' => [ 'GetRandomPasswordRequest$IncludeSpace' => 'Specifies whether to include the space character. If you include this switch, the password can contain space characters.
', ], ], 'InternalServiceError' => [ 'base' => 'An error occurred on the server side.
', 'refs' => [], ], 'InvalidNextTokenException' => [ 'base' => 'The NextToken value is invalid.
The parameter name or value is invalid.
', 'refs' => [], ], 'InvalidRequestException' => [ 'base' => 'A parameter value is not valid for the current state of the resource.
Possible causes:
The secret is scheduled for deletion.
You tried to enable rotation on a secret that doesn\'t already have a Lambda function ARN configured and you didn\'t include such an ARN as a parameter in this call.
The secret is managed by another service, and you must use that service to update it. For more information, see Secrets managed by other Amazon Web Services services.
The KMS keys used to encrypt the secret version.
', ], ], 'KmsKeyIdType' => [ 'base' => NULL, 'refs' => [ 'CreateSecretRequest$KmsKeyId' => 'The ARN, key ID, or alias of the KMS key that Secrets Manager uses to encrypt the secret value in the secret. An alias is always prefixed by alias/, for example alias/aws/secretsmanager. For more information, see About aliases.
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 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.
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.
The key ID or alias ARN of the KMS key that Secrets Manager uses to encrypt the secret value. If the secret is encrypted with the Amazon Web Services managed key aws/secretsmanager, this field is omitted. Secrets created using the console use an KMS key ID.
The ARN, key ID, or alias of the KMS key to encrypt the secret. If you don\'t include this field, Secrets Manager uses aws/secretsmanager.
Can be an ARN, Key ID, or Alias.
The ARN of the KMS key that Secrets Manager uses to encrypt the secret value. If the secret is encrypted with the Amazon Web Services managed key aws/secretsmanager, this field is omitted.
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 with the staging labels AWSCURRENT, AWSPENDING, or AWSPREVIOUS. If you don\'t have kms:Encrypt permission to the new key, Secrets Manager does not re-ecrypt existing secret versions with the new key. For more information about versions and staging labels, see Concepts: Version.
A key alias is always prefixed by alias/, for example alias/aws/secretsmanager. For more information, see About aliases.
If you set this to an empty string, 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.
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.
The date that the secret was last accessed in the Region. This field is omitted if the secret has never been retrieved in the Region.
', 'ReplicationStatusType$LastAccessedDate' => 'The date that the secret was last accessed in the Region. This field is omitted if the secret has never been retrieved in the Region.
', 'SecretListEntry$LastAccessedDate' => 'The date that the secret was last accessed in the Region. This field is omitted if the secret has never been retrieved in the Region.
', 'SecretVersionsListEntry$LastAccessedDate' => 'The date that this version of the secret was last accessed. Note that the resolution of this field is at the date level and does not include the time.
', ], ], 'LastChangedDateType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$LastChangedDate' => 'The last date and time that this secret was modified in any way.
', 'SecretListEntry$LastChangedDate' => 'The last date and time that this secret was modified in any way.
', ], ], 'LastRotatedDateType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$LastRotatedDate' => 'The last date and time that Secrets Manager rotated the secret. If the secret isn\'t configured for rotation, Secrets Manager returns null.
', 'SecretListEntry$LastRotatedDate' => 'The most recent date and time that the Secrets Manager rotation process was successfully completed. This value is null if the secret hasn\'t ever rotated.
', ], ], 'LimitExceededException' => [ 'base' => 'The request failed because it would exceed one of the Secrets Manager quotas.
', 'refs' => [], ], 'ListSecretVersionIdsRequest' => [ 'base' => NULL, 'refs' => [], ], 'ListSecretVersionIdsResponse' => [ 'base' => NULL, 'refs' => [], ], 'ListSecretsRequest' => [ 'base' => NULL, 'refs' => [], ], 'ListSecretsResponse' => [ 'base' => NULL, 'refs' => [], ], 'MalformedPolicyDocumentException' => [ 'base' => 'The resource policy has syntax errors.
', 'refs' => [], ], 'MaxResultsType' => [ 'base' => NULL, 'refs' => [ 'ListSecretVersionIdsRequest$MaxResults' => '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.
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.
The name of the new secret.
The secret name can contain ASCII letters, numbers, and the following 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 after the secret name at the end of the ARN.
', 'DeleteResourcePolicyResponse$Name' => 'The name of the secret that the resource-based policy was deleted for.
', 'GetResourcePolicyResponse$Name' => 'The name of the secret that the resource-based policy was retrieved for.
', 'PutResourcePolicyResponse$Name' => 'The name of the secret.
', 'ValidationErrorsEntry$CheckName' => 'Checks the name of the policy.
', ], ], 'NextRotationDateType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$NextRotationDate' => 'The next rotation is scheduled to occur on or before this date. If the secret isn\'t configured for rotation, Secrets Manager returns null.
', 'SecretListEntry$NextRotationDate' => 'The next rotation is scheduled to occur on or before this date. If the secret isn\'t configured for rotation, Secrets Manager returns null.
', ], ], 'NextTokenType' => [ 'base' => NULL, 'refs' => [ 'ListSecretVersionIdsRequest$NextToken' => '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.
Secrets Manager includes this value if there\'s more output available than what is included in the current response. This can occur even when the response includes no values at all, such as when you ask for a filtered view of a long list. To get the next results, call ListSecretVersionIds again with this value.
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.
Secrets Manager includes this value if there\'s more output available than what is included in the current response. This can occur even when the response includes no values at all, such as when you ask for a filtered view of a long list. To get the next results, call ListSecrets again with this value.
A JSON-formatted string that contains the permissions policy attached to the secret. For more information about permissions policies, see Authentication and access control for Secrets Manager.
', 'PutResourcePolicyRequest$ResourcePolicy' => 'A JSON-formatted string for an Amazon Web Services resource-based policy. For example policies, see Permissions policy examples.
', 'ValidateResourcePolicyRequest$ResourcePolicy' => '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.
', ], ], 'OwningServiceType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$OwningService' => 'The ID of the service that created this secret. For more information, see Secrets managed by other Amazon Web Services services.
', 'SecretListEntry$OwningService' => 'Returns the name of the service that created the secret.
', ], ], 'PasswordLengthType' => [ 'base' => NULL, 'refs' => [ 'GetRandomPasswordRequest$PasswordLength' => 'The length of the password. If you don\'t include this parameter, the default length is 32 characters.
', ], ], 'PreconditionNotMetException' => [ 'base' => 'The request failed because you did not complete all the prerequisite steps.
', 'refs' => [], ], 'PublicPolicyException' => [ 'base' => 'The BlockPublicPolicy parameter is set to true, and the resource policy did not prevent broad access to the secret.
A string with the password.
', ], ], 'RecoveryWindowInDaysType' => [ 'base' => NULL, 'refs' => [ 'DeleteSecretRequest$RecoveryWindowInDays' => '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 by default Secrets Manager uses a 30 day recovery window.
The Region the secret is in. If a secret is replicated to other Regions, the replicas are listed in ReplicationStatus.
A Region code. For a list of Region codes, see Name and code of Regions.
', 'ReplicationStatusType$Region' => 'The Region where replication occurs.
', 'SecretListEntry$PrimaryRegion' => 'The Region where Secrets Manager originated the secret.
', ], ], 'RemoveRegionsFromReplicationRequest' => [ 'base' => NULL, 'refs' => [], ], 'RemoveRegionsFromReplicationResponse' => [ 'base' => NULL, 'refs' => [], ], 'RemoveReplicaRegionListType' => [ 'base' => NULL, 'refs' => [ 'RemoveRegionsFromReplicationRequest$RemoveReplicaRegions' => 'The Regions of the replicas to remove.
', ], ], 'ReplicaRegionType' => [ 'base' => 'A custom type that specifies a Region and the KmsKeyId for a replica secret.
A list of the replicas of this secret and their status:
Failed, which indicates that the replica was not created.
InProgress, which indicates that Secrets Manager is in the process of creating the replica.
InSync, which indicates that the replica was created.
A list of the replicas of this secret and their status:
Failed, which indicates that the replica was not created.
InProgress, which indicates that Secrets Manager is in the process of creating the replica.
InSync, which indicates that the replica was created.
The status of replicas for this secret after you remove Regions.
', 'ReplicateSecretToRegionsResponse$ReplicationStatus' => 'The status of replication.
', ], ], 'ReplicationStatusType' => [ 'base' => 'A replication object consisting of a RegionReplicationStatus object and includes a Region, KMSKeyId, status, and status message.
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.
', ], ], 'ResourceExistsException' => [ 'base' => 'A resource with the ID you requested already exists.
', 'refs' => [], ], 'ResourceNotFoundException' => [ 'base' => 'Secrets Manager can\'t find the resource that you asked for.
', 'refs' => [], ], 'RestoreSecretRequest' => [ 'base' => NULL, 'refs' => [], ], 'RestoreSecretResponse' => [ 'base' => NULL, 'refs' => [], ], 'RotateSecretRequest' => [ 'base' => NULL, 'refs' => [], ], 'RotateSecretResponse' => [ 'base' => NULL, 'refs' => [], ], 'RotationEnabledType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$RotationEnabled' => 'Specifies whether automatic rotation is turned on for this secret.
To turn on rotation, use RotateSecret. To turn off rotation, use CancelRotateSecret.
', 'SecretListEntry$RotationEnabled' => 'Indicates whether automatic, scheduled rotation is enabled for this secret.
', ], ], 'RotationLambdaARNType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$RotationLambdaARN' => 'The ARN of the Lambda function that Secrets Manager invokes to rotate the secret.
', 'RotateSecretRequest$RotationLambdaARN' => 'For secrets that use a Lambda rotation function to rotate, the ARN of the Lambda rotation function.
For secrets that use managed rotation, omit this field. For more information, see Managed rotation in the Secrets Manager User Guide.
', 'SecretListEntry$RotationLambdaARN' => 'The ARN of an Amazon Web Services Lambda function invoked by Secrets Manager to rotate and expire the secret either automatically per the schedule or manually by a call to RotateSecret .
A structure that defines the rotation configuration for the secret.
', 'refs' => [ 'DescribeSecretResponse$RotationRules' => 'The rotation schedule and Lambda function for this secret. If the secret previously had rotation turned on, but it is now turned off, this field shows the previous rotation schedule and rotation function. If the secret never had rotation turned on, this field is omitted.
', 'RotateSecretRequest$RotationRules' => 'A structure that defines the rotation configuration for this secret.
', 'SecretListEntry$RotationRules' => 'A structure that defines the rotation configuration for the secret.
', ], ], 'ScheduleExpressionType' => [ 'base' => NULL, 'refs' => [ 'RotationRulesType$ScheduleExpression' => 'A cron() or rate() expression that defines the schedule for rotating your secret. Secrets Manager rotation schedules use UTC time zone. Secrets Manager rotates your secret any time during a rotation window.
Secrets Manager rate() expressions represent the interval in hours or days that you want to rotate your secret, for example rate(12 hours) or rate(10 days). You can rotate a secret as often as every four hours. If you use a rate() expression, the rotation window starts at midnight. For a rate in hours, the default rotation window closes after one hour. For a rate in days, the default rotation window closes at the end of the day. You can set the Duration to change the rotation window. The rotation window must not extend into the next UTC day or into the next rotation window.
You can use a cron() expression to create a rotation schedule that is more detailed than a rotation interval. For more information, including examples, see Schedule expressions in Secrets Manager rotation in the Secrets Manager Users Guide. For a cron expression that represents a schedule in hours, the default rotation window closes after one hour. For a cron expression that represents a schedule in days, the default rotation window closes at the end of the day. You can set the Duration to change the rotation window. The rotation window must not extend into the next UTC day or into the next rotation window.
The ARN of the secret.
', 'CreateSecretResponse$ARN' => 'The ARN of the new secret. The ARN includes the name of the secret followed by six random characters. This ensures that if you create a new secret with the same name as a deleted secret, then users with access to the old secret don\'t get access to the new secret because the ARNs are different.
', 'DeleteResourcePolicyResponse$ARN' => 'The ARN of the secret that the resource-based policy was deleted for.
', 'DeleteSecretResponse$ARN' => 'The ARN of the secret.
', 'DescribeSecretResponse$ARN' => 'The ARN of the secret.
', 'GetResourcePolicyResponse$ARN' => 'The ARN of the secret that the resource-based policy was retrieved for.
', 'GetSecretValueResponse$ARN' => 'The ARN of the secret.
', 'ListSecretVersionIdsResponse$ARN' => 'The ARN of the secret.
', 'PutResourcePolicyResponse$ARN' => 'The ARN of the secret.
', 'PutSecretValueResponse$ARN' => 'The ARN of the secret.
', 'RemoveRegionsFromReplicationResponse$ARN' => 'The ARN of the primary secret.
', 'ReplicateSecretToRegionsResponse$ARN' => 'The ARN of the primary secret.
', 'RestoreSecretResponse$ARN' => 'The ARN of the secret that was restored.
', 'RotateSecretResponse$ARN' => 'The ARN of the secret.
', 'SecretListEntry$ARN' => 'The Amazon Resource Name (ARN) of the secret.
', 'StopReplicationToReplicaResponse$ARN' => 'The ARN of the promoted secret. The ARN is the same as the original primary secret except the Region is changed.
', 'UpdateSecretResponse$ARN' => 'The ARN of the secret that was updated.
', 'UpdateSecretVersionStageResponse$ARN' => 'The ARN of the secret that was updated.
', ], ], 'SecretBinaryType' => [ 'base' => NULL, 'refs' => [ 'CreateSecretRequest$SecretBinary' => '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.
This parameter is not available in the Secrets Manager console.
', 'GetSecretValueResponse$SecretBinary' => 'The decrypted secret value, if the secret value was originally provided as binary data in the form of a byte array. The response parameter represents the binary data as a base64-encoded string.
If the secret was created by using the Secrets Manager console, or if the secret value was originally provided as a string, then this field is omitted. The secret value appears in SecretString instead.
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.
You must include SecretBinary or SecretString, but not both.
You can\'t access this value from the Secrets Manager console.
', 'UpdateSecretRequest$SecretBinary' => '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 SecretBinary or SecretString must have a value, but not both.
You can\'t access this parameter in the Secrets Manager console.
', ], ], 'SecretIdType' => [ 'base' => NULL, 'refs' => [ 'CancelRotateSecretRequest$SecretId' => 'The ARN or name of the secret.
For an ARN, we recommend that you specify a complete ARN rather than a partial ARN. See Finding a secret from a partial ARN.
', 'DeleteResourcePolicyRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'DeleteSecretRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'DescribeSecretRequest$SecretId' => 'The ARN or name of the secret.
For an ARN, we recommend that you specify a complete ARN rather than a partial ARN. See Finding a secret from a partial ARN.
', 'GetResourcePolicyRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'GetSecretValueRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'ListSecretVersionIdsRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'PutResourcePolicyRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'PutSecretValueRequest$SecretId' => '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. See Finding a secret from a partial ARN.
If the secret doesn\'t already exist, use CreateSecret instead.
The ARN or name of the secret.
', 'ReplicateSecretToRegionsRequest$SecretId' => 'The ARN or name of the secret to replicate.
', 'RestoreSecretRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'RotateSecretRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'StopReplicationToReplicaRequest$SecretId' => 'The ARN of the primary secret.
', 'TagResourceRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'UntagResourceRequest$SecretId' => 'The ARN or name of the secret.
For an ARN, we recommend that you specify a complete ARN rather than a partial ARN. See Finding a secret from a partial ARN.
', 'UpdateSecretRequest$SecretId' => 'The ARN or name of the secret.
For an ARN, we recommend that you specify a complete ARN rather than a partial ARN. See Finding a secret from a partial ARN.
', 'UpdateSecretVersionStageRequest$SecretId' => '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. See Finding a secret from a partial ARN.
', 'ValidateResourcePolicyRequest$SecretId' => 'This field is reserved for internal use.
', ], ], 'SecretListEntry' => [ 'base' => 'A structure that contains the details about a secret. It does not include the encrypted SecretString and SecretBinary values. To get those values, use GetSecretValue .
A list of the secrets in the account.
', ], ], 'SecretNameType' => [ 'base' => NULL, 'refs' => [ 'CancelRotateSecretResponse$Name' => 'The name of the secret.
', 'CreateSecretResponse$Name' => 'The name of the new secret.
', 'DeleteSecretResponse$Name' => 'The name of the secret.
', 'DescribeSecretResponse$Name' => 'The name of the secret.
', 'GetSecretValueResponse$Name' => 'The friendly name of the secret.
', 'ListSecretVersionIdsResponse$Name' => 'The name of the secret.
', 'PutSecretValueResponse$Name' => 'The name of the secret.
', 'RestoreSecretResponse$Name' => 'The name of the secret that was restored.
', 'RotateSecretResponse$Name' => 'The name of the secret.
', 'SecretListEntry$Name' => 'The friendly name of the secret. You can use forward slashes in the name to represent a path hierarchy. For example, /prod/databases/dbserver1 could represent the secret for a server named dbserver1 in the folder databases in the folder prod.
The name of the secret that was updated.
', 'UpdateSecretVersionStageResponse$Name' => 'The name of the secret that was updated.
', ], ], 'SecretStringType' => [ 'base' => NULL, 'refs' => [ 'CreateSecretRequest$SecretString' => '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.
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 a Lambda rotation function can parse.
The decrypted secret value, if the secret value was originally provided as a string or through the Secrets Manager console.
If this secret was created by using the console, then Secrets Manager stores the information as a JSON structure of key/value pairs.
', 'PutSecretValueRequest$SecretString' => 'The text to encrypt and store in the new version of the secret.
You must include SecretBinary or SecretString, but not both.
We recommend you create the secret string as JSON key/value pairs, as shown in the example.
', 'UpdateSecretRequest$SecretString' => '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.
Either SecretBinary or SecretString must have a value, but not both.
The unique identifier of the version of the secret created during the rotation. This version might not be complete, and should be evaluated for possible deletion. We recommend that you remove the VersionStage value AWSPENDING from this version so that Secrets Manager can delete it. Failing to clean up a cancelled rotation can block you from starting future rotations.
The unique identifier associated with the version of the new secret.
', 'GetSecretValueRequest$VersionId' => '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 value with 32 hexadecimal digits.
', 'GetSecretValueResponse$VersionId' => 'The unique identifier of this version of the secret.
', 'PutSecretValueResponse$VersionId' => 'The unique identifier of the version of the secret.
', 'RotateSecretResponse$VersionId' => 'The ID of the new version of the secret.
', 'SecretVersionsListEntry$VersionId' => 'The unique version identifier of this version of the secret.
', 'SecretVersionsToStagesMapType$key' => NULL, 'UpdateSecretResponse$VersionId' => 'If Secrets Manager created a new version of the secret during this operation, then VersionId contains the unique identifier of the new version.
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.
', 'UpdateSecretVersionStageRequest$MoveToVersionId' => '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 parameter.
The staging label of the version of the secret to retrieve.
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.
The staging label to add to this version.
', ], ], 'SecretVersionStagesType' => [ 'base' => NULL, 'refs' => [ 'GetSecretValueResponse$VersionStages' => 'A list of all of the staging labels currently attached to this version of the secret.
', 'PutSecretValueRequest$VersionStages' => '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 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.
The list of staging labels that are currently attached to this version of the secret. Secrets Manager uses staging labels to track a version as it progresses through the secret rotation process.
', 'SecretVersionsListEntry$VersionStages' => 'An array of staging labels that are currently associated with this version of the secret.
', 'SecretVersionsToStagesMapType$value' => NULL, ], ], 'SecretVersionsListEntry' => [ 'base' => 'A structure that contains information about one version of a secret.
', 'refs' => [ 'SecretVersionsListType$member' => NULL, ], ], 'SecretVersionsListType' => [ 'base' => NULL, 'refs' => [ 'ListSecretVersionIdsResponse$Versions' => 'A list of the versions of the secret.
', ], ], 'SecretVersionsToStagesMapType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$VersionIdsToStages' => 'A list of the versions of the secret that have staging labels attached. Versions that don\'t have staging labels are considered deprecated and Secrets Manager can delete them.
Secrets Manager uses staging labels to indicate the status of a secret version during rotation. The three staging labels for rotation are:
AWSCURRENT, which indicates the current version of the secret.
AWSPENDING, which indicates the version of the secret that contains new secret information that will become the next current version when rotation finishes.
During rotation, Secrets Manager creates an AWSPENDING version ID before creating the new secret version. To check if a secret version exists, call GetSecretValue.
AWSPREVIOUS, which indicates the previous current version of the secret. You can use this as the last known good version.
For more information about rotation and staging labels, see How rotation works.
', 'SecretListEntry$SecretVersionsToStages' => 'A list of all of the currently assigned SecretVersionStage staging labels and the SecretVersionId attached to each one. Staging labels are used to keep track of the different versions during the rotation process.
A version that does not have any SecretVersionStage is considered deprecated and subject to deletion. Such versions are not included in this list.
Secrets are listed by CreatedDate.
Status message such as "Secret with this name already exists in this region".
', ], ], 'StatusType' => [ 'base' => NULL, 'refs' => [ 'ReplicationStatusType$Status' => 'The status can be InProgress, Failed, or InSync.
A structure that contains information about a tag.
', 'refs' => [ 'TagListType$member' => NULL, ], ], 'TagKeyListType' => [ 'base' => NULL, 'refs' => [ 'UntagResourceRequest$TagKeys' => '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 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 Specifying parameter values for the Amazon Web Services CLI in the Amazon Web Services CLI User Guide.
', ], ], 'TagKeyType' => [ 'base' => NULL, 'refs' => [ 'Tag$Key' => 'The key identifier, or name, of the tag.
', 'TagKeyListType$member' => NULL, ], ], 'TagListType' => [ 'base' => NULL, 'refs' => [ 'CreateSecretRequest$Tags' => '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:
[{"Key":"CostCenter","Value":"12345"},{"Key":"environment","Value":"production"}]
Secrets Manager tag key names are case sensitive. A tag with the key "ABC" is a different tag from one with key "abc".
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 and Limit access to identities with tags that match secrets\' tags.
For information about how to format a JSON parameter for the various command line tool environments, see Using JSON for Parameters. 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 restrictions apply to tags:
Maximum number of tags per secret: 50
Maximum key length: 127 Unicode characters in UTF-8
Maximum value length: 255 Unicode characters in UTF-8
Tag keys and values are case sensitive.
Do not use the aws: prefix in your tag names or values because Amazon Web Services reserves it for Amazon Web Services use. You can\'t edit or delete tag names or values with this prefix. Tags with this prefix do not count against your tags per secret limit.
If you use your tagging schema across multiple services and 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: + - = . _ : / @.
The list of tags attached to the secret. To add tags to a secret, use TagResource. To remove tags, use UntagResource.
', 'SecretListEntry$Tags' => 'The list of user-defined tags associated with the secret. To add tags to a secret, use TagResource . To remove tags, use UntagResource .
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 Specifying parameter values for the Amazon Web Services CLI in the Amazon Web Services CLI User Guide.
', ], ], 'TagResourceRequest' => [ 'base' => NULL, 'refs' => [], ], 'TagValueType' => [ 'base' => NULL, 'refs' => [ 'Tag$Value' => 'The string value associated with the key of the tag.
', ], ], 'TimestampType' => [ 'base' => NULL, 'refs' => [ 'DescribeSecretResponse$CreatedDate' => 'The date the secret was created.
', 'SecretListEntry$CreatedDate' => 'The date and time when a secret was created.
', ], ], 'UntagResourceRequest' => [ 'base' => NULL, 'refs' => [], ], 'UpdateSecretRequest' => [ 'base' => NULL, 'refs' => [], ], 'UpdateSecretResponse' => [ 'base' => NULL, 'refs' => [], ], 'UpdateSecretVersionStageRequest' => [ 'base' => NULL, 'refs' => [], ], 'UpdateSecretVersionStageResponse' => [ 'base' => NULL, 'refs' => [], ], 'ValidateResourcePolicyRequest' => [ 'base' => NULL, 'refs' => [], ], 'ValidateResourcePolicyResponse' => [ 'base' => NULL, 'refs' => [], ], 'ValidationErrorsEntry' => [ 'base' => 'Displays errors that occurred during validation of the resource policy.
', 'refs' => [ 'ValidationErrorsType$member' => NULL, ], ], 'ValidationErrorsType' => [ 'base' => NULL, 'refs' => [ 'ValidateResourcePolicyResponse$ValidationErrors' => 'Validation errors if your policy didn\'t pass validation.
', ], ], ],];