updateSecret method
Modifies many of the details of the specified secret. If you include a
ClientRequestToken
and either
SecretString
or SecretBinary
then it also
creates a new version attached to the secret.
To modify the rotation configuration of a secret, use RotateSecret instead.
-
If a version with a
VersionId
with the same value as theClientRequestToken
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
orSecretBinary
to create a new secret version, Secrets Manager automatically attaches the staging labelAWSCURRENT
to the new version.
To run this command, you must have the following permissions:
- secretsmanager:UpdateSecret
- kms:GenerateDataKey - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager.
- kms:Decrypt - needed only if you use a custom AWS KMS key to encrypt the secret. You do not need this permission to use the account's AWS managed CMK for Secrets Manager.
- 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.
May throw InvalidParameterException. May throw InvalidRequestException. May throw LimitExceededException. May throw EncryptionFailure. May throw ResourceExistsException. May throw ResourceNotFoundException. May throw MalformedPolicyDocumentException. May throw InternalServiceError. May throw PreconditionNotMetException.
Parameter secretId
:
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.
If you specify an incomplete ARN without the random suffix, and instead provide the 'friendly name', you must not include the random suffix. If you do include the random suffix added by Secrets Manager, you receive either a ResourceNotFoundException or an AccessDeniedException error, depending on your permissions.
Parameter clientRequestToken
:
(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 AWS CLI or one of the AWS 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 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 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
andSecretBinary
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 that version's
SecretString
andSecretBinary
values are different from the request then an error occurs because you cannot modify an existing secret value.
VersionId
of the new version.
Parameter description
:
(Optional) Specifies an updated user-provided description of the secret.
Parameter kmsKeyId
:
(Optional) Specifies an updated ARN or alias of the AWS KMS customer
master key (CMK) to be used to encrypt the protected text in new versions
of this secret.
Parameter secretBinary
:
(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.
This parameter is not accessible using the Secrets Manager console.
Parameter secretString
:
(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 information on how to format a JSON parameter for the various command line tool environments, see Using JSON for Parameters in the AWS CLI User Guide. For example:
{"username":"bob"},{"password":"abc123xyz456"}
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. You can also 'escape' the double quote character in the embedded JSON text by prefacing each with a backslash. For example, the following string is surrounded by double-quotes. All of the embedded double quotes are escaped:
"
{\"username\":\"bob\"},{\"password\":\"abc123xyz456\"}
"
Implementation
Future<UpdateSecretResponse> updateSecret({
required String secretId,
String? clientRequestToken,
String? description,
String? kmsKeyId,
Uint8List? secretBinary,
String? secretString,
}) async {
ArgumentError.checkNotNull(secretId, 'secretId');
_s.validateStringLength(
'secretId',
secretId,
1,
2048,
isRequired: true,
);
_s.validateStringLength(
'clientRequestToken',
clientRequestToken,
32,
64,
);
_s.validateStringLength(
'description',
description,
0,
2048,
);
_s.validateStringLength(
'kmsKeyId',
kmsKeyId,
0,
2048,
);
_s.validateStringLength(
'secretString',
secretString,
0,
65536,
);
final headers = <String, String>{
'Content-Type': 'application/x-amz-json-1.1',
'X-Amz-Target': 'secretsmanager.UpdateSecret'
};
final jsonResponse = await _protocol.send(
method: 'POST',
requestUri: '/',
exceptionFnMap: _exceptionFns,
// TODO queryParams
headers: headers,
payload: {
'SecretId': secretId,
'ClientRequestToken':
clientRequestToken ?? _s.generateIdempotencyToken(),
if (description != null) 'Description': description,
if (kmsKeyId != null) 'KmsKeyId': kmsKeyId,
if (secretBinary != null) 'SecretBinary': base64Encode(secretBinary),
if (secretString != null) 'SecretString': secretString,
},
);
return UpdateSecretResponse.fromJson(jsonResponse.body);
}