put_secret_value¶
Operation¶
put_secret_value
async
¶
put_secret_value(input: PutSecretValueInput, plugins: list[Plugin] | None = None) -> PutSecretValueOutput
Creates a new version of your secret by creating a new encrypted value
and attaching it to the secret. version can contain a new SecretString
value or a new SecretBinary value.
Do not call 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 keeps 100 of the most recent
versions, but it keeps all secret versions created in the last 24
hours. If you call PutSecretValue more than once every 10 minutes, you
will 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, SecretString, or RotationToken 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.
Warning
When you enter commands in a command shell, there is a risk of the command history being accessed or utilities having access to your command parameters. This is a concern if the command includes the value of a secret. Learn how to Mitigate the risks of using command-line tools to store Secrets Manager secrets.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
input
|
PutSecretValueInput
|
An instance of |
required |
plugins
|
list[Plugin] | None
|
A list of callables that modify the configuration dynamically. Changes made by these plugins only apply for the duration of the operation execution and will not affect any other operation invocations. |
None
|
Returns:
| Type | Description |
|---|---|
PutSecretValueOutput
|
An instance of |
Input¶
PutSecretValueInput
dataclass
¶
Dataclass for PutSecretValueInput structure.
Attributes¶
client_request_token
class-attribute
instance-attribute
¶
client_request_token: str | None = None
A unique identifier for the new version of the secret.
Note
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 generate a raw HTTP request to the Secrets Manager service
endpoint, then you must generate a ClientRequestToken and include it
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
ClientRequestTokenvalue 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
SecretStringorSecretBinaryvalues 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
SecretStringandSecretBinaryvalues 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.
rotation_token
class-attribute
instance-attribute
¶
A unique identifier that indicates the source of the request. Required for secret rotations using an IAM assumed role or cross-account rotation, in which you rotate a secret in one account by using a Lambda rotation function in another account. In both cases, the rotation function assumes an IAM role to call Secrets Manager, and then Secrets Manager validates the identity using the token. For more information, see How rotation works and Rotation by Lambda functions.
Sensitive: This field contains sensitive information, so the service does not include it in CloudTrail log entries. If you create your own log entries, you must also avoid logging the information in this field.
secret_binary
class-attribute
instance-attribute
¶
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.
Sensitive: This field contains sensitive information, so the service does not include it in CloudTrail log entries. If you create your own log entries, you must also avoid logging the information in this field.
secret_id
class-attribute
instance-attribute
¶
secret_id: str | None = None
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.
secret_string
class-attribute
instance-attribute
¶
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.
Sensitive: This field contains sensitive information, so the service does not include it in CloudTrail log entries. If you create your own log entries, you must also avoid logging the information in this field.
version_stages
class-attribute
instance-attribute
¶
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.