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 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.

As Auth0 says on their website “Identity is the front door of every user interaction”. As you’re building our new serverless applications, that becomes even more important as you have multiple apps that you need to secure. In this blog post I’ll walk you through how that can work in Akka Serverless.

CI/CD is one of those quintessential mindset shifts that helps developers automate away the toil of deploying apps. Especially in the realm of serverless, where the whole idea is to focus on the things that matter and let the undifferentiated heavy lifting be handled by others, automating as much as possible is paramount. It helps developers focus on what matters, code, and it helps business focus on what matters, getting quality software to market faster. So how does that work in Akka Serverless?

As developers, we all want to be more productive. Serverless helps you do just that, by letting you focus on the business logic while shifting operations somewhere else. As more companies discover this emerging technology, we also discover drawbacks like state management. In this session, I focused on what serverless is, how it helps developers, what potential drawbacks exist, and how we can add state management into serverless.