
The increasing popularity of data lakes isn’t surprising anyone in the analytics space. The appeal of importing data from multiple sources into a single data lake, then providing access to hundreds, or even thousands of users, is undeniable.
The catch? Building enterprise-scale data lakes is a historically cumbersome, complex, and extremely time-consuming process.
AWS developed AWS Lake Formation as an answer to these challenges, giving organizations the tools to quickly build data lakes while simplifying security management. In short, AWS Lake Formation addresses the technical complexity and security challenges of building a petabyte-scale data lake. The technology will be an enormous help to AWS customers burdened by distributed data access and security, even within the AWS ecosystem.
I’m excited to share the news that Starburst Enterprise now supports, in public preview, AWS Lake Formation.
Starburst and AWS Lake Formation
This is just the latest evolution in our longstanding partnership. AWS has been a critical Starburst partner since our early days, and we’ve helped our joint customers uncover transformative insights, reduce costs by 50%, accelerate queries, and much more. Yet this latest development could have an even broader organizational impact.
AWS Lake Formation has emerged as an essential tool for companies looking to shift to a data mesh, the architectural framework that delivers faster, more accurate access to distributed datasets. In addition to its key security benefits, AWS Lake Formation provides self-service data access capabilities that are core to the data mesh approach and robust data lake analytics.
AWS Lake Formation makes it easier for AWS customers to set up a secure data lake. It helps customers import data into Amazon S3, catalog and label data, and provide row and cell-level security and access controls.
AWS Lake Formation provides a single place to manage access controls policies. You can define security policies that restrict access to data at database, table, column, row and cell levels. These policies apply to AWS Identity and Access Management (IAM) users and roles, and to users and groups when federating through an external identity provider.