AWS Lake Formation
aws.amazon.com
- Free plan
- Web
- API
What AWS Lake Formation is
AWS Lake Formation helps govern, secure, and share data used for analytics and machine learning. It organizes metadata and data permissions through the AWS Glue Data Catalog, with policies available at database, table, column, row, and cell levels. Tag-based controls use data attributes to apply permissions as data changes. Native integrations include Amazon Athena, SageMaker, Redshift, AWS Glue, and EMR; named third-party integrations include Starburst, Dremio, Privacera, and Collibra. Data can be shared across accounts and Regions, including with selected IAM principals in other accounts. Integration with AWS Data Exchange supports sharing with external businesses without moving or copying the data. CloudTrail audit logs show which users or roles attempted access and when. Creating permissions and using them through integrated services is free, although integrated services may still incur standard charges. Storage API billing is based on scanned bytes, rounded to the next megabyte, with a 10 MB minimum; that API is available only when no other AWS Analytics service processes the data. AWS describes security as shared responsibility: AWS protects cloud infrastructure, while customers manage security in the cloud.
Who it suits
It suits organizations using AWS services that need centralized data permissions, auditing, or cross-account and cross-Region sharing. Teams should account for the charges of integrated services and the Storage API's usage conditions.
Good to know, and what to watch
- Policies can reach down to cell level.
- Tag-based controls adapt permissions to changing data.
- CloudTrail logs record attempted data access.
- AWS Data Exchange supports sharing without moving data.
- Integrated services can incur standard charges.
- Storage API has a 10 MB minimum billing quantity.
- Storage API is limited when other AWS Analytics services process data.
Plans
Every plan and priceGoverned Tables
Storage API
Storage optimizer
Permissions
Getting started
- Open the AWS Lake Formation website
- Use the web console or API
- Choose the Permissions plan, listed as free
- Connect the AWS Glue Data Catalog and selected AWS integrations
- Configure governance policies and sharing controls
- Review access activity through AWS CloudTrail
Limits to check
The Storage API charges by bytes scanned, rounded to the next megabyte, with a 10 MB minimum, and can be used only when no other AWS Analytics service processes the data. Governed Tables charge for tracked files, metadata API calls, and storage-optimizer bytes; Storage optimizer charges by bytes processed.
The Club's review
AWS Lake Formation is a cloud service for governing and sharing data used in analytics and machine learning. It is best for organizations already using AWS analytics services that need a shared permissions layer around their data catalog. Its strongest case is fine-grained control across AWS workflows; it is less compelling if you need a standalone or self-hosted platform.
Overview
Lake Formation centralizes metadata and data permissions through the AWS Glue Data Catalog. That can give teams a common governance layer when multiple analytics services work with the same data. The trade-off is that this is one part of an AWS environment, not a way to avoid its other costs or security responsibilities: AWS protects the cloud infrastructure, while customers remain responsible for security in the cloud.
Key features
- Fine-grained access: Policies can apply at database, table, column, row, and cell level. That precision suits teams that need to restrict access to particular fields or records, not merely whole datasets.
- Tag-based controls: Permissions can use data attributes to scale as data changes. This is useful for evolving catalogs where rules based on attributes can be more manageable than repeatedly assigning access to individual objects.
- Analytics integrations: Native integrations include Amazon Athena, SageMaker, Redshift, AWS Glue, and EMR. Starburst, Dremio, Privacera, and Collibra are named third-party integrations. This makes Lake Formation a practical fit for varied analytics workflows, especially those already built around AWS services.
- Data sharing: Teams can share data across accounts and Regions, including with selected IAM principals in other accounts. AWS Data Exchange integration also supports sharing with external businesses without moving or copying the data, a useful option when collaboration should not require another data copy.
- Audit: AWS CloudTrail logs can show which users or roles attempted access and when. That supports access monitoring, though Lake Formation's security model still leaves customers responsible for security in the cloud.
Pricing
Lake Formation has a free plan for permissions, but that does not make the surrounding analytics workflow free. Creating permissions and using them through integrated services costs nothing; standard usage rates for services such as Amazon S3 or AWS Glue Data Catalog still apply.
- Permissions — free: Best for teams using the integrated permission capabilities. The plan covers permission creation and use, not the standard charges of connected services.
- Storage API — custom pricing: Charges are based on bytes scanned, rounded to the next megabyte, with a 10 MB minimum billing quantity. It can be used only when no other AWS Analytics service processes the data, a significant constraint for workflows that already rely on those services.
- Governed Tables — custom pricing: Charges reflect files tracked, metadata API calls, and bytes processed by the storage optimizer. Teams should account for these separate usage dimensions when evaluating governed tables.
- Storage optimizer — custom pricing: Charges are based on bytes processed, rounded to the next megabyte. It compacts small files into larger ones for Governed Tables, so its cost is tied to the data it processes.
Platforms
Lake Formation is a cloud deployment with web and API access. It supports batch ingestion, a metadata catalog, governance controls, both query interfaces, and open table formats. Those capabilities suit cloud analytics pipelines, rather than teams seeking a self-hosted deployment.
Who it's for
Choose Lake Formation if your organization already uses AWS analytics services and needs centralized permissions, auditing, and cross-account or external data sharing. Its column-, row-, and cell-level controls matter most where different users need different views of shared data. Consider another approach if you need self-hosting, or if the Storage API's restriction conflicts with how your analytics services process data.
Pros and cons
- Pro: Fine-grained permissions across the catalog. Controls extend down to cells, giving teams more precision than database- or table-only rules.
- Pro: Sharing without unnecessary copies. Cross-account and cross-Region sharing, plus AWS Data Exchange integration, support collaboration while keeping data in place.
- Pro: Broad analytics connections. Native AWS services and named third-party integrations make it relevant across more than one analytics tool.
- Con: Free permissions do not mean free operation. Integrated services retain their standard charges, and the Storage API and other usage-based plans have separate billing dimensions.
- Con: Storage API has a narrow use condition. It cannot be used when another AWS Analytics service processes the data, and its billing has a 10 MB minimum.
- Con: Customers retain cloud security duties. AWS secures the infrastructure, but security in the cloud remains the customer's responsibility.
Alternatives
Data Lake Software is a useful place to compare more options by category. Consider Parseable instead if its free OSS plan—with SQL queries, dashboards, threshold alerts, OIDC SSO, unlimited users, and customizable retention and object storage—matches your needs. HPCC Systems is a free, Apache 2.0-licensed, self-hosted option for teams that prefer open-source deployment. Tencent Cloud Application Performance Management offers freemium access and packages with three days of trace storage, a better fit when those terms match the requirement. HPE Ezmeral Data Fabric is worth considering for teams seeking a paid, reseller-priced data fabric with one- to five-year E-LTU offerings. lakeFS offers a freemium route and enterprise deployment either as managed lakeFS Cloud or self-managed on-premises, in your own cloud, or air-gapped. Apache Hadoop HDFS and Apache Ozone are free alternatives for readers evaluating open-source storage projects. Oracle Big Data Service is another paid cloud option, with an hourly OCPU service fee and separately priced compute shapes and Oracle Cloud SQL.
Verdict
Lake Formation is a strong choice for AWS-centered teams that need centralized, granular governance and data sharing across analytics workflows. Its best reason to choose it is the combination of catalog-level permissions and sharing without copying data. Look elsewhere if self-hosting is essential, or if the Storage API's usage restriction and the costs of connected services make the fit poor.
The verdict
Lake Formation brings data catalog, access control, audit, and sharing capabilities together for AWS analytics workflows. Its permission features do not remove the need to account for integrated-service charges or the Storage API's limits.
Questions people ask
Is AWS Lake Formation free?
The Permissions plan is free. Integrated services such as Amazon S3 or the AWS Glue Data Catalog can still apply their standard usage rates.
Which platforms does it support?
AWS Lake Formation is available through web and API interfaces.
Can it share data between AWS accounts?
Yes. It supports cross-account and cross-Region sharing, including selected IAM principals in other accounts.
Which services integrate natively?
Native integrations include Amazon Athena, Amazon SageMaker, Amazon Redshift, AWS Glue, and Amazon EMR. Named partner integrations include Starburst, Dremio, Privacera, and Collibra.
Does it provide audit logs?
Yes. AWS CloudTrail logs which users or roles attempted data access and when.
What the maker publishes
- Audit
- Lake Formation provides audit logs through AWS CloudTrail to monitor data access, including which users or roles attempted access and when. source
- AWS integrations
- Native integrations include Amazon Athena, Amazon SageMaker, Amazon Redshift, AWS Glue, and Amazon EMR. source
- Catalog
- It centralizes metadata and data permissions using the AWS Glue Data Catalog. source
- Data sharing
- It supports cross-account and cross-Region data sharing, including sharing with selected IAM principals in other accounts. source
- External data sharing
- Integration with AWS Data Exchange allows sharing data with external businesses without moving or copying it. source
- Fine-grained access
- It supports access policies at database, table, column, row, and cell levels. source
- Founded
- 2006 source
- Partner integrations
- Named third-party integrations include Starburst, Dremio, Privacera, and Collibra. source
- Pricing limit
- Permissions created or used through integrated services are free, while integrated service usage can incur its standard charges. source
- Purpose
- AWS Lake Formation helps centrally govern, secure, and share data for analytics and machine learning. source
- Security model
- AWS describes Lake Formation security as a shared responsibility: AWS protects cloud infrastructure, while customers are responsible for security in the cloud. source
- Storage API limit
- The Storage API can be used only when no other AWS Analytics service processes the data, and scanned bytes have a 10 MB minimum billing quantity. source
- Tag-based controls
- Lake Formation tag-based access control uses data attributes to scale permissions as data changes. source
Checked against the maker's pages on 29 Sept 2026.