UPDATE_FAILED AWS::CloudFormation::Stack JetsPreheatJob Embedded stack

[archie_fpl]

Hello, I’m trying to deploy my api to aws but it always return this error.
UPDATE_FAILED AWS::CloudFormation::Stack JetsPreheatJob Embedded stack
The following resource(s) failed to update: [TorchEventsRule].
What is “Torch Event Rule”? I looked in the source code, in the documentation and nowhere did I find what would cause or what this error would be, I cannot give much information about Api because it is a project for a company, but I would be grateful if you could give me some light on what causes this type of error.

Thanks in advance.

[tung]

Its the lambda function that Jets creates to do prewarming. Wondering what the error message in the CloudFormation child stack is. Here are some docs to show you how to find that:

Debugging CloudFormation - Jets Ruby Serverless Framework

Note: Would like to upgrade this so that we can use AWS Lambda provisioned concurrency instead also. It’s a matter of time.

[thampton]

We see deployment errors like this frequently and the CloudFormation event log shows rate limit errors. The error detail doesn’t show up in the Jets output, but if we dig into the CloudFormation event logs it’s almost always a CloudFormation rate limit error.

[tung]

As mentioned in

Generated CoudFormation templates & deploy stagger

Bummer. Yup. AWS has limits like any other cloud provider. As you mentioned, Jets 3.0.17 has rate-limiting improvements. Actually ran into rate-limit issues issue enough with a BoltOps client that has over 200 lambda functions. Fixed it as a part of that work. They haven’t seen or reported any more rate limit issues since then. So believe address most of the rate-limit issues for large apps. RE: It would be a nice option, if all actions (GET, PUT, etc) on a given resource (/foo/bar) could b…

Jets v3.0.17 contains rate-limiting improvements.