AWS secretsmanager documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' throughout the document, removed redundant AWS branding in service names, and adjusted console references/links.
Security assessment
The changes are editorial in nature, focusing on branding consistency (removing redundant 'AWS' from CloudFormation references) and documentation formatting. While the context involves updating Lambda rotation functions (which could relate to security maintenance), the specific changes in this diff do not address vulnerabilities, security incidents, or add new security guidance. The Python 3.7 deprecation mentioned in the surrounding text relates to runtime updates, but the diff itself does not introduce security fixes or documentation for security features.
Diff
diff --git a/secretsmanager/latest/userguide/troubleshoot_rotation.md b/secretsmanager/latest/userguide/troubleshoot_rotation.md index a415d82e0..e967e9889 100644 --- a//secretsmanager/latest/userguide/troubleshoot_rotation.md +++ b//secretsmanager/latest/userguide/troubleshoot_rotation.md @@ -266 +266 @@ Some rotation functions created before November 2022 used Python 3.7. The AWS SD - * Option 1: Recreate the rotation function using AWS CloudFormation + * Option 1: Recreate the rotation function using CloudFormation @@ -268 +268 @@ Some rotation functions created before November 2022 used Python 3.7. The AWS SD - * Option 2: Update the runtime for the existing rotation function using AWS CloudFormation + * Option 2: Update the runtime for the existing rotation function using CloudFormation @@ -275 +275 @@ Some rotation functions created before November 2022 used Python 3.7. The AWS SD -### Option 1: Recreate the rotation function using AWS CloudFormation +### Option 1: Recreate the rotation function using CloudFormation @@ -277 +277 @@ Some rotation functions created before November 2022 used Python 3.7. The AWS SD -When you use the Secrets Manager console to turn on rotation, Secrets Manager uses AWS CloudFormation to create the necessary resources, including the Lambda rotation function. If you used the console to turn on rotation, or you created the rotation function using a AWS CloudFormation stack, you can use the same AWS CloudFormation stack to recreate the rotation function with a new name. The new function uses the more recent version of Python. +When you use the Secrets Manager console to turn on rotation, Secrets Manager uses CloudFormation to create the necessary resources, including the Lambda rotation function. If you used the console to turn on rotation, or you created the rotation function using a CloudFormation stack, you can use the same CloudFormation stack to recreate the rotation function with a new name. The new function uses the more recent version of Python. @@ -279 +279 @@ When you use the Secrets Manager console to turn on rotation, Secrets Manager us -###### To find the AWS CloudFormation stack that created the rotation function +###### To find the CloudFormation stack that created the rotation function @@ -292 +292 @@ The stack name is embedded in the ARN, as shown in the following example. -###### To recreate a rotation function (AWS CloudFormation) +###### To recreate a rotation function (CloudFormation) @@ -294 +294 @@ The stack name is embedded in the ARN, as shown in the following example. - 1. In AWS CloudFormation, search for the stack by name, and then choose **Update**. + 1. In CloudFormation, search for the stack by name, and then choose **Update**. @@ -306 +306 @@ If a dialog box appears recommending you update the root stack, choose **Go to r - 3. In the **Continue to AWS CloudFormation** dialog box, choose **Confirm and continue to AWS CloudFormation**. + 3. In the **Continue to CloudFormation** dialog box, choose **Confirm and continue to CloudFormation**. @@ -308 +308 @@ If a dialog box appears recommending you update the root stack, choose **Go to r - 4. Continue through the AWS CloudFormation stack workflow and then choose **Submit**. + 4. Continue through the CloudFormation stack workflow and then choose **Submit**. @@ -313 +313 @@ If a dialog box appears recommending you update the root stack, choose **Go to r -### Option 2: Update the runtime for the existing rotation function using AWS CloudFormation +### Option 2: Update the runtime for the existing rotation function using CloudFormation @@ -315 +315 @@ If a dialog box appears recommending you update the root stack, choose **Go to r -When you use the Secrets Manager console to turn on rotation, Secrets Manager uses AWS CloudFormation to create the necessary resources, including the Lambda rotation function. If you used the console to turn on rotation, or you created the rotation function using a AWS CloudFormation stack, you can use the same AWS CloudFormation stack to update the runtime for the rotation function. +When you use the Secrets Manager console to turn on rotation, Secrets Manager uses CloudFormation to create the necessary resources, including the Lambda rotation function. If you used the console to turn on rotation, or you created the rotation function using a CloudFormation stack, you can use the same CloudFormation stack to update the runtime for the rotation function. @@ -317 +317 @@ When you use the Secrets Manager console to turn on rotation, Secrets Manager us -###### To find the AWS CloudFormation stack that created the rotation function +###### To find the CloudFormation stack that created the rotation function @@ -330 +330 @@ The stack name is embedded in the ARN, as shown in the following example. -###### To update the runtime for a rotation function (AWS CloudFormation) +###### To update the runtime for a rotation function (CloudFormation) @@ -332 +332 @@ The stack name is embedded in the ARN, as shown in the following example. - 1. In AWS CloudFormation, search for the stack by name, and then choose **Update**. + 1. In CloudFormation, search for the stack by name, and then choose **Update**. @@ -344 +344 @@ If a dialog box appears recommending you update the root stack, choose **Go to r - 3. In the **Continue to AWS CloudFormation** dialog box, choose **Confirm and continue to AWS CloudFormation**. + 3. In the **Continue to CloudFormation** dialog box, choose **Confirm and continue to CloudFormation**. @@ -346 +346 @@ If a dialog box appears recommending you update the root stack, choose **Go to r - 4. Continue through the AWS CloudFormation stack workflow and then choose **Submit**. + 4. Continue through the CloudFormation stack workflow and then choose **Submit**. @@ -372 +372 @@ Secrets Manager is transitioning from Python 3.9 to 3.10 for Lambda rotation fun -The Lambda rotation functions identified in this list can be deployed through Secrets Manager console, AWS Serverless Application Repository apps, or AWS CloudFormation transforms. Each of these deployment strategies have a distinct update path. +The Lambda rotation functions identified in this list can be deployed through Secrets Manager console, AWS Serverless Application Repository apps, or CloudFormation transforms. Each of these deployment strategies have a distinct update path. @@ -442 +442 @@ If the Lambda function is deployed through this transform, [updating the stacks -Use the following procedure to update AWS CloudFormation stack using existing template. +Use the following procedure to update CloudFormation stack using existing template. @@ -444 +444 @@ Use the following procedure to update AWS CloudFormation stack using existing te - 1. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 1. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). @@ -459 +459 @@ Use the following procedure to update AWS CloudFormation stack using existing te -If you experience issues updating the stack, see [Determine the cause of a stack failure](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/determine-root-cause-for-stack-failures.html) in the _AWS CloudFormation User Guide_. +If you experience issues updating the stack, see [Determine the cause of a stack failure](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/determine-root-cause-for-stack-failures.html) in the _CloudFormation User Guide_. @@ -464 +464 @@ AWS::SecretsManager-2020-07-23 transform macro -We recommend you migrate to the newer transform version if you're using `AWS::SecretsManager-2020-07-23`. See [Introducing an enhanced version of the AWS Secrets Manager transform: AWS::SecretsManager-2024-09-16](https://aws.amazon.com/blogs/security/introducing-an-enhanced-version-of-the-aws-secrets-manager-transform-awssecretsmanager-2024-09-16/) in the _AWS Security Blog_ for more information. If you continue to use `AWS::SecretsManager-2020-07-23`, you can experience a mismatch error between your runtime version and the Lambda function code artifacts. For more information, see [AWS::SecretsManager::RotationSchedule HostedRotationLambda](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-secretsmanager-rotationschedule-hostedrotationlambda.html#cfn-secretsmanager-rotationschedule-hostedrotationlambda-runtime) in the _AWS CloudFormation Template Reference_. +We recommend you migrate to the newer transform version if you're using `AWS::SecretsManager-2020-07-23`. See [Introducing an enhanced version of the AWS Secrets Manager transform: AWS::SecretsManager-2024-09-16](https://aws.amazon.com/blogs/security/introducing-an-enhanced-version-of-the-aws-secrets-manager-transform-awssecretsmanager-2024-09-16/) in the _AWS Security Blog_ for more information. If you continue to use `AWS::SecretsManager-2020-07-23`, you can experience a mismatch error between your runtime version and the Lambda function code artifacts. For more information, see [AWS::SecretsManager::RotationSchedule HostedRotationLambda](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-secretsmanager-rotationschedule-hostedrotationlambda.html#cfn-secretsmanager-rotationschedule-hostedrotationlambda-runtime) in the _CloudFormation Template Reference_. @@ -466 +466 @@ We recommend you migrate to the newer transform version if you're using `AWS::Se -If you experience issues updating the stack, [Determine the cause of a stack failure](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/determine-root-cause-for-stack-failures.html) in the _AWS CloudFormation User Guide_. +If you experience issues updating the stack, [Determine the cause of a stack failure](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/determine-root-cause-for-stack-failures.html) in the _CloudFormation User Guide_.