Which solution will meet these requirements with the LEAST development effort?
Configure a data lake in AWS Lake Formation. Use AWS Glue crawlers to ingest the security data into the data lake.
Configure an AWS Lambda function to collect the security data in .csv format. Upload the data to an Amazon S3 bucket.
Configure a data lake in Amazon Security Lake to collect the security data. Upload the data to an Amazon S3 bucket.
Configure an AWS Database Migration Service (AWS DMS) replication instance to load the security data into an Amazon RDS cluster.
Explanations:
While AWS Lake Formation is a good tool for building data lakes, configuring it and using AWS Glue crawlers requires more development effort to set up compared to other options. It involves creating a data lake and defining data ingestion processes.
Using an AWS Lambda function to collect and upload security data to an S3 bucket is feasible but requires development effort to build and maintain the Lambda function. Additionally, this method lacks centralized management and may not scale well compared to dedicated security solutions.
Amazon Security Lake is specifically designed for centralized collection of security data with minimal setup and development effort. It automatically aggregates security data from various sources, making it a straightforward solution for improving workload protection across the company.
Using AWS Database Migration Service (AWS DMS) to load security data into an Amazon RDS cluster is not ideal for centralized security data collection. This approach requires configuration of a replication instance and ongoing management, which introduces unnecessary complexity for the stated purpose.