AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-02-25 · Documentation low

File: prescriptive-guidance/latest/security-reference-architecture/log-archive.md

Summary

Updated 'Amazon Quick Suite' to 'Amazon Quick' in analytics tool references.

Security assessment

A branding update with no impact on security controls, access policies, or log analysis procedures described in the documentation.

Diff

diff --git a/prescriptive-guidance/latest/security-reference-architecture/log-archive.md b/prescriptive-guidance/latest/security-reference-architecture/log-archive.md
index e174c6ee1..eca837cbf 100644
--- a//prescriptive-guidance/latest/security-reference-architecture/log-archive.md
+++ b//prescriptive-guidance/latest/security-reference-architecture/log-archive.md
@@ -58 +58 @@ AWS Security Hub CSPM is a supported native data source in Security Lake, and yo
-To gain visibility and actionable insights from logs and events, you can query the data by using tools such as [Amazon Athena](https://docs.aws.amazon.com/athena/latest/ug/what-is.html), [Amazon OpenSearch Service](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html), [Amazon Quick Suite](https://docs.aws.amazon.com/quicksuite/latest/userguide/what-is.html), and third-party solutions. Users who require access to the Security Lake log data shouldn't access the Log Archive account directly. They should access data only from the Security Tooling account. Or they can use other AWS accounts or on-premises locations that provide analytics tools such as OpenSearch Service, Quick Suite, or third-party tools such as security information and event management (SIEM) tools. To provide access to the data, the administrator should configure [Security Lake subscribers](https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-management.html) in the Log Archive account and configure the account that needs access to the data as a [query access subscriber](https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-query-access.html). For more information, see [Amazon Security Lake](./security-tooling.html#tool-security-lake) in the _Security OU ‒ Security Tooling account_ section of this guide.
+To gain visibility and actionable insights from logs and events, you can query the data by using tools such as [Amazon Athena](https://docs.aws.amazon.com/athena/latest/ug/what-is.html), [Amazon OpenSearch Service](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html), [Amazon Quick](https://docs.aws.amazon.com/quicksuite/latest/userguide/what-is.html), and third-party solutions. Users who require access to the Security Lake log data shouldn't access the Log Archive account directly. They should access data only from the Security Tooling account. Or they can use other AWS accounts or on-premises locations that provide analytics tools such as OpenSearch Service, Quick, or third-party tools such as security information and event management (SIEM) tools. To provide access to the data, the administrator should configure [Security Lake subscribers](https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-management.html) in the Log Archive account and configure the account that needs access to the data as a [query access subscriber](https://docs.aws.amazon.com/security-lake/latest/userguide/subscriber-query-access.html). For more information, see [Amazon Security Lake](./security-tooling.html#tool-security-lake) in the _Security OU ‒ Security Tooling account_ section of this guide.