Which final step will meet these requirements in the MOST operationally efficient way?
Create a bash script to compare the configuration to the current DB instance configuration and to report any changes.
Use the CloudFormation drift detection feature to check if the DB instance configurations have changed.
Set up CloudFormation to use drift detection to send notifications if the DB instance configurations have been changed.
Create an AWS Lambda function to compare the configuration to the current DB instance configuration and to report any changes.
Explanations:
A bash script could manually compare configurations, but it is not a fully automated or repeatable solution. Additionally, it would require custom logic and maintenance.
CloudFormation drift detection is designed to check if a resource’s actual configuration differs from the configuration in the CloudFormation template. This will allow the company to verify changes after deployment in an operationally efficient way.
While drift detection can be used, sending notifications through CloudFormation is not an optimal solution because CloudFormation does not natively support sending notifications for drift. Notifications would require additional configuration or services.
A Lambda function could compare configurations, but it introduces extra complexity and maintenance. It would require more resources and effort compared to using built-in CloudFormation drift detection.
I weigh that the answer is:
Use the CloudFormation drift detection feature to check if the DB instance configurations have changed.