Open tommedema opened 5 years ago
I am confused with this too. But I guess it could be due to the fact that , DATA API is available for only Aurora serverless DB , And you can't give an Amazon Aurora Serverless DB cluster a public IP address. You can access an Aurora Serverless DB cluster only from within a virtual private cloud (VPC), based on the Amazon VPC service. And if we still need to access the DATA API, from outside the VPC, we may need to create a lambda, expose via API gateway and pass on SQL statement for lambda to execute the DATA API. Just my thoughts.. .
There's a mysterious lambda function in the cloudformation file that I cannot wrap my mind around. It's been explained as:
Why would the user need to create a separate lambda function to accept HTTP requests? Isn't the whole point of the Data API that Aurora can start accepting HTTP requests? So why would developers themselves have to create another HTTP endpoint?
Is there a way for us to inspect the lambda code at bucket cloudformation-templates-useast-1 and key rds-aurora-serverless/rds-data-api-lambda-function.zip?