AWS secretsmanager documentation change
Summary
Updated method names in Lambda rotation function documentation from snake_case to camelCase (e.g. create_secret → createSecret)
Security assessment
The changes appear to be documentation formatting updates to align with naming conventions rather than addressing security vulnerabilities. No security implications are mentioned in the diff.
Diff
diff --git a/secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md b/secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md index b4ccf1b8e..7f2ed6d6a 100644 --- a//secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md +++ b//secretsmanager/latest/userguide/rotate-secrets_lambda-functions.md @@ -40 +40 @@ Setting the provisioned concurrency parameter to a value lower than 10 can cause - * create_secret: Create a new version of the secret + * createSecret: Create a new version of the secret @@ -42 +42 @@ Setting the provisioned concurrency parameter to a value lower than 10 can cause - * set_secret: Change the credentials in the database or service + * setSecret: Change the credentials in the database or service @@ -44 +44 @@ Setting the provisioned concurrency parameter to a value lower than 10 can cause - * test_secret: Test the new secret version + * testSecret: Test the new secret version @@ -46 +46 @@ Setting the provisioned concurrency parameter to a value lower than 10 can cause - * finish_secret: Finish the rotation + * finishSecret: Finish the rotation @@ -51 +51 @@ Setting the provisioned concurrency parameter to a value lower than 10 can cause -### `create_secret`: Create a new version of the secret +### `createSecret`: Create a new version of the secret @@ -53 +53 @@ Setting the provisioned concurrency parameter to a value lower than 10 can cause -The method `create_secret` first checks if a secret exists by calling [`get_secret_value`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.get_secret_value) with the passed-in `ClientRequestToken`. If there's no secret, it creates a new secret with [`create_secret`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.create_secret) and the token as the `VersionId`. Then it generates a new secret value with [`get_random_password`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.get_random_password). Next it calls [`put_secret_value`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.put_secret_value) to store it with the staging label ``AWSPENDING``. Storing the new secret value in ``AWSPENDING`` helps ensure idempotency. If rotation fails for any reason, you can refer to that secret value in subsequent calls. See [How do I make my Lambda function idempotent](https://aws.amazon.com/premiumsupport/knowledge-center/lambda-function-idempotent/). +The method `createSecret` first checks if a secret exists by calling [`get_secret_value`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.get_secret_value) with the passed-in `ClientRequestToken`. If there's no secret, it creates a new secret with [`create_secret`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.create_secret) and the token as the `VersionId`. Then it generates a new secret value with [`get_random_password`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.get_random_password). Next it calls [`put_secret_value`](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/secretsmanager.html#SecretsManager.Client.put_secret_value) to store it with the staging label ``AWSPENDING``. Storing the new secret value in ``AWSPENDING`` helps ensure idempotency. If rotation fails for any reason, you can refer to that secret value in subsequent calls. See [How do I make my Lambda function idempotent](https://aws.amazon.com/premiumsupport/knowledge-center/lambda-function-idempotent/). @@ -66 +66 @@ The method `create_secret` first checks if a secret exists by calling [`get_secr -### **set_secret** : Change the credentials in the database or service +### **setSecret** : Change the credentials in the database or service @@ -68 +68 @@ The method `create_secret` first checks if a secret exists by calling [`get_secr -The method `set_secret` changes the credential in the database or service to match the new secret value in the `AWSPENDING` version of the secret. +The method `setSecret` changes the credential in the database or service to match the new secret value in the `AWSPENDING` version of the secret. @@ -87 +87 @@ The method `set_secret` changes the credential in the database or service to mat -### **test_secret** : Test the new secret version +### **testSecret** : Test the new secret version @@ -91 +91 @@ Next, the Lambda rotation function tests the `AWSPENDING` version of the secret -### **finish_secret** : Finish the rotation +### **finishSecret** : Finish the rotation