AWS Chalice

It seems dead? <a href="https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;chalice&#x2F;issues&#x2F;2067">https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;chalice&#x2F;issues&#x2F;2067</a>

My last company were huge users of this. It&#x27;s quite limited in terms of the resources it can deploy. To add additional resources that it doesn&#x27;t work with, you need to write some Terraform.<p>I summarised the pattern we were using here <a href="https:&#x2F;&#x2F;github.com&#x2F;elgrove&#x2F;terroir">https:&#x2F;&#x2F;github.com&#x2F;elgrove&#x2F;terroir</a><p>I&#x27;m not surprised the project is dead. AWS want everyone using the CDK for Python or CloudFormation

Discussed here a number of times since it was announced in 2016, including the launch post which has the most discussion<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12074388">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12074388</a>

as a previous contributor and user, I would not recommend.<p>as a project in the GitHub aws organization, it can not accept non amazon external maintainers.<p>as a project, it has a single maintainer, doing on average, an hr every few months.<p>as a result of both of those , its not able to keep up, or reach critical mass on community.<p>it has fallen fairly far behind current lambda feature set. for a simple throw away, its okay, but if you want to grow something or take advantage of new features in the underlying service capabilities or integrations, this is a dead end.<p>I filed this ticket a few years ago <a href="https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;chalice&#x2F;issues&#x2F;2067">https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;chalice&#x2F;issues&#x2F;2067</a>

Anyone here actually developing Python apps on AWS Lambda? If so do you use Serverless Framework or something else? I am part of a research project that is developing techniques for identifying security vulnerabilities in serverless apps so would be interested to understand what people are actually using for deployment and why.

I&#x27;ve built a couple of systems for customers using this, and the development comfort and Flask-like-ness is quite nice.<p>But it&#x27;s really just completely dead by now, which is a bummer as this leaves a large complexity gap between this and jumping ahead to just doing full Lambda+CDK&#x2F;Serverless&#x2F;Terraform setups.

How does that work? That code works partly at deploy time, to register the serverless app with SQS&#x2F;..., and then it runs partly in the serverless invocation?

Everyone in Quebec goes CÂLISSE DE TABARNAK

Spin something up in an hour; spend a week fixing it when the magic inevitably breaks.<p>Maybe I am just incredibly jaded but I can&#x27;t stand all these shortcut frameworks. It just ends up locking you into an ecosystem, especially AWS, and decouples you from building technical understanding of the system where if you go down the path long enough, you have no abort button besides an entire re-build because your code is enmeshed with the framework.<p>Do it right the first time: build it simple &amp; iterate as you go. You don&#x27;t need to be thinking about scaling to 1M concurrent users when you have 0 users.

Hilariously, &quot;chalice&quot; is a strong swear word in Quebec French, so there the name of this product is roughly equivalent to &quot;AWS Fuck&quot;.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Quebec_French_profanity" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Quebec_French_profanity</a>