如何通过AWS CLI轮询QuickSight数据源更新请求状态？

I’ve been in your exact situation before—running an update command, getting a 202 response, and then being left in the dark about whether it actually worked, only to find later the change never applied. Let’s break down how to track your update progress and get to the bottom of the failure:

1. Track the Update Status #

To check the real-time state of your data source update, use the describe-data-source CLI command with the DataSourceId from your initial response:

aws quicksight describe-data-source \
  --aws-account-id <my-aws-account-nr> \
  --data-source-id 099676d0-99e3-44d7-b581-d6e532e72961 \
  --output json

Pay attention to the Status field in the response:

• UPDATE_IN_PROGRESS: The update is still running (give it a few more minutes if needed)
• ACTIVE: The update completed successfully
• FAILED: The update didn’t go through (this is what you’re likely encountering)

If the status is FAILED, the response will include an ErrorInfo object with a specific error message and type—this is your most valuable clue for debugging.

2. Debug the Failure #

Once you confirm the update failed, here’s how to diagnose the issue:

• Dig into ErrorInfo: The ErrorMessage will spell out specific problems, like invalid database credentials, missing IAM permissions, or VPC connectivity blocks preventing QuickSight from reaching your data source.
• Validate your JSON config: Double-check the update-stag-data-source-request.json file. Ensure all parameters match your data source type—for example, if updating an RDS source, confirm the DB instance ARN, connection string, and credentials are all correct.
• Use the QuickSight Console: Head to the QuickSight web console, locate your data source, and check its History tab or error logs. The console often shows more context than the CLI, like detailed connection test results or permission breakdowns.
• Verify IAM Permissions: Make sure the IAM user/role running the update-data-source command has the quicksight:UpdateDataSource permission. Also, confirm the QuickSight service role (if you’re using one) has the necessary access to your underlying data source—like S3 read permissions or RDS connection rights.

For example, if your describe-data-source response includes:

"ErrorInfo": {
  "ErrorMessage": "Unable to connect to the database: Invalid credentials provided",
  "ErrorType": "ACCESS_DENIED"
}

You’ll know to recheck the credentials in your update request or confirm QuickSight is authorized to use those credentials.

内容的提问来源于stack exchange，提问作者korulis