AWS API Gateway Introduction

preview_player
Показать описание
Learn about how AWS API Gateway works, its key features, and why it's such a popular AWS service.

📚 My Courses 📚

🎉SUPPORT BE A BETTER DEV🎉

📚 INCREDIBLE BOOKS TO BUILD YOUR ABILITY TO FOCUS AND ORGANIZE 📚

📚 MY RECOMMENDED READING LIST FOR SOFTWARE DEVELOPERS📚

🎙 MY RECORDING EQUIPMENT 🎙

💻 MY DESKTOP EQUIPMENT 💻

🌎 Find me here:

#aws
#apigateway
Рекомендации по теме
Комментарии
Автор

youtube didn't just place this gem in my recommendations. subscribed

mrkostya
Автор

1st of all thank you for wonderfully organized and immediately useful contents!
2nd - there is a not publicly-advertised (but not secret) capability to increase gateway timeout beyond 30 seconds. This quota increase is ONLY available to Premium (Enterprise) Support customers. Customer does have to agree to lower RPS when API Gateway timeout is increased the formula is pretty simple. So if you want one minute timeout your RPS will be halved. (former Senior TAM here).

igorstavnitser
Автор

Awesome tutorial on API Gateway Fundamental tutorial! Thanks for sharing. 👏👏👏👏

PankeshPatel-vs
Автор

FYI: the underlying protocol for REST is HTTP. So, there is no protocol called "REST".

karimm
Автор

thanks for the informative video. One correction though, REST is not a protocol like HTTP, it is an architectural approach/a set of rules to develop API. In fact HTTP is the underlying protocol for RESTFull API.

tlprasad
Автор

hi! AMazing video!!

where can we find how to set it up ( like a tutorial )

abedmalak_
Автор

There is a fourth entry point, which is the Lambda end point (which can be exposed externally). I'm doing small stuff, but that's what I use. I wonder how that fits in - maybe just for 'small stuff'?

martinmillar
Автор

Hello - thank you for our video!

I have an architecture question. If I have a public API and private API on the same server exposed by an internal ALB - the public API is exposed by a public API Gateway (resides outside the VPC), where as the private api is exposed by a Private API Gateway which is accessible through a VPN. Both of the API Gateways point to the internal ALB. Does this set up make sense to your or is there a better way to have a private API and publci API accessible to end users on the same server?

BallersEdmonton
Автор

Thanks for the video. I've been using REST API gateway for a few years now, but the rest of the details about http and websockets were insightful.

One remark, I think that there might be few more limitations to API Gateway. I think that there is a different limit for data response maybe? (5 mb?)

nulldivision
Автор

Great video.
Question for you: if I have an API Gateway connected to a REST API lambda, and I wanted to use a custom rate limiter lambda to check req count, would it be possible to have the gateway hit the rate limiter first to verify if the user is allowed to send the request, then hit the API? Kind of like an authorizer

tzvimashiach
Автор

I thought this video was about AWS API gateway, not HTTP, REST, or Websockets. If you want to talk about those technologies, you should create a video about them.

kevin
Автор

please stop using such stupid services, just have your own api and do your thing. it's gonna be much faster believe me

yldrmcs