Embark on a data-driven journey with AWS Lake Formation and Glue Data Catalog! Read what we released in 2023 to help you innovate and simplofy your Data Governance with Lake Formation. This summary recaps a year of groundbreaking enhancements. Fasten your seatbelts for a journey that unveils the future of seamless data management!

Chief data officers, data platform administrators, architects, owners, and consumers are looking to simplify data access permissions and governance. AWS Lake Formation makes it easier to centrally govern, secure, and globally share data for analytics and machine learning use cases. Join this session to learn about new capabilities, customer stories, and how you can get the most out of Lake Formation.

Elevate your data security governance with the powerful integration of AWS Lake Formation and Privacera for Databricks. Streamline policy enforcement and monitoring across AWS services, Databricks, and Amazon S3 from a single, convenient hub. As an AWS Data and Analytics Competency Partner, Privacera extends AWS Lake Formation’s capabilities, allowing you to centrally manage data access policies for consistent control. Read this blog to simplify your data journey, reduce time to insights, and unlock the full potential of your expanding data landscape with the Privacera and AWS Lake Formation.

In today’s data-driven world, ensuring the security and proper management of sensitive information is paramount. Collibra Protect and AWS Lake Formation offer a powerful combination to address the growing challenges of enterprise data access governance. In this post, we’ll show you how to start building data access policies with Collibra Protect and have them enforced by AWS Lake Formation.

Many organizations are using AWS Lake Formation to manage data security and access management for Amazon Athena, Amazon Redshift Spectrum, or Presto with Amazon EMR, but they want to be able to manage other sources with a single central data security platform. In this blog we show how the two new Privacera integrations extend AWS Lake Formation.

A modern data strategy is a comprehensive plan or blueprint to help you manage, access, analyze, and act on data. Many companies are developing roadmaps to help them realize their modern data goals. In this session, learn how deploying a modern data architecture on AWS can help businesses navigate their data challenges, optimize analytics processes, and deliver business insights faster. Take a closer look at AWS Glue and AWS Lake Formation, and see how they help accelerate the process.

One of the largest struggles within product is articulating your organization’s unique abilities to deliver value to its market. But guess what, it’s also one of the most important! So how do you develop a successful path that combines innovation, proven methodology and sure-fire approaches to hone-in on the attributes and differentiators that set you apart from your competitors?

One of the things I love about serverless is that I never have to be bothered with managing servers, it’s just using a service like Lambda, Cloud Run, etc and my code is running. If I want to use a database I can rely on services like DynamoDB or CosmosDB. While I think that is absolutely great, it feels like serverless is only for stateless processes. I think serverless needs a bold and stateful vision so that we can build any type of application (stateful and stateless) without ever managing servers. In this talk, I’ll touch on why statefulness matters and how stateful serverless makes patterns like Event Sourcing and CQRS available to anyone.

In the session I went over why serverless is important to our industry, why server admins (which I then rephrased to SREs) are so important to our serverless success, and why stateless isn’t the answer for everything. Technology wise I’ll be “all over the map” talking about things like Knative and the VMware Event Broker Appliance, AWS Lambda, Akka Serverless

Leon Stigter, senior product manager for serverless at Lightbend, elaborated on the problem, telling SiliconANGLE that developers generally consider serverless to be a “stateless solution,” which means that every time an application needs to do something, it must connect to a database first. For single services that isn’t so difficult, he said, but when it happens at bigger scales, tasks such as connection pooling can be very difficult, causing lots of headaches.