AWS security-lake: Fix URL for custom sources best practices
Summary
Corrected a documentation URL by removing an extra slash.
Security assessment
Only repairs a broken link; no security implications or content changes.
Evidence
+If you created a custom source, to ensure that custom source data is replicated properly to the destination, Security Lake recommends following the best practices described in [Best practices for ingesting custom sources](https://docs.aws.amazon.com/security-lake/latest/userguide/custom-sources.html#custom-sources-best-practices). Replication cannot be performed on data that does not follow the S3 partition data path format as described on the page.
Diff
diff --git a/security-lake/latest/userguide/add-rollup-region.md b/security-lake/latest/userguide/add-rollup-region.md index eab38e191..841f49345 100644 --- a//security-lake/latest/userguide/add-rollup-region.md +++ b//security-lake/latest/userguide/add-rollup-region.md @@ -17 +17 @@ Due to limitations in Amazon S3, replication from Customer Managed Key (CMK) enc -If you created a custom source, to ensure that custom source data is replicated properly to the destination, Security Lake recommends following the best practices described in [Best practices for ingesting custom sources](https://docs.aws.amazon.com//security-lake/latest/userguide/custom-sources.html#custom-sources-best-practices). Replication cannot be performed on data that does not follow the S3 partition data path format as described on the page. +If you created a custom source, to ensure that custom source data is replicated properly to the destination, Security Lake recommends following the best practices described in [Best practices for ingesting custom sources](https://docs.aws.amazon.com/security-lake/latest/userguide/custom-sources.html#custom-sources-best-practices). Replication cannot be performed on data that does not follow the S3 partition data path format as described on the page.