amazon-connect-cfn icon indicating copy to clipboard operation
amazon-connect-cfn copied to clipboard

Published 20 hours ago • verified publisher icon iann0036

Issue: Reason: 'Cannot find module \'iltorb\''

Open jo9553 opened this issue 4 years ago • 6 comments

The error is generated when deploying the example_stack.yaml to CloudFormation. Thanks.

jo9553 avatar Sep 23 '20 01:09 jo9553

I'm having the same issue.

mariandumitrascu avatar Sep 23 '20 20:09 mariandumitrascu

I solved this error after I installed the npm packages locally and then uploaded to Lambda again. But still have other issues when trying to create resources. "Failed to create resource. waiting for selector div.launch-page-login-link failed", may need to adjust the timeout setting or other crawling problems.

jo9553 avatar Sep 24 '20 02:09 jo9553

Yes. I did "npm i aws-sdk chrome-aws-lambda puppeteer-core request-promise request" in /lambda folder and packed it into a zip and used as the package for the lambda function and it worked. It worked only for "AWS::Connect::Instance" though.
Amazon changed slightly the interface for Connect and thats why I think "AWS::Connect::ContactFlow" is failing.
But that can be fixed.

mariandumitrascu avatar Sep 24 '20 14:09 mariandumitrascu

Hey all,

Thanks for reporting. I don't have a whole bunch of time to work on this right now, but if you manage to figure out the fix, I'll happily merge the PR and re-upload the hosted ZIP.

It's also probably worth looking into the official API for AWS::Connect::ContactFlow now that it exists. Couldn't figure out the syntax for the call though.

iann0036 avatar Sep 26 '20 02:09 iann0036

@mariandumitrascu Were you able to figure out how to prevent AWS::Connect::ContactFlow from failing?

Caoimhin89 avatar Nov 29 '20 00:11 Caoimhin89

@iann0036 forked it. I'm working on a fix now. I'll send over a PR as soon as I get it all worked out. Awesome work, by the way!

Caoimhin89 avatar Nov 29 '20 07:11 Caoimhin89