vpalomog
commented
2 years ago The CloudFormation console shows if all resources were created successfully. All resources are grouped under a Lambda application for easy access. If no other restrictions are on the account (such as SCPs) and everything else looks smooth:
- Double check the configuration provided in Secrets Manager (Twitter Streaming API credentials and Amazon Connect configuration).
- The TWITTER_TOPIC in the secret on Secrets Manager represents the filter for the Twitter stream, make sure you specify something such as: #AmazonConnectTwitterListener and use that same expression on your test tweets.
- The EC2 instance executes a Python3 script (located at /usr/local/twitter-streamer.py) as a service (named twitter-streamer) on boot. Log in to the EC2 and verify if the service is running correctly:
systemctl status twitter-streamerCheck the log of the service:sudo journalctl -u twitter-streamer.service
This could provide details on possible Twitter credentials erroring out (such as when accounts are placed on hold).
- Check the logs for the Stream Processor Lambda Function to confirm there are messages delivered from the stream and attempted to be delivered to the Contact Flow.
Hope this helps.
AWSJedi
molopa
Hi, trying to test this github, have done the deployment in our aws account, but don't see any tasks created under Connect based on keywords under monitoring as well as no cloudwatch logs under connect instance log group....can you advise if there is some to validate if the stack is deployed correctly , or any issues that could be causing no outputs post deployment...thanks