AWS Security ChangesHomeSearch

AWS secretsmanager: Clarify AWSCURRENT label move in rotation flow

Service: secretsmanager · 2026-10-10 · Documentation low

File: secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md

Summary

Rewords the description of the final rotation step, removing the claim that moving AWSCURRENT also removes the AWSPENDING label in the same API call.

Security assessment

A wording correction about staging label behavior during rotation; it touches credential rotation mechanics but does not document a new security feature or fix a vulnerability.

Evidence

+Finally, the Lambda rotation function moves the label `AWSCURRENT` from the previous secret version to this version. Secrets Manager adds the `AWSPREVIOUS` staging label to the previous version, so that you retain the last known good version of the secret. 

Diff

diff --git a/secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md b/secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md
index a701ce0..763bd6a 100644
--- a//secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md
+++ b//secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md
@@ -95 +95 @@ Next, the Lambda rotation function tests the `AWSPENDING` version of the secret
-Finally, the Lambda rotation function moves the label `AWSCURRENT` from the previous secret version to this version, which also removes the `AWSPENDING` label in the same API call. Secrets Manager adds the `AWSPREVIOUS` staging label to the previous version, so that you retain the last known good version of the secret. 
+Finally, the Lambda rotation function moves the label `AWSCURRENT` from the previous secret version to this version. Secrets Manager adds the `AWSPREVIOUS` staging label to the previous version, so that you retain the last known good version of the secret.