AWS re:Invent 2023 - I didn’t know Amazon API Gateway did that (SVS323)

This session provides an introduction to Amazon API Gateway and the problems it solves. Learn about the moving parts of API Gateway and how it works, including common and not-so-common use cases. Discover why you should use API Gateway and what it can do.

Subscribe:

ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.

AWS is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.

#AWSreInvent #AWSreInvent2023

[cloudstudiope]

I had the pleasure of meeting Eric at the Serverless event in Nashville in 2023, and the energy that this guy has is incredible! Great talk, Eric; you enjoy what you do; it motivates people to grow.

[rf-]

Oh, man. I wish I had met Eric when I was at AWS and doing re:invent. Passing this around to all the people at current work learning serverless and API gateway.

[Rickety]

OH MAN!!! I WAS AT RE:INVENT AND DIDN'T KNOW YOU WERE SPEAKING!! I saw your previous lecture and it was probably the best I've ever seen. Happy to catch up here online.

[karolrvn]

Quote of the year :D «If that makes you uncomfortable... I'm also comfortable with that!»

[maadzqeqER]

Great job, always appreciate your talks Eric. Never a sales presentation, geared for developers. Thanks!!!

[jairjosafath]

VTL with AGW is pretty awesome, you can even do fine-grained access control

[krishnakumarg]

The most Fun and Intelligent speaker i have ever watched for AWS sessions

[erikkremzner]

The degree of certainly on the bucket token algorithm has really thrown my understanding out the window.

What is the behavior of an API configured with a burst of 1000 and a rate of 1. My understanding of the algorithm was that if you sent 1000 requests in a single second they would be filled, but for the next 1000 seconds it would be limited to 1rps.

But it seems that Eric mentions burst should always be lower then rate and the intended usage is to control concurrent invocations. Is this true, am I misunderstanding the algorithm?

[bubblegammu]

I can't believe I knew all of it 😮😮

[olivereisenbarth]

I just heard the Audio and didn't get the One-Finger thing at all. Now I see...

[jhonsen]

When ever i see API Gateway I get confsued with Application Load Balancer.