Which solution will meet these requirements MOST cost-effectively?
Enable advanced auditing on the Aurora cluster to log CONNECT events. Export audit logs from Amazon CloudWatch to Amazon S3 by using an AWS Lambda function that is invoked by an Amazon EventBridge (Amazon CloudWatch Events) scheduled event. Build a dashboard by using Amazon QuickSight.
Capture connection attempts to the Aurora cluster with AWS Cloud Trail by using the DescribeEvents API operation. Create a CloudTrail trail to export connection logs to Amazon S3. Build a dashboard by using Amazon QuickSight.
Start a database activity stream for the Aurora cluster. Push the activity records to an Amazon Kinesis data stream. Build a dynamic dashboard by using AWS Lambda.
Publish the DatabaseConnections metric for the Aurora DB instances to Amazon CloudWatch. Build a dashboard by using CloudWatch dashboards.
Explanations:
Enabling advanced auditing for CONNECT events allows for capturing user connection information. Exporting logs to Amazon S3 using an AWS Lambda function triggered by EventBridge ensures long-term storage for 7 years, which meets compliance requirements. QuickSight can be used to create a dashboard.
CloudTrail does not log detailed database connection events like Aurora’s specific connection logs. It focuses more on AWS API activity and would not capture all necessary database connection details.
While activity streams capture database activity, they are more suited for security and compliance auditing and are not ideal for tracking user connections specifically. Also, using Kinesis for dashboard creation introduces unnecessary complexity and cost.
CloudWatch metrics like DatabaseConnections provide data on database load but do not capture detailed user connection information. This solution would not meet the compliance requirement of retaining logs for 7 years.