Closed haljeshi closed 2 years ago
Hi @haljeshi, thanks for your question. A couple of months ago we found issues when using older node versions (older than 15). If you check the actual CDK deployment pipeline you will see that we use 'n 16.15.1'. That should solve the first part of the issue. I have redeployed the platform and I am not encountering your issue, but one possible explanation is the site package JSII, which in general we don't have to worry about because AWS CDK manages this dependency. However, sometimes we have seen issues with conflicting new versions of this package, so a possible quick workaround would be to add it in the deploy/requirements.txt
as “jsii==1.67.0". Give it a try and let us know if it works :)
Hi @dlpzx Thank you for your suggestion. However, it did not solved my problem.
However, the problem has been solved by something much simpler that I didn't notice before. And I'm reporting it here so that if someone else has done this same silly mistake as me, they can check their code.
In the cdk.json
file, the first line is "app": "python ./deploy/app.py"
by default
This will invoke python2 if you didn't change the alias before. I modified this line to "app": "python3.8 ./deploy/app.py"
and it worked.
Sorry to bother you and hope that this will help other people successfully install the system.
Hello,
I have tried following the instruction presented here to deploy on AWS several times. In every attempt, I reach to Step 5 (running cdk synth) and it's not working for me.
I have tried using Amazon Linux 2 and Ubuntu. I have tried with different versions of node, cdk and python. And Every time, it fails to run cdk synth.
During my several attempts, I noticed is that the node version is the thing that is making a difference. So, here is what I get depending on the node version I try (all output is the result of running 'cdk synth --verbose'):
On node v12.22.12
On node v13.14.0
On node v14.20.0 (it takes a long time)
On node v16.17.0