Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy chalice app to HTTP APIs #1321

Open
danil-smirnov opened this issue Dec 10, 2019 · 21 comments
Open

Deploy chalice app to HTTP APIs #1321

danil-smirnov opened this issue Dec 10, 2019 · 21 comments

Comments

@danil-smirnov
Copy link

AWS has recently announced API Gateway HTTP APIs, which are up to 71% cheaper compared to REST APIs.

I suppose all and everyone are now keen to deploy their chalice apps to this exciting new infra!

@benjaminsanborn
Copy link

any perspective on if the chalice project is interested in targeting HTTP Gateway?

@jamesls
Copy link
Member

jamesls commented Feb 24, 2020

Yes! Just need to work out the API we want for being able to configure this. I also haven't had much chance to play around with these new API type so I'm not sure what's involved in supporting this.

@danil-smirnov
Copy link
Author

@jamesls Any estimation on this? I believe this feature should be prioritised as it allows Chalice users to save costs on API Gateway service...

@jamesls
Copy link
Member

jamesls commented Apr 24, 2020

Let me dig into this a little more so I can get a better idea of what's needed to support this.

@JPVan
Copy link

JPVan commented Jul 17, 2020

@jamesls Excited for this. :)

@kapilt
Copy link
Contributor

kapilt commented Aug 12, 2020

isn't it just another configuration on API Gateway v2 which chalice already supports as part of web sockets? wrt to decorator expression, maybe @app.http_route or @app.route2() just spitballing to start a conversation ;-)

@ricky-sb
Copy link

Do we even need a separate decorator? This could be as easy as a boolean in config.json to deploy to HTTP APIs vs. REST APIs.

@subssn21
Copy link
Contributor

They just added support for lambda and iam authorizers for http apis. I don’t think you would want to make it a boolean on the current decorator since they have different feature sets.

@jamesls
Copy link
Member

jamesls commented Sep 11, 2020

Yeah, if we do go down the route of separate APIs I'd imagine they'd be as similar as possible so there's minimal adjustments needed to switch/migrate over. From what I can tell, HTTP APIs are different enough that I'm not sure we'd be able to share APIs.

@jdalzatec
Copy link

Hi guys, anyone knows what is the status of this feature? Thanks in advance.

@bl-ue
Copy link

bl-ue commented Jun 29, 2021

🏓 @jamesls — any ETA? We need this :)

@Glocktober
Copy link

Adding to this request...
I've been working with these for a while with straight lambda functions, but it would be useful to capitalize on the Chalice framework for some projects.

@baotran2207
Copy link

Any update for this feature ? :(

@romcab
Copy link

romcab commented Oct 27, 2021

waiting for this feature as well...

@rajeshkatkarnice
Copy link

any updates?

@softwareguy74
Copy link

Any updates? Can't use it until this is implemented.

@baotran2207
Copy link

+1 this feature

@sladg
Copy link

sladg commented Jan 10, 2023

+1 for this, are there any frameworks for HttpApi available?

@matteocontrini
Copy link

@sladg take a look at AWS Lambda Powertools for Python

@JimLundin
Copy link

+1, any updates at all?

@kapilt
Copy link
Contributor

kapilt commented Aug 21, 2023

#2067

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests