Closed Samjin closed 6 years ago
The lex-web-ui uses temporary AWS credentials obtained through cognito and the associated unauthenticated role created for this pool. Without AWS temporary credentials, the lex-web-ui will not be able to communicate with the Lex service.
Is your existing login using AWS Cognito Identity / User pools? If yes, you can configure the stack parameter CognitoIdentityPoolId to use the existing pool. If no, you will need to leave in place the functionality which creates the new Cognito Identity Pool.
The Polly service is used by Lex to generate audio responses. Is your use case text chat only for the bot? If no and you want to support both text and voice then you will need to leave Polly enabled. If you really want to disable calling Polly you would need to remove the policy created with the name PollySynth in cognito.yaml which creates a policy for the action "polly:SynthesizeSpeech". You'd also want to disable the visible mic in the UI as well so that users can't attempted voice interaction. It would be better to understand your use case first before making this change.
Thanks for answering my question for different scenarios.
My user would already login with their credential before seeing the UI. How do I customize the template to remove cognito and polly service?