Quicksight Disaster Recovery Setup

Amazon QuickSight's identity management is tied to a specific identity region (in your case, us-east-1), which creates challenges for disaster recovery setups across regions.

The error you're encountering occurs because QuickSight user and group management operations must be performed in your identity region (us-east-1). When us-east-1 is down, you won't be able to retrieve user and group data from that region, which would impact your ability to access dashboards and data sources in us-east-2.

For setting up a disaster recovery solution for QuickSight, consider these approaches:

1. Use the AssetBundle Export and Import APIs to maintain copies of your QuickSight assets (dashboards, analyses, datasets) across regions. You can export assets from us-east-1 and import them into us-east-2.

2. After importing assets to the target region (us-east-2), you'll need to share these resources with the appropriate users. Navigate to Manage QuickSight → Manage Assets, find your imported resources (they'll be prefixed with "Imported-"), and share them with the respective users.

3. For user management across regions, consider implementing federated access using AWS IAM Identity Center or an external identity provider (IdP) like Okta or Ping. This approach can provide more flexibility for cross-region access.

4. If using IAM Identity Center, ensure it's properly set up and configured before subscribing to QuickSight in your DR region. Create appropriate permission sets in IAM Identity Center and provision them to the target AWS account where QuickSight is subscribed.

5. For private data sources, you'll need to set up VPC connections in the target region that mirror your source region configuration.

Remember that QuickSight's identity region limitation means you'll need to plan carefully for how users will authenticate during a disaster scenario when the primary identity region is unavailable.
Sources
Amazon QuickSight asset deployments using AssetBundle Export and Import APIs - Private Datasource Guidelines | AWS re:Post
Configuring federated user access to QuickSight through IAM Identity Center - AWS Prescriptive Guidance
Configuring federated user access to QuickSight through IAM and an external IdP - AWS Prescriptive Guidance