voicefoundry-cloud-public / amazon-connect-chat-translate-demo Goto Github PK

Hi I'm getting a error when trying to login or create new access.
I've already added "@aws-amplify/auth": "^3.4.7"

but still doesn't work.

Any ideas?

Issue:

The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions.
We recommend you use the new runtime (nodejs18.x) while creating or updating functions.

Full Error:

CREATE_FAILED      LambdaFunction                                                                     AWS::Lambda::Function      Thu Jun 08 2023 08:53:20 GMT+0000 (Coordinated Universal Time) Resource handler returned message: "The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs18.x) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: 3f67c4fd-2a0d-4dec-83ce-50108668c80d)" (RequestToken: 559bc6ca-92a7-300f-7825-7195acd152c0, HandlerErrorCode: InvalidRequest)

Hi Team,

Just want to know if my instance type is SAML .is it working with saml instance also?

Hii,
I am trying to deployed this project with SAML based amazon connect instance but we can't use this with SAML based amazon connect instance. It is possible to use this with SAML based connect instance.

Even after adding master.XYZ.amplifyapp.com to the Amazon Connect instance approved origins list, and ensuring the right REACT_APP_CONNECT_INSTANCE_URL Env. Vars were set (without extra spaces) + a rebuild, we still get the following error:

Refused to execute inline script because it violates the following Content Security Policy directive: "default-src self". Either the 'unsafe-inline' keyword, a hash ('sha256-TcxCqm3IAZb7lwb/jIKWl56mO4KCckyb4BUJD45PFNs='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.

master.XYZ.amplifyapp.com/:1 Refused to load the script 'https://master.XYZ.amplifyapp.com/static/js/3.b650f316.chunk.js' because it violates the following Content Security Policy directive: "default-src self". Note that 'script-src-elem' was not explicitly set, so 'default-src' is used as a fallback.

As per our company policy, I can't able to connect github account to AWS sandbox(Console). Could you please help me with any other way to deploy this solution without connecting to github account?

cool concept but i can't get the deployment to work. keeps going into a loop looking or a non-existent directory. :-( I'd love to see your concept work before I write something from scratch.
Attached a copy of my console log.

:-
master.d9yuqyn7m238w.amplifyapp.com-1646831097149.log
)

Hi there,

I'm having these two issues when I deploy

The same with Oregon region

Thank you in advance for your support

Hello following the guide I launched the click to deploy in amplify link and was unable to build or deploy the application. The error returned is below with a screen shoot. Would love to get this working with our connect instance. Please advise and thank you for your efforts.

"3 validation errors detected: Value '' at 'platform' failed to satisfy constraint: Member must satisfy enum value set: [WEB_COMPUTE, WEB_DYNAMIC, WEB]; Value at 'buildSpec' failed to satisfy constraint: Member must have length greater than or equal to 1; Value at 'buildSpec' failed to satisfy constraint: Member must satisfy regular expression pattern: (?s).+"