Integrate your REST API with Kinesis Using API Gateway Service Proxy

[@stwatertown]

Thanks!

[@BeABetterDev]

Thank you so much for your generosity!

[@N7SOLDIER]

This was very useful.

[@alexandermiller7330]

Really cool stuff. Didnt realize API GateWay would interface directly into Kinesis. Would've done a lambda middleware had I not known. Thanks!!!

[@houserental5424]

Lambda dispatch from API GW for ETL or service routing is probably cheaper unless you need high frequency data ingest and queuing provided by KDS or KDF.

[@anjaligaikwad692]

Really Helpful Content..Thanks!

[@cristiannechita2032]

Neat stuff as always!

[@vaibhavmalik6832]

Really helpful. Point worth mentioning here is that the API Gateway and Kinesis exist in the same account. Correct if i am wrong but i think 'Integration Type: AWS Service' doesn't support cross account integration.

[@vaibhavsrivastava8988]

1. The example demonstrates writing data to Kinesis Streams using API Gateway. Is it possible to use the same approach with Kinesis Firehose? 2. After deploying the API on API Gateway, can it be used directly from the UI without requiring AWS credentials?

[@Rahulmehta13]

This is really helpful!! Thanks!! However, I have a question:- Can I use Oauth 2 through AWS Cognito for securing the above API endpoint setup ?

[@zpmaloy]

Do you know if it adds additional pricing on top of this? It sounds much cheaper instead of using API -> Lambda -> Kinesis.

[@chrisder1814]

hello Do you use custom GPT?

[@satya4866]

Good

[@houserental5424]

Can API GW ingest HTTP data fast enough to justify even using KDS rather then just using direct service routing built into API GW or Lambda?

[@haithai1010]

Anyone do you got a problem when call it from API got 415 unsupported type?

[@rishiraj2548]

🙏💯💯

[@lukeschoenberger86]

Thanks!