1 Answer
- Newest
- Most votes
- Most comments
1
It is overall correct but I would check on the following items.
- IAM Role Trust Relationships: Please ensure that the trust relationships for the IAM roles in both accounts are correctly configured. The role in Account B should trust Account A, and the role in Account A should trust the grafana.amazonaws.com service.
- IAM Role Permissions: The permissions attached to the roles in both accounts should be correctly configured. The role in Account B should have the necessary permissions to access the Timestream database, and the role in Account A should have the sts:AssumeRole permission for the role in Account B.
- Role Assumption: Ensure that the Grafana workspace in Account A is correctly assuming the role in Account B. This is typically done through the Grafana AWS CloudWatch data source configuration.
- Network Connectivity: Ensure that there are no network connectivity issues or restrictions that might be preventing the Grafana workspace in Account A from connecting to the Timestream database in Account B.
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hi Giovanni, thank you very much for your prompted response. I was able to fix this by removing the Managed Grafana workspace from the VPC. Thank you for the response