Unable to create QuickSight subscription – PreconditionNotMetException in multiple regions

The PreconditionNotMetException you're encountering indicates that one or more preconditions required for creating a QuickSight subscription are not being met at the account level. This is a known exception that can occur during the account subscription creation process.

Based on the error pattern you're describing—occurring consistently across multiple regions and methods (web console, CLI)—this does point to an account-level issue rather than a regional or configuration problem.

Here are some additional things to verify:

IAM Permissions: Even though you're using the root user, ensure your IAM policy (if any is attached) includes both the Subscribe and CreateAccountSubscription actions set to Allow. If either action is set to Deny, it will prevail and cause the operation to fail.

Account Prerequisites: Make sure you can connect to your existing AWS account and that the account is in good standing. There may be underlying account status issues that aren't immediately visible but prevent QuickSight provisioning.

Service Availability: While rare, there could be service-specific prerequisites or account validations that need to occur before QuickSight can be provisioned in your account.

Since you've already opened AWS Support cases, that's the correct path forward. Given the account-level nature of this issue and the fact that it's persisting across regions, this likely requires AWS Support intervention to investigate the backend account provisioning status. You might want to follow up on your existing cases or try opening a new case specifically categorizing it as an "Account and Billing" issue to potentially get faster routing to the appropriate team.

Unfortunately, this type of account-level provisioning issue typically cannot be resolved without AWS Support's direct involvement in your account's backend configuration.
Sources
PreconditionNotMetException - botocore 1.42.50 documentation
create_account_subscription - Boto3 1.42.50 documentation

This does sound like a challenge.

While I'm unable to discuss case or account info over re:Post, I was able to pass on what you've shared to our internal teams.

Keep a lookout for their response, and seek updates over your case thread.

- Randi S.