Closed trkelly320 closed 1 year ago
Hi, what does your terminal output when you run aws ec2 describe-availability-zones --output text --query 'AvailabilityZones[0].[RegionName]'
? This will check the region.
Hi, what does your terminal output when you run
aws ec2 describe-availability-zones --output text --query 'AvailabilityZones[0].[RegionName]'
? This will check the region.
$ aws ec2 describe-availability-zones --output text --query 'AvailabilityZones[0].[RegionName]' us-east-1
I was able to get past this error by running the commands below in the git bask terminal after generating new short-term credentials.
I'm also now running this in a Cloud9 environment after some discussion with AWS support. However, now I've gotten a new error when running the "npm run cdk:deploy". I'm getting an error stating that my CDK schema version is a mismatch with the application that the application schema is older than my environment.
This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version. (Cloud assembly schema version mismatch: Maximum schema version supported is 21.0.0, but found 31.0.0)
Hi there, I actually deployed the project earlier today and ran into the same issue. It seems like the CDK version has moved on too far from the project version. I came up with this workaround -
Error message: This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version. (Cloud assembly schema version mismatch: Maximum schema version supported is 21.0.0, but found 31.0.0)
Steps to fix: In the directory "amazon-connect-data-analytics-sample", run the following:
npm uninstall -g aws-cdk
npm install -g aws-cdk@2.51.0
rm -fr node_modules package-lock.json cdk.out
Then, in the directory "amazon-connect-data-analytics-sample/cdk-stacks", run the following:
npm run install:all
npm run cdk:deploy
I am asking around in internal circles about the best practice to maintain CDK projects and will post back about what I find. In the meantime, please try out the workaround above and let me know how it goes.
Thank you for the quick response! I did run the commands as described above but still received the same error.
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ npm uninstall -g aws-cdk
removed 1 package, and audited 1 package in 337ms
found 0 vulnerabilities
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ npm install -g aws-cdk@2.51.0
added 1 package, and audited 2 packages in 1s
found 0 vulnerabilities
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ rm -fr node_modules package-lock.json cdk.out
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ cd cdk-stacks/
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample/cdk-stacks (main) $ npm run install:all
> cdk-stacks@0.1.0 install:all
> npm run install:cdk-stacks && npm run install:lambdas
> cdk-stacks@0.1.0 install:cdk-stacks
> npm install
up to date, audited 643 packages in 3s
32 packages are looking for funding
run `npm fund` for details
34 moderate severity vulnerabilities
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
> cdk-stacks@0.1.0 install:lambdas
> cd lambdas && npm install
up to date, audited 189 packages in 1s
14 packages are looking for funding
run `npm fund` for details
9 vulnerabilities (2 moderate, 7 high)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample/cdk-stacks (main) $ npm run cdk:deploy
> cdk-stacks@0.1.0 cdk:deploy
> npm run cdk:remove:context && cdk deploy --all --no-rollback
> cdk-stacks@0.1.0 cdk:remove:context
> rm -f cdk.context.json
Running in stack mode...
Bundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/StartPartitioningLambda/Code/Stage...
cdk.out/bundling-temp-bcf63c9d072a5e348b5a445b88985d1cab61ccb0582b74572accb2bd86ceca8f/index.js 8.1kb
⚡ Done in 36ms
Bundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/PollPartitioningStatusLambda/Code/Stage...
cdk.out/bundling-temp-f2c987ec4daf3ff1cb057eaea2bb82d4159fc4f0d8faaf74cd7dc6b26dc3aa37/index.js 8.1kb
⚡ Done in 5ms
Bundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/GetPartitioningResultsLambda/Code/Stage...
cdk.out/bundling-temp-b111dcbaddf86506b8a3298f1f29d823196414010bce35c50b09a9ba4bf050ed/index.js 8.1kb
⚡ Done in 5ms
Bundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/PartitioningIteratorLambda/Code/Stage...
cdk.out/bundling-temp-f35fab75aceffa224f5e0ec6bec6f04404c032cc72ff3dc8dd9a7a08fcb501d7/index.js 8.2kb
⚡ Done in 6ms
This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.
(Cloud assembly schema version mismatch: Maximum schema version supported is 21.0.0, but found 31.0.0)
Can you run ‘cdk —version’ and share output?
On Fri, Jun 30, 2023 at 11:59 AM trkelly320 @.***> wrote:
Thank you for the quick response! I did run the commands as described above but still received the same error.
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ npm uninstall -g aws-cdk removed 1 package, and audited 1 package in 337ms found 0 vulnerabilities AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ npm install -g @.*** added 1 package, and audited 2 packages in 1s found 0 vulnerabilities AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ rm -fr node_modules package-lock.json cdk.out AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample (main) $ cd cdk-stacks/AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample/cdk-stacks (main) $ npm run install:all
@.*** install:all> npm run install:cdk-stacks && npm run install:lambdas
@.*** install:cdk-stacks> npm install
up to date, audited 643 packages in 3s 32 packages are looking for funding run
npm fund
for details 34 moderate severity vulnerabilities To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Runnpm audit
for details.@.*** install:lambdas> cd lambdas && npm install
up to date, audited 189 packages in 1s 14 packages are looking for funding run
npm fund
for details 9 vulnerabilities (2 moderate, 7 high) To address all issues, run: npm audit fix Runnpm audit
for details.AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample/cdk-stacks (main) $ npm run cdk:deploy@.*** cdk:deploy> npm run cdk:remove:context && cdk deploy --all --no-rollback
@.*** cdk:remove:context> rm -f cdk.context.json Running in stack mode...Bundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/StartPartitioningLambda/Code/Stage...
cdk.out/bundling-temp-bcf63c9d072a5e348b5a445b88985d1cab61ccb0582b74572accb2bd86ceca8f/index.js 8.1kb ⚡ Done in 36msBundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/PollPartitioningStatusLambda/Code/Stage...
cdk.out/bundling-temp-f2c987ec4daf3ff1cb057eaea2bb82d4159fc4f0d8faaf74cd7dc6b26dc3aa37/index.js 8.1kb ⚡ Done in 5msBundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/GetPartitioningResultsLambda/Code/Stage...
cdk.out/bundling-temp-b111dcbaddf86506b8a3298f1f29d823196414010bce35c50b09a9ba4bf050ed/index.js 8.1kb ⚡ Done in 5msBundling asset AmazonConnectDataAnalyticsSampleBackend/PartitioningStack/PartitioningIteratorLambda/Code/Stage...
cdk.out/bundling-temp-f35fab75aceffa224f5e0ec6bec6f04404c032cc72ff3dc8dd9a7a08fcb501d7/index.js 8.2kb ⚡ Done in 6ms This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.(Cloud assembly schema version mismatch: Maximum schema version supported is 21.0.0, but found 31.0.0)
— Reply to this email directly, view it on GitHub https://github.com/aws-samples/amazon-connect-data-analytics-sample/issues/5#issuecomment-1615079823, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGBYT543OPAF4HQ36OCWHJDXN4OYPANCNFSM6AAAAAAZWD4T7Q . You are receiving this because you commented.Message ID: <aws-samples/amazon-connect-data-analytics-sample/issues/5/1615079823@ github.com>
-- Angela Yu
Yes absolutely. it shows 2.51.0 (build a87259f)
AWSReservedSSO_AWSAdministratorAccess_761a2c42a00f49e2:~/environment/amazon-connect-data-analytics-sample/cdk-stacks (main) $ cdk --version 2.51.0 (build a87259f)
Can you try changing the package deps like in the screenshot? Basically adding the two carets. Then try the 5 commands again.
I received quite a few warning messages about various API deprecation but it did deploy that time. I'm not sure if that's all the hurdles but it's the furthest I've made it so thank you! I'm currently watching CloudFormation for everything to finish. Have a great weekend!
Great news! Feel free to re-open if you run into any other issues.
When attempting to run 'npm run configure' I am receiving an error 'ERROR: putParameterSSMBatch: Region is missing'. AWS commands seem to be working independently of the package. I have attempted to set a region manually but nothing seems to be working. Could use assistance on how to set region. I am using Git Bash terminal on Windows 11. I am following the blog post at: https://aws.amazon.com/blogs/contact-center/managing-agent-quality-using-amazon-connect-contact-lens-and-evaluation-forms/ and this is step 4 under the Deploy Data Pipeline section.