Which solution will meet these requirements?
Configure the Lambda functions to have an increased timeout value during peak periods. Use RDS Reserved Instances for the database. Use CloudFront and subscribe to AWS Shield Advanced to protect against the SQL injection and web exploit attempts.
Increase the memory of the Lambda functions, Transition to Amazon Redshift for the database. Integrate Amazon Inspector with CloudFront to protect against the SQL injection and web exploit attempts.
Use Lambda functions with provisioned concurrency for compute during peak periods, Transition to Amazon Aurora Serverless for the database. Use CloudFront and subscribe to AWS Shield Advanced to protect against the SQL injection and web exploit attempts.
Use Lambda functions with provisioned concurrency for compute during peak periods. Use RDS Reserved Instances for the database. Integrate AWS WAF with CloudFront to protect against the SQL injection and web exploit attempts.
Explanations:
Increasing the Lambda timeout and using RDS Reserved Instances will not address cold starts, scalability, or SQL injection protection effectively. AWS Shield Advanced does not specifically protect against SQL injection or web exploits.
Transitioning to Amazon Redshift is not appropriate for transactional workloads like those of the web application. Also, Amazon Inspector is not designed for protecting against SQL injection on web applications.
Aurora Serverless is not optimal for workloads with high and unpredictable traffic, as it can take time to scale up or down. AWS Shield Advanced does not specifically protect against SQL injection or web exploits.
Provisioned concurrency for Lambda functions ensures low-latency access during peak periods. RDS Reserved Instances optimize costs for consistent DB usage. AWS WAF provides protection against SQL injection and web exploit attempts.