- Newest
- Most votes
- Most comments
The issue you're experiencing with the AWS IoT TwinMaker scene not loading in Amazon Managed Grafana is likely not related to the plugin version you're using. Your Grafana version (10.4) and the TwinMaker plugin version (1.10.1) should be compatible.
The problem appears to be with your CORS (Cross-Origin Resource Sharing) configuration for the Amazon S3 bucket. While you've made an effort to configure CORS, there's a small but important detail missing in your configuration.
In the "AllowedOrigins" section of your CORS configuration, you need to include an asterisk (*) at the beginning, followed by your Grafana workspace domain. The correct format should look like this:
"AllowedOrigins": [ "*https://g-e562bf4c53.grafana-workspace.us-east-1.amazonaws.com" ]
This asterisk is crucial as it allows subdomains and ensures proper access.
To fix this issue:
- Go back to your Amazon S3 console and select the bucket you're using for your AWS IoT TwinMaker workspace.
- Navigate to the "Permissions" tab.
- In the "Cross-origin resource sharing (CORS)" section, click "Edit".
- Modify your CORS configuration to include the asterisk before your Grafana workspace domain in the "AllowedOrigins" section.
- Save the changes.
After making this adjustment, your AWS IoT TwinMaker scene should load properly in Amazon Managed Grafana. If you continue to experience issues, double-check your data source configuration and ensure that your IAM roles and permissions are set up correctly for accessing AWS IoT TwinMaker resources from Grafana.
Remember, AWS IoT TwinMaker scenes are designed to update dynamically based on knowledge graph queries. In a read-only Scene Viewer like in Grafana, you should see updates to your scenes approximately every 30 seconds.
Sources
AWS IoT Twinmaker Scene not loading in Amazon Managed Grafana | AWS re:Post
CORS configuration for Grafana scene viewer - AWS IoT TwinMaker
Dynamic scenes - AWS IoT TwinMaker
Relevant content
- asked 10 months ago
