docwho2 / java-connect-lex-chatgpt Goto Github PK

Deployment failed and returned the following error

ResourceStatus ResourceType LogicalResourceId ResourceStatusReason

CREATE_IN_PROGRESS AWS::DynamoDB::Table SessionTable -
CREATE_IN_PROGRESS AWS::IAM::ManagedPolicy ContactUpdatePolicy -
CREATE_IN_PROGRESS AWS::KMS::Key BucketKey -
CREATE_IN_PROGRESS AWS::SNS::Topic NewCallTopic -
CREATE_IN_PROGRESS AWS::IAM::Role BotRuntimeRole -
CREATE_IN_PROGRESS AWS::DynamoDB::Table CallTable -
CREATE_IN_PROGRESS AWS::IAM::Role BotRuntimeRole Resource creation Initiated
CREATE_FAILED AWS::KMS::Key BucketKey Resource handler returned message:
"Policy contains a statement with
one or more invalid principals.
(Service: Kms, Status Code: 400,
Request ID: 5d2ceba6-72c0-4e0f-9b4d
-b5e41e144c45)" (RequestToken: 840c
1c0c-9a44-59e6-ae92-80effc0cc09e,
HandlerErrorCode: InvalidRequest)
CREATE_IN_PROGRESS AWS::IAM::ManagedPolicy ContactUpdatePolicy Resource creation Initiated
CREATE_IN_PROGRESS AWS::DynamoDB::Table SessionTable Resource creation Initiated
CREATE_IN_PROGRESS AWS::SNS::Topic NewCallTopic Resource creation Initiated
CREATE_FAILED AWS::IAM::Role BotRuntimeRole Resource creation cancelled
CREATE_FAILED AWS::SNS::Topic NewCallTopic Resource creation cancelled
CREATE_FAILED AWS::IAM::ManagedPolicy ContactUpdatePolicy Resource creation cancelled
CREATE_FAILED AWS::DynamoDB::Table CallTable Resource creation cancelled
CREATE_FAILED AWS::DynamoDB::Table SessionTable Resource creation cancelled
ROLLBACK_IN_PROGRESS AWS::CloudFormation::Stack connect-chatgpt The following resource(s) failed to
create: [BotRuntimeRole, BucketKey,
SessionTable, NewCallTopic,
CallTable, ContactUpdatePolicy].
Rollback requested by user.
DELETE_IN_PROGRESS AWS::DynamoDB::Table SessionTable -
DELETE_IN_PROGRESS AWS::IAM::Role BotRuntimeRole -
DELETE_IN_PROGRESS AWS::IAM::ManagedPolicy ContactUpdatePolicy -
DELETE_IN_PROGRESS AWS::SNS::Topic NewCallTopic -
DELETE_IN_PROGRESS AWS::DynamoDB::Table CallTable -
DELETE_COMPLETE AWS::IAM::ManagedPolicy ContactUpdatePolicy -
DELETE_COMPLETE AWS::IAM::Role BotRuntimeRole -
DELETE_COMPLETE AWS::DynamoDB::Table SessionTable -
DELETE_COMPLETE AWS::DynamoDB::Table CallTable -
DELETE_COMPLETE AWS::SNS::Topic NewCallTopic -
DELETE_COMPLETE AWS::KMS::Key BucketKey -
ROLLBACK_COMPLETE AWS::CloudFormation::Stack connect-chatgpt -

Error: Failed to create/update the stack: connect-chatgpt, Waiter StackCreateComplete failed: Waiter encountered a terminal failure state: For expression "Stacks[].StackStatus" we matched expected path: "ROLLBACK_COMPLETE" at least once

==============================
Prior to the deployment, the "sam build" also failed (partially)
"=============================="

Build Failed
Error: JavaMavenWorkflow:MavenBuild - Maven Failed: [INFO] Scanning for projects...
[INFO]
[INFO] ---------< cloud.cleo.awsconnect-chatgpt:generate-poly-prompt >---------
[INFO] Building Polly Prompt Generator 1.0
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for com.amazonaws:aws-lambda-java-events:jar:4.0.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.662 s
[INFO] Finished at: 2023-09-13T17:03:53-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project generate-poly-prompt: Could not resolve dependencies for project cloud.cleo.awsconnect-chatgpt:generate-poly-prompt:jar:1.0: The following artifacts could not be resolved: com.amazonaws:aws-lambda-java-events:jar:4.0.0 (absent): com.amazonaws:aws-lambda-java-events:jar:4.0.0 was not found in https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

========================
When I ran ./init.bash before sam build, it also failed :
"========================"

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.024 s
[INFO] Finished at: 2023-09-13T17:03:11-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.2.1:shade (default) on project aws-lambda-java-serialization: Error creating shaded jar: duplicate entry: META-INF/services/com.amazonaws.lambda.thirdparty.com.fasterxml.jackson.core.JsonFactory -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

When deploying, I am encountering the following error:

Resource handler returned message: "Resource of type 'AWS::Lambda::Version' with identifier 'arn:aws:lambda:us-west-2:543274669242:function:connect-chatgpt-ChatGPT:3' did not stabilize. Status Reason is An error occurred during function initialization." (RequestToken: dc471de3-75b5-4737-efc8-de9c60cbcc2b, HandlerErrorCode: NotStabilized)

I have tried to look for information, but it has not been satisfactory.

Do you have any advice?

Is there any way to either 1. keep continuous dialogue going w/out a lex bot?, or 2. immediately trigger a fallback intent for lex? This is a fantastic project, but responses are extremely slow and break the 'feel' of a real conversation. Thanks for sharing it openly!

Facing an issue for the Lambda ChatGPT role during deployment, is there a workaround for this?

Resource handler returned
                                                                                                message: "'MemorySize' value
                                                                                                failed to satisfy constraint:
                                                                                                Member must have value less
                                                                                                than or equal to 3008
                                                                                                (Service: Lambda, Status
                                                                                                Code: 400, Request ID: e5bf05
                                                                                                4b-d513-410f-9946-
                                                                                                490e2a73d8a9)" (RequestToken:
                                                                                                9ccc96b1-2dbc-1e2e-2a73-
                                                                                                a915b3607337,
                                                                                                HandlerErrorCode:
                                                                                                InvalidRequest)