Im trying to understand the AWS API Gateway http endpoint and http proxy endpoint.
At this point my understanding is that If you have an existing REST service, you can use http proxy for additional services on top of my REST service. But what should be used for regular http endpoints? Is it for regular db or web calls? How does it work?
As documented here, with the HTTP integration you are integrating to a backend API service - you have to perform both Integration Request & Response mapping.
Whereas for HTTP_PROXY pattern, you do not have to perform the mapping. API Gateway passes the request from client to HTTP endpoint directly and similarly response from the integration back to the client.
For your question - if you are looking to input/output the same data that your REST service is built for, then HTTP_PROXY pattern makes sense. That is, you need the API gateway only for its non-functional capabilities such as API Key, Authorization, Throttling, Domain name, etc.
If you intend to use the integration aspects of the gateway - such as manipulate the input to your API and its output, then you can choose HTTP where you have more control over what the API expects and returns. And use all of the capabilities of the API gateway too.
HTTP (Hypertext Transfer Protocol) is a service for sending and displaying files like (text, sound, video, images and other multimedia files) on the Internet.
HTTP Proxy is a high performance content filter. It examines Web traffic to identify suspicious content, which can be a spyware, malformed content, or another type of attack. It can also protect your Web server from attacks from the external network using protocol anomaly detection rules to identify and deny suspicious packets.
