# Amazon Security Lake

Amazon Security Lake centralizes security data from AWS environments, external providers, and custom sources in a customer-owned data lake on Amazon S3.

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-security-lake

> Amazon Security Lake collects supported AWS security logs and findings, converts them to a common schema, and organizes them for analysis across accounts and Regions. Engineers can connect analytics tools and security platforms through controlled subscriber access while retaining control over storage, retention, and encryption.

Practice exams covering Amazon Security Lake: [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 9 key features of Amazon Security Lake

1. **Managed collection of AWS security telemetry**: Enable supported AWS log and finding sources without building a separate collection pipeline for each one. Select sources by account and Region to match your investigation requirements and control ingestion volume.
2. **OCSF normalization and Parquet storage**: Security Lake converts supported AWS source records into OCSF and stores them in Apache Parquet format. Analysts can correlate common fields across different sources while using column-oriented query engines.
3. **Customer-owned S3 storage**: Security data resides in S3 buckets in your account. Configure retention, storage transitions, and encryption requirements while preserving the permissions needed by Security Lake.
4. **Organization-wide administration**: Use AWS Organizations and a delegated administrator to manage collection across member accounts. Centrally configure which accounts and sources participate instead of maintaining independent pipelines in every account.
5. **Regional collection and rollup**: Collect data in enabled Regions and configure rollup Regions for consolidated access. Evaluate replication costs and data residency requirements before selecting aggregation destinations.
6. **Custom source ingestion**: Integrate external security products and internal applications through custom sources. Producers must deliver records in the required OCSF-compatible schema and Parquet format.
7. **Controlled subscriber access**: Create subscribers for object-level data access or Lake Formation-based query access. Scope each subscriber to the source datasets it needs rather than granting broad bucket access.
8. **Cataloged analytical datasets**: Security Lake maintains dataset metadata through AWS Glue Data Catalog and integrates with Lake Formation permissions. Query-capable consumers can use this metadata to discover and analyze authorized tables.
9. **CloudWatch operational metrics**: Security Lake automatically collects and publishes data lake metrics to Amazon CloudWatch at one-minute intervals. Use CloudWatch to view and analyze these metrics and configure alarms for specified thresholds.

## Where Amazon Security Lake is used

1. **Cross-account incident investigation**: Centralize relevant telemetry from production, development, and shared-services accounts so investigators can trace activity across account boundaries. Use a query engine to correlate API activity, network flows, and DNS requests.
2. **Threat hunting across different data sources**: Use OCSF-normalized fields to investigate suspicious identities, IP addresses, or resources across multiple datasets. Validate source-specific field mappings before building reusable hunting queries.
3. **Supplying data to security analytics platforms**: Give a SIEM or detection platform subscriber access to selected datasets. Object notifications can drive incremental ingestion without repeatedly scanning the entire lake.
4. **Security telemetry retention**: Retain security records independently of the operational retention settings in downstream analysis tools. Apply storage lifecycle policies that balance historical investigation needs with storage and retrieval costs.
5. **Combining AWS and external security data**: Publish endpoint, identity, or application security events through custom sources and analyze them alongside AWS telemetry. Build producer-side validation so malformed records do not undermine investigations.

## How Amazon Security Lake is priced

- **Usage-based AWS data ingestion and normalization**: Security Lake charges for ingestion and normalization of supported AWS source data according to its pricing dimensions. Rates depend on the Region and source category; use source volumes and the applicable billing definitions when estimating costs.
- **Custom and third-party source data**: Security Lake does not charge its ingestion and normalization fees for third-party or custom source data. Producers remain responsible for preparing compliant data, and storage, delivery, and other supporting services can still incur charges.
- **Storage and supporting AWS services**: Amazon S3 storage, requests, lifecycle transitions, retrieval, replication, and applicable data transfer are billed separately. Include AWS KMS and other supporting service usage where applicable.
- **Analytics and downstream consumption**: Query engines and connected security platforms have their own pricing. For example, Athena queries incur Athena charges, while a subscriber platform may charge for ingestion, processing, or retained data.
- **15-day free trial**: New Security Lake accounts can try the service free for 15 days in supported Regions, with access to all features.

## Services Amazon Security Lake works with

A common architecture places Security Lake administration in a dedicated security account and uses AWS Organizations to manage collection across member accounts. Data is stored in Regional S3 buckets, with optional rollup Regions for consolidated analysis. AWS Glue Data Catalog describes the resulting datasets, while Lake Formation controls query-access subscribers. Encryption permissions must align with both the collection workflow and the consumers that need to read the data.

For interactive investigation, analysts commonly use Athena against authorized Security Lake tables. Queries should restrict time ranges and relevant partitions, and select only necessary columns to limit scanned data. Security Hub findings provide useful investigation starting points that can be correlated with API activity, network flows, and DNS telemetry.

For continuous downstream processing, configure a data-access subscriber and use SQS notifications to trigger retrieval of newly available S3 objects. A SIEM or custom analytics worker should tolerate retries and process objects idempotently. External producers can also contribute custom sources, but must prepare compliant OCSF and Parquet data before delivery. Across both ingestion and consumption paths, monitor delivery health, access failures, schema compatibility, and the cost of storage, queries, and replication.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Security Lake stores normalized security records in customer-owned S3 buckets. For example, retain recent records in an immediately accessible storage class and transition older objects according to investigation and retention requirements. Account for retrieval constraints before moving data to archival storage.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: AWS Organizations enables centralized Security Lake administration across member accounts through a delegated administrator. For example, a security account can manage collection for application accounts and configure organization-wide onboarding behavior. Align account inclusion and Regional settings with your organization's security boundaries.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Security Lake uses AWS Glue Data Catalog to describe its security datasets. For example, an analyst can discover a source table and inspect its schema before writing a query. Validate table and schema versions when maintaining saved queries.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: Lake Formation provides the permissions model for Security Lake query-access subscribers. For example, grant an analytics account access to selected security datasets without granting unrestricted access to all lake contents. Coordinate Lake Formation grants with IAM permissions and encryption access.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: Athena can query Security Lake datasets using catalog metadata and the required Lake Formation permissions. For example, investigators can search CloudTrail activity for a compromised role and correlate the results with network telemetry. Filter by relevant partitions and select only needed columns to reduce scanned data.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub findings are a supported Security Lake source, allowing findings to be analyzed alongside underlying telemetry. For example, investigate a resource associated with a finding by querying its API activity and related network flows. Security Lake stores the data for analysis; it does not replace Security Hub's finding-management workflows.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: Security Lake data can feed security-analysis workflows that use Amazon Bedrock foundation models to generate insights and explain suspicious activity. These workflows can use retrieved security records to provide context for an investigation.
- **[Amazon Detective](https://blowstack.com/tools/cloud-services-hub/amazon-detective)**: Security Lake integrates with Amazon Detective so investigators can query centrally collected logs during an investigation. Detective can retrieve relevant Security Lake records to help investigate entities and activities associated with security findings.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Security Lake natively collects Amazon EKS audit logs and converts them into OCSF records stored in Apache Parquet format. These records let security teams investigate Kubernetes API activity alongside other security events.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Security Lake uses Amazon EventBridge to notify subscribers when new objects are written to the data lake. Subscriber notification settings support delivery through HTTPS endpoints or Amazon SQS queues.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: Security Lake integrates with OpenSearch Ingestion to load security records into Amazon OpenSearch Service for analysis and visualization. OpenSearch Service also supports zero-ETL direct queries against Security Lake data, while OpenSearch Ingestion can normalize custom-source data and write it into Security Lake.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: Security Lake data can be visualized in Amazon QuickSight through Amazon Athena queries over its cataloged tables. Dashboards can summarize security events, show activity trends, and compare findings across accounts.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Security Lake data can be queried from Amazon Redshift using Redshift Spectrum and the tables registered in the AWS Glue Data Catalog. This allows analysts to join security logs with other analytical datasets without first loading those logs into Redshift tables.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Security Lake natively collects Route 53 Resolver query logs and normalizes them into OCSF records. Analysts can use these records to investigate DNS queries, such as requests for suspicious domains.
- **[Amazon S3 Glacier](https://blowstack.com/tools/cloud-services-hub/amazon-s3-glacier)**: Security Lake lifecycle settings can transition stored security data into S3 Glacier storage classes for lower-cost archival retention. Objects in archival classes that require restoration must be restored before their contents can be queried.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Security Lake data can be accessed from Amazon SageMaker for machine-learning analysis of security activity. Analysts can use notebooks and models to explore normalized events and identify unusual patterns.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: Security Lake uses Amazon SQS queues to notify data-access subscribers when new security-log objects are available. Subscribers consume these notifications and retrieve the corresponding objects for processing.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Security Lake natively collects VPC Flow Logs and converts them into OCSF records in Apache Parquet format. These records support investigations of network traffic, including unexpected connections and rejected traffic.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Security Lake resources can be provisioned with AWS CloudFormation, including data lakes, AWS log sources, subscribers, and subscriber notification configurations. Templates provide a repeatable way to deploy security-log collection and subscriber access.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Security Lake natively ingests CloudTrail management events and supported Amazon S3 and AWS Lambda data events, normalizing them into OCSF records. CloudTrail also records Security Lake API activity so administrators can audit changes to data lakes, sources, and subscribers.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Security Lake uses IAM policies and roles to authorize administration, collect source data, manage its supporting resources, and grant subscribers access. Service-linked roles provide the permissions needed for Security Lake to operate on your behalf.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Security Lake encrypts its stored data using AWS KMS and supports customer-managed keys for its data lake. Key policies must allow the required Security Lake operations and authorized subscriber access.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Security Lake uses Lambda functions for data-processing tasks and to register source-data partitions in the AWS Glue Data Catalog. It also natively collects Lambda invocation data events through its CloudTrail source integration.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Security Lake supports interface VPC endpoints through AWS PrivateLink. Applications and administrative tools in a VPC can access the Security Lake API privately without requiring an internet gateway or NAT device.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: Security Lake uses AWS RAM resource sharing when granting cross-account subscribers query access to Lake Formation tables. Subscribers accept the resource share to access the shared security-data tables from their own accounts.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Security Lake data-access subscribers use AWS STS to assume the IAM role that grants access to the lake's objects. The subscriber's external ID is used in the role's trust relationship to restrict who can assume it.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: Security Lake natively collects AWS WAFv2 logs and converts them into OCSF records in Apache Parquet format. These records let analysts investigate inspected web requests and rule actions alongside other security telemetry.

## Amazon Security Lake exam questions

Real practice exam questions on Amazon Security Lake, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A company uses Amazon Security Lake to collect security logs from its AWS Organizations member accounts in three AWS Regions. Two Regions replicate their collected data to a designated rollup Region. Investigators query the consolidated data in the rollup Region. No storage-class transitions or expiration settings are currently configured.

The company's retention policy requires source-Region copies to expire after 30 days and consolidated copies in the rollup Region to remain available for 400 days. Investigators must be able to query the most recent 30 days of consolidated records without restoring objects. Older consolidated records can require a restore operation that takes several hours. The company wants to reduce storage costs by archiving older consolidated records.

Which configuration meets these requirements?

**Correct answer:** Configure a 30-day expiration in each source Region. In the rollup Region, configure a transition to S3 Glacier Flexible Retrieval after 30 days and expiration after 400 days.

**Explanation:** Security Lake lifecycle settings are regional. The source Regions can expire their copies after 30 days while the rollup Region retains its independently managed copies for 400 days. Transitioning consolidated objects to S3 Glacier Flexible Retrieval after 30 days preserves immediate query access to recent records and provides lower-cost archival storage for older records that can tolerate restoration.

### Question 2 (SCS-C03)

**Question:**

A company uses AWS Organizations to manage 60 accounts with workloads in three AWS Regions. The security team must collect CloudTrail management events and VPC Flow Logs from every account in all three Regions. Copies of all collected records must be consolidated into company-controlled object storage in one designated analysis Region, although Regional copies may remain.

The consolidated datasets must use a common security schema and a columnar format. A third-party security platform will analyze the datasets through an existing supported integration. The company wants managed collection, normalization, cataloging, and cross-Region consolidation without maintaining custom pipelines.

Which solution meets these requirements?

**Correct answer:** Designate an Amazon Security Lake delegated administrator. Enable the required sources for all organization accounts in each workload Region, and configure the analysis Region as a rollup Region with the other Regions as contributing Regions.

**Explanation:** Security Lake provides managed collection of the supported sources, normalizes them to OCSF, stores them as Parquet objects, and maintains catalog metadata. Enabling collection in every workload Region establishes coverage, while the rollup configuration consolidates copies into the analysis Region for independent analytics tools to consume.

## Practice Amazon Security Lake in a full exam

Questions on Amazon Security Lake in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions

## What is Amazon Security Lake

Amazon Security Lake provides a managed foundation for collecting and organizing security telemetry in your AWS account. It stores data in Amazon S3 rather than providing a built-in investigation console or detection engine. Security teams use the resulting lake with query services, security information and event management platforms, and other analytics applications. This separates collection and storage from the tools used to investigate or detect threats.

For supported AWS sources, Security Lake handles collection and converts records into the Open Cybersecurity Schema Framework, or OCSF. It stores normalized records in Apache Parquet format, which supports efficient analytical queries. Supported sources include AWS CloudTrail events, Amazon VPC Flow Logs, Amazon Route 53 Resolver query logs, and AWS Security Hub findings. Enable only the sources and source versions needed for your investigations, and verify availability in each deployment Region.

Custom sources allow applications and external security products to contribute data. Unlike supported AWS sources, custom producers must supply data that meets Security Lake requirements, including the applicable OCSF schema and Parquet format. Treat schema validation, delivery permissions, and producer monitoring as part of the integration rather than assuming Security Lake will transform arbitrary incoming records.

In a multi-account environment, use AWS Organizations and a delegated administrator to manage collection centrally. Configure the accounts, Regions, and sources included in the lake. Regional data collection can be combined with rollup Regions to consolidate copies for analysis. Choose this topology deliberately because aggregation affects data residency, storage consumption, replication traffic, and the location in which analysts run queries.

Security Lake uses AWS Glue Data Catalog metadata and AWS Lake Formation permissions to support governed access. Subscribers can receive access to S3 objects or query access through Lake Formation, depending on their integration model. Data-access subscribers can receive notifications when new objects become available. Grant subscribers only the accounts, Regions, and source datasets they require, and ensure encryption key policies allow the intended access.

Configure retention and storage transitions according to investigative and compliance requirements. A useful starting point is to keep recent data readily queryable and move older data to lower-cost storage where appropriate. Account for the retrieval behavior of the selected storage class before relying on archived data during an incident.

Security Lake does not support Amazon S3 Object Lock. It is disabled by default on newly created data lake buckets; enabling it interrupts delivery of normalized log data.

Operational readiness requires more than enabling collection. Monitor source delivery, custom producer health, subscriber processing, and access failures. Validate representative queries against each enabled source and OCSF version, and test whether investigators can retrieve the required history. Budget for Security Lake processing as well as S3 storage, analytical queries, encryption operations, and any applicable replication or transfer charges.

## Learn Amazon Security Lake in lessons

4 short lessons on Amazon Security Lake in 2 certification courses.

- SAP-C03: Amazon Security Lake: organization-wide collection topology (Premium), https://app.blowstack.com/lessons/amazon-security-lake-organization-wide-collection-topology-sap-c03
- SCS-C03: Amazon Security Lake: Normalized security data storage (Premium), https://app.blowstack.com/lessons/amazon-security-lake-normalized-security-data-storage-scs-c03
- SAP-C03: Amazon Security Lake and AWS Security Hub: telemetry lakes versus findings aggregation (Premium), https://app.blowstack.com/lessons/amazon-security-lake-and-aws-security-hub-telemetry-lakes-versus-findings-aggregation-sap-c03
- SCS-C03: Amazon Security Lake: Subscriber access (Premium), https://app.blowstack.com/lessons/amazon-security-lake-subscriber-access-scs-c03

## Concepts related to Amazon Security Lake

- [Log Normalization](https://blowstack.com/tools/cloud-concepts-hub/log-normalization): Log normalization converts differently structured log records into a consistent schema and representation so they can be searched, compared, and correlated.
- [Anomaly Detection](https://blowstack.com/tools/cloud-concepts-hub/anomaly-detection): Anomaly detection identifies data or events that deviate from expected patterns and warrant investigation.
- [Database Normalization](https://blowstack.com/tools/cloud-concepts-hub/database-normalization): Database normalization organizes relational data into tables according to dependencies to reduce redundancy and prevent inconsistent updates.
- [Event Correlation](https://blowstack.com/tools/cloud-concepts-hub/event-correlation): Event correlation is the process of connecting related events across sources using shared attributes, timing, and rules to identify meaningful activity.
- [Immutable Storage](https://blowstack.com/tools/cloud-concepts-hub/immutable-storage): Immutable storage preserves written data by preventing modification or deletion for a defined retention period or while a protective hold remains in effect.
- [Open Cybersecurity Schema Framework (OCSF)](https://blowstack.com/tools/cloud-concepts-hub/open-cybersecurity-schema-framework-(ocsf)): Open Cybersecurity Schema Framework (OCSF) is an open, vendor-neutral framework for representing cybersecurity events in a common schema.
- [Temporal Correlation](https://blowstack.com/tools/cloud-concepts-hub/temporal-correlation): Temporal correlation is the process of relating events by their timestamps, time windows, and sequence to identify potentially connected activity.
