Reputation: 8663
Let's imagine a system like below:
The problem is that the metrics are stored in a common AWS account (even if they are stored in separate CloudWatch namespaces)! So, a member of Customer X can see the metrics of Customer Y by adding a datasource which accesses the namespace of the Customer Y.
Is there a mechanism to have separate credentials to securely isolate CloudWatch namespaces? Or another solution (other than having a separate AWS account for each customer) to fix this problem?
Upvotes: 0
Views: 328
Reputation: 28646
You can use IAM role with condition keys to limit access to particular CloudWatch namespace. So each Grafana organization will use own limited IAM role.
Upvotes: 1