AWS Security ChangesHomeSearch

AWS codecommit documentation change

Service: codecommit · 2025-08-13 · Documentation low

File: codecommit/latest/userguide/how-to-notify.md

Summary

Removed documentation about cross-account SNS topic policies and an example policy reference for Lambda integration

Security assessment

The change removes references to configuring cross-account SNS policies and an example policy link, but there's no explicit evidence of addressing a security vulnerability. It appears to streamline documentation without altering security guidance.

Diff

diff --git a/codecommit/latest/userguide/how-to-notify.md b/codecommit/latest/userguide/how-to-notify.md
index 41d8c1820..f97e6c035 100644
--- a//codecommit/latest/userguide/how-to-notify.md
+++ b//codecommit/latest/userguide/how-to-notify.md
@@ -57,3 +57 @@ You can integrate Amazon SNS topics and Lambda functions with triggers in CodeCo
-  * If you want to configure your trigger to use an Amazon SNS topic in another AWS account, you must first configure that topic with a policy that allows CodeCommit to publish to that topic. For more information, see [Example 1: Create a policy that enables cross-account access to an Amazon SNS topic](./customer-managed-policies.html#access-permissions-sns-int).
-
-  * You can configure Lambda functions by creating the trigger in the Lambda console as part of the function. This is the simplest method, because triggers created in the Lambda console automatically include the permissions required for CodeCommit to invoke the Lambda function. If you create the trigger in CodeCommit, you must include a policy to allow CodeCommit to invoke the function. For more information, see [Create a trigger for an existing Lambda function](./how-to-notify-lambda-cc.html) and [Example 3: Create a policy for AWS Lambda integration with a CodeCommit trigger](./customer-managed-policies.html#access-permissions-lambda-int).
+  * You can configure Lambda functions by creating the trigger in the Lambda console as part of the function. This is the simplest method, because triggers created in the Lambda console automatically include the permissions required for CodeCommit to invoke the Lambda function. If you create the trigger in CodeCommit, you must include a policy to allow CodeCommit to invoke the function. For more information, see [Create a trigger for an existing Lambda function](./how-to-notify-lambda-cc.html).