View source: R/secretsmanager_operations.R
secretsmanager_put_secret_value | R Documentation |
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.
See https://www.paws-r-sdk.com/docs/secretsmanager_put_secret_value/ for full documentation.
secretsmanager_put_secret_value(
SecretId,
ClientRequestToken = NULL,
SecretBinary = NULL,
SecretString = NULL,
VersionStages = NULL
)
SecretId |
[required] 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
|
ClientRequestToken |
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. 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 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.
This value becomes the |
SecretBinary |
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 You can't access this value from the Secrets Manager console. |
SecretString |
The text to encrypt and store in the new version of the secret. You must include We recommend you create the secret string as JSON key/value pairs, as shown in the example. |
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 If you don't include |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.