AWS managedservices documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in Secrets Manager rotation documentation
Security assessment
Terminology update in existing security control context. Highlights existing permission restrictions but does not introduce new security features or address vulnerabilities.
Diff
diff --git a/managedservices/latest/userguide/secrets-manager.md b/managedservices/latest/userguide/secrets-manager.md index 251704143..c983814eb 100644 --- a//managedservices/latest/userguide/secrets-manager.md +++ b//managedservices/latest/userguide/secrets-manager.md @@ -23 +23 @@ Request access to Secrets Manager by submitting an RFC with the Management | AWS -Full functionality of AWS Secrets Manager is available in your AMS account, along with automatic rotation functionality of secrets. However, note that setting up your rotation using 'Create a new Lambda function to perform rotation' is not supported because it requires elevated permissions to create the AWS CloudFormation stack (IAM Role and Lambda function creation), which bypasses the Change Management process. AMS Advanced only supports 'Use an existing Lambda function to perform rotation' where you manage your Lambda functions to rotate secrets using the AWS Lambda SSPS Admin role. AMS Advanced doesn't create or manage Lambda to rotate the secrets. +Full functionality of AWS Secrets Manager is available in your AMS account, along with automatic rotation functionality of secrets. However, note that setting up your rotation using 'Create a new Lambda function to perform rotation' is not supported because it requires elevated permissions to create the CloudFormation stack (IAM Role and Lambda function creation), which bypasses the Change Management process. AMS Advanced only supports 'Use an existing Lambda function to perform rotation' where you manage your Lambda functions to rotate secrets using the AWS Lambda SSPS Admin role. AMS Advanced doesn't create or manage Lambda to rotate the secrets.