AWS Security ChangesHomeSearch

AWS security-lake documentation change

Service: security-lake · 2025-11-22 · Documentation low

File: security-lake/latest/userguide/best-practices-overview.md

Summary

Fixed a broken URL in the AWS Lambda developer guide reference.

Security assessment

This is a documentation link fix with no security implications or vulnerability remediation.

Diff

diff --git a/security-lake/latest/userguide/best-practices-overview.md b/security-lake/latest/userguide/best-practices-overview.md
index 64b30a491..496d6558f 100644
--- a//security-lake/latest/userguide/best-practices-overview.md
+++ b//security-lake/latest/userguide/best-practices-overview.md
@@ -29 +29 @@ For more information, see [Integration with AWS Security Hub](./securityhub-inte
-When deleting a AWS Lambda function, we recommend against disabling it first. Disabling a Lambda function before deletion could interfere with data querying capabilities and potentially impact other functionalities. It's best to delete the Lambda function directly without disabling it. For more information on deleting Lambda function, see [AWS Lambda developer guide](https://docs.aws.amazon.com/lambda/latest/dg/example_lambda_DeleteFunction_section.html).
+When deleting a AWS Lambda function, we recommend against disabling it first. Disabling a Lambda function before deletion could interfere with data querying capabilities and potentially impact other functionalities. It's best to delete the Lambda function directly without disabling it. For more information on deleting Lambda function, see [AWS Lambda developer guide](https://docs.aws.amazon.com//lambda/latest/dg/example_lambda_DeleteFunction_section.html).