Chalice: Deploy chalice app to HTTP APIs

[danil-smirnov]

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]

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

[jamesls]

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]

@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]

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

[JPVan]

@jamesls Excited for this. :)

[kapilt]

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]

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]

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]

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.