I have just read following article
And I really don't get why the AWS API Gateway doesn't support VPCs out of the box and we have to proxy all the requests through a lambda function?
Does anyone have an idea about why is that?
I have just read following article
And I really don't get why the AWS API Gateway doesn't support VPCs out of the box and we have to proxy all the requests through a lambda function?
Does anyone have an idea about why is that?
Copyright © 2021 Jogjafile Inc.
Though I never found any AWS official statement about this matter, I strongly believe that accessing private resources (VPCs, subnets) from an always public entity (as is API Gateway) would require much more effort (testing) regarding the product security.
I don't believe their plan is to keep it like this forever, though. From this same article you linked, they state (my emphasis):
My guess is that "tomorrow" API Gateway access to private resources will exist and, yes, our lives will be easier (and cheaper, btw).
In the end of the day, and given that my assumption is right, I believe it was the right decision: launch a useful (but more limited) version first and learn with it.
EDIT: Since 2017 November, API Gateway integrates with private VPCs. https://aws.amazon.com/pt/about-aws/whats-new/2017/11/amazon-api-gateway-supports-endpoint-integrations-with-private-vpcs/