We are getting an "Access Denied Exception" saying our operation is being called on us-east-2 but our identity region is us-east-1, but as far as we can tell, our QuickSight setup is for us-east-2

Question & Answer
1

Hi,
We are trying create namespace from East-2 region but getting below exception.

We are getting an “Access Denied Exception” saying our operation is being called on us-east-2 but our identity region is us-east-1, but as far as we can tell, our QuickSight setup is for us-east-2.

We have our RDS and Quicksight setup is done in East-2.

Please suggest how to proceed. Thanks!

2

We’ve had a lot of users contact us and say they can’t connect and it is because the email they get tells them -1 when it should be -2. We haven’t found an answer to it to be honest but we now send a follow up email asking them to check that the URL has -2.
We think it is because the account is in Ireland but the data in London. It would be interesting to find a proper solution.

3

Hi,

When initially setting up the account, the identity region is selected. Further when creating namespaces, they have to be created in the selected identity region.

To get the identity region : Workshop Studio

Since the users are created and maintained in the identity region , you can do a list users and the response has Arn of the user (identity region : eu-central-1 ) .

"Arn": "arn:aws:quicksight:eu-central-1:xxxx:user/default/Admin/xxxx-Isengard"

A list namespace call will also provide you the identity region (capacityregion)

{
            "Name": "default",
            "Arn": "arn:aws:quicksight:eu-central-1:xxxxx:namespace/default",
            "CapacityRegion": "eu-central-1",
            "CreationStatus": "CREATED",
            "IdentityStore": "QUICKSIGHT"
        }

Regards,
Koushik

4

Hi, @Prasannat. Did @Koushik_Muthanna’s solution work for you? I am marking their reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community Q&A Forum!

5

We are able create the namespace with east-1 region not with east-2. So we followed the same.