Integrating with Lambda via MySQL stored procedures is deprecated

[sayler.b]

For this question in Set 1:

A car dealership website hosted in Amazon EC2 stores car listings in an Amazon Aurora database managed by Amazon RDS. Once a vehicle has been sold, its data must be removed from the current listings and forwarded to a distributed processing system.

The answer is “Create a native function or a stored procedure that invokes an AWS Lambda function. Configure the Lambda function to send event notifications to an Amazon SQS queue for the processing system to consume.”

However, the current documentation for integrating MySQL with Lambda says that using stored procedures is deprecated. The original question also doesn’t mention MySQL as the specific database engine being worked with. If using PostgreSQL, the correct integration is to install an extension that exposes functions to invoke Lambdas. Other database engines may work differently as well.

[Irene-TutorialsDojo]

Hi sayler.b,

Thank you for the detailed and well-researched feedback. You’re absolutely right!

We have updated the question and explanation to reflect the current AWS documentation. The correct answer has been revised to “Use an Aurora MySQL native function to invoke an AWS Lambda function whenever a vehicle listing is deleted. Configure the Lambda function to send the data to an Amazon SQS queue for the distributed processing system to consume.” The reference to stored procedures has been removed, as AWS now explicitly deprecates that approach and it is no longer available in Aurora MySQL version 3 (MySQL 8.0-compatible).

We have also updated the explanation to specify Aurora MySQL as the engine and clarified that the native functions

lambda_sync and lambda_async are the recommended integration path.

We appreciate you taking the time to flag this — feedback like yours helps us keep our content accurate and aligned with the latest AWS documentation!

Cheers,

Irene @ Tutorials Dojo