search

aws-samples / amazon-q-slack-gateway

MIT No Attribution
79 stars 28 forks source link

[Help required] Slack setup with Okta and Amazon Q #49

Closed fabseven closed 1 month ago

fabseven commented 2 months ago

Describe the bug I have been trying to set up the Amazon Q slack gateway in our company slack workspace with Okta. I run into issues with it though when I click on the sign in button from slack -> get redirected to log in to okta -> get redirected to AWS link where the only message I get is "Internal server error". I also tried to take a look at the logs that it spits out but it doesn't really say much.

I am not sure if it's linked but we have our IAM identity center in eu-west-1 while our Amazon Q business app is located in us-east-1. Does the IAM identity center have to be in the same region for it to work properly?

To Reproduce Steps to reproduce the behavior: Step 1: Type "Hello" to the slackbot Step 2: Click on "Sign in to Amazon Q" Step 3: Redirect to Okta login page to sign in Step 4: Redirect to AWS page with the error: "Internal server error"

Screenshots image image

leenmin-aws commented 2 months ago

Yes, unfortunately cross region IdC instance is not supported at this time.

leenmin-aws commented 2 months ago

In fact, I believe your IAM identity center instance needs to be in the same region as the Q business app in general https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/idc-notes.html

fabseven commented 2 months ago

I managed to get idC in the same region and ran the scripts but it's still showing the same error but with different logs now.

image image

I am not really sure in what place it fails now

fabseven commented 1 month ago

Turns out it was a major identity center issue that I managed to fix