Building a Unified Observability Dashboard with Amazon Managed Grafana

This article introduces a method for integrating CloudWatch / Prometheus / OpenSearch data sources and building a multi-source observability dashboard.

About 7 min readLast updated: 2026-10-31

Features of Managed Grafana

Managed Grafana provides open source (OSS) Grafana as a managed service. Provisioning, scaling, patching, and backups of Grafana servers are managed automatically, so you can concentrate on building dashboards. You can integrate 30 or more data sources, such as CloudWatch metrics and logs, Prometheus metrics, OpenSearch logs, X-Ray traces, and Timestream time-series data, and visualize them across sources on a single dashboard. Compared with CloudWatch's native dashboards, it is superior in integrating multiple data sources, advanced visualization, and dynamic filtering with template variables.

Data Source Integration and Dashboard Design

Setting up AWS data sources is completed simply by associating an IAM role with the workspace. The CloudWatch data source directly queries metrics from EC2, RDS, Lambda, and other services, and the Prometheus data source retrieves metrics from Amazon Managed Prometheus or your own Prometheus servers. A dashboard is composed by arranging panels (graphs, tables, gauges, and heatmaps). A design that makes Region, environment, and service name switchable from drop-downs with template variables and monitors multiple environments with one dashboard is efficient. Grafana dashboards can be exported/imported as JSON and version-controlled with Git. If you also collect metrics in Datadog separately from the CloudWatch data source, you create an IAM role for Datadog in your AWS account and ingest logs/events/most metrics from 90 or more AWS services through the AWS integration. Metrics and logs from Google Cloud and Azure can also be collected in the same Datadog through their respective integrations. As of October 2026, the default collection is API polling every 10 minutes on average, and CloudWatch metrics with 5-minute granularity may arrive 15 to 20 minutes late. The setup flow is described in the official Datadog documentation for the AWS integration.

Alerts and Access Control

With Grafana's alerting feature, you can set alerts based on metric thresholds being exceeded or on log pattern matches. You can define alerts with conditions that span multiple data sources (for example, CPU utilization of more than 80% and 10 or more error logs per minute). You can also monitor compound conditions that are hard to build with CloudWatch alarms alone. Notification destinations support many channels, such as SNS, Slack, PagerDuty, and OpsGenie. Access control is integrated with IAM Identity Center (formerly AWS SSO), and view/edit permissions for dashboards are controlled based on the organization's users and groups.

Managed Grafana Pricing

Managed Grafana pricing consists of licenses for editor users (dashboard creators) and viewer users (people who view dashboards). Editors cost $9.00 per month per active user per workspace, and viewers likewise cost $5.00 per month (as of October 2026). Each workspace requires at least one editor license, which is billed even if no users log in. Compared with self-hosted Grafana (EC2 + EBS), the managed service is cheaper when the number of users is small, and the operational burden is also lighter. In environments with more than 20 users, costs are compared with self-hosting, and the decision is made based on the total cost of ownership, including operational costs.

Integrating Metrics / Logs / Traces

In observability, the whole picture becomes visible only when the three perspectives of metrics / logs / traces are combined. The value of Managed Grafana lies in letting you place these side by side and correlate them on one dashboard instead of following them in separate tools. You can carry out the investigation flow of detecting an anomaly with metrics, checking the details in logs from the same time period, and tracing where a request was delayed, without interruption. Being able to see correlations across multiple data sources helps shorten the time it takes to identify the cause of a failure.

Operating Dashboards and Turning Them into Templates

A dashboard is not finished once it is created; it is something you operate and grow. Because Grafana dashboards can be exported as JSON, it is safe to version-control them with Git so that you can track the change history. With template variables, you can create one general-purpose dashboard in which environments and services can be switched from drop-downs, and monitor multiple targets on the same screen. If you reuse frequently used panels as shared components, you can also launch monitoring for new services quickly. The idea of managing dashboards as code improves their consistency and maintainability.

Designing Alerts and Notifications

The strength of Managed Grafana's alerts is that you can build conditions spanning multiple data sources. Because alerts can fire on compound conditions that combine metrics and logs rather than a single indicator alone, you can design practical alerts with fewer false positives. Because notification destinations support a variety of channels, including SNS, you can incorporate them into existing communication routes. Notification destinations are separated by severity so that only alerts that require action reach the person in charge. If you attach a link to the dashboard that is the basis of the alert, the recipient can check the situation immediately, and the response becomes faster.

Comparing with Self-Hosting and Choosing

Grafana can be operated either as a managed service or self-hosted. The advantages of the managed version are that you can delegate server setup/updates/backups and that authentication is easy to integrate with the organization's identity platform. It is suited to cases where there are relatively few users and you want to save operational effort. On the other hand, in cases such as when you want to add plugins freely, apply your own extensions, or reduce license costs because many people use it, self-hosting becomes an option. Comparing by total cost, including the staff time needed for operations, and choosing the form that fits your organization's structure and requirements is reasonable in the long run.

Summary

Managed Grafana is a service for building advanced observability dashboards that integrate multiple AWS data sources. It requires no operation of Grafana servers, and its features are access control through IAM Identity Center and alert settings with compound conditions. It is an effective option when you have visualization requirements that CloudWatch dashboards cannot meet.

References (Official AWS Resources)

The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.

If this page and the official documentation disagree, treat the official documentation as authoritative.

How AWS Keeps Time Internally - Amazon Time Sync Service and Leap Second Smearing DesignLearn how Amazon Time Sync Service works, how GPS and atomic clocks provide high-precision time sources, the design decision to absorb leap seconds through smearing, and why time synchronization matters in distributed systems.Centralizing SaaS Audit Logs with AWS AppFabric - OCSF Standardization and Security Lake IntegrationThis article explains collecting audit logs from SaaS applications with AppFabric, standardizing them to OCSF format, and building analysis pipelines.Implementing Feature Flags with AWS AppConfig - Safe Configuration Deployment and RollbackRoll out configuration changes independently from code deployments using Linear and Exponential strategies. Ensure safety with automatic rollback triggered by CloudWatch alarms.Architecture Review - Systematically Evaluating Workloads with AWS Well-Architected ToolExplains architecture reviews of workloads using AWS Well-Architected Tool. Introduces evaluation based on the 6 pillars, building improvement plans, and using custom lenses.Audit Log Design and Operations - Complete API Activity Recording with CloudTrailLearn how to design audit logs using AWS CloudTrail, including recording API activity, long-term storage in S3, and compliance automation through integration with AWS Config.Lessons from AWS Incident Reports (COE) - How Past Major Outages Shaped Design PrinciplesAnalyze the root causes of past major incidents including the S3 outage, us-east-1 DNS failure, and Kinesis outage from AWS's published Correction of Errors (COE) and incident reports, and explain how they changed AWS's design principles.Tag Design Determines Operations - Trivia and Practical Naming Conventions for AWS Resource Tagging StrategyWe explain why AWS resource tags are not just labels but the foundation for cost allocation, access control, and automation, covering tag key naming conventions, how to use the 50-tag limit, and governance through tag policies.Why AWS Service Quotas Exist - Multi-Tenant Design That Protects Shared InfrastructureExplain how AWS service quotas (formerly service limits) are not mere restrictions but a design to protect other customers in a multi-tenant environment, covering the noisy neighbor problem, soft vs hard limits, and what happens behind quota increase requests.