AWS opensearch-service documentation change
Summary
Updated blueprint name from 'Firewall Traffic logs' to 'Security Lake'
Security assessment
Simple naming change without security implications. Doesn't address vulnerabilities or add security-specific documentation.
Diff
diff --git a/opensearch-service/latest/developerguide/configure-client-sink-security-lake.md b/opensearch-service/latest/developerguide/configure-client-sink-security-lake.md index 5fb98ce76..3912cff11 100644 --- a//opensearch-service/latest/developerguide/configure-client-sink-security-lake.md +++ b//opensearch-service/latest/developerguide/configure-client-sink-security-lake.md @@ -13 +13 @@ Use the Amazon S3 sink plugin in OpenSearch Ingestion to send data from any supp -To configure your pipeline to write log data to Security Lake, use the preconfigured **Firewall Traffic logs** blueprint. The blueprint includes a default configuration for retrieving raw security logs or other data stored in an Amazon S3 bucket, processing the records, and normalizing them. It then maps the data to Open Cybersecurity Schema Framework (OCSF) and sends the transformed OCSF-compliant data to Security Lake. +To configure your pipeline to write log data to Security Lake, use the preconfigured **Security Lake** blueprint. The blueprint includes a default configuration for retrieving raw security logs or other data stored in an Amazon S3 bucket, processing the records, and normalizing them. It then maps the data to Open Cybersecurity Schema Framework (OCSF) and sends the transformed OCSF-compliant data to Security Lake.