How can I fix my QuickSight account having capacity and identity in different regions?

Question & Answer
, , ,
1

I just deleted my QuickSight account which was in us-east-1, and recreated it in us-east-2, and now I get errors when I try to create namespaces in either region. How can I resolve this? I would prefer to have both my capacity and identity in us-east-2.

Here are some CLI calls that reveal the problem:

$ aws quicksight list-namespaces --aws-account-id 012345678910
 --profile thrive --region us-east-2
{
    "Namespaces": [
        {
            "Name": "default",
            "Arn": "arn:aws:quicksight:us-east-2:012345678910:namespace/default",
            "CapacityRegion": "us-east-2",
            "CreationStatus": "CREATED",
            "IdentityStore": "QUICKSIGHT"
        }
    ],
    "Status": 200,
    "RequestId": "5ce099b0-c543-4f50-87a6-cf2a559a70a5"
}

$ aws quicksight create-namespace --aws-account-id 012345678910 --profile thrive  --region us-east-2 --namespace test_namespace --identity-store QUICKSIGHT

An error occurred (AccessDeniedException) when calling the CreateNamespace operation: Operation is being called from endpoint us-east-2, but your identity region is us-east-1. Please use the us-east-1 endpoint.

$ aws quicksight create-namespace --aws-account-id 012345678910 --profile thrive  --region us-east-1 --namespace test_namespace --identity-store QUICKSIGHT

An error occurred (AccessDeniedException) when calling the CreateNamespace operation: CreateNamespace was called using the us-east-1 region. Please call this API in the identity region us-east-2.

As you can see, the last two commands are reporting conflicting information.

2

Hi @Canaan_Epperson and welcome to the QuickSight community!
As this issue may call for more in depth assistance in particular to your account, I would suggest creating a support ticket so that you can get direct assistance from the AWS support team.

3

Hi @Canaan_Epperson - Looking at the error, looks like the aws profile ( you have created) is pointing to a different region. You can create a new profile with correct region ( where you want to create the resource) and then run quicksight api with passing the profile name as argument. This will fix the issue.

Regards - Sanjeeb

5

Do you mean the default region in my aws config file? I tried the command in the cloud terminal in both us-east-1 and us-east-2, both with and without the --region option, but I still got the contradictory errors.
Also the profile’s default region is set to us-east-2, which is where I set up my QuickSight account, and where I want to create the namespace.

I have opened a support ticket with no luck so far. A ticket has been opened with the QuickSight team, and I will update with the result.

6

Thank you Brett, this was the correct answer. A glitch occurred when I deleted my QuickSight account in us-east-1, and the QuickSight team had to manually fix the issue.

1 Like