Overview
Grafana Enterprise is a commercial edition of Grafana that includes premium features not found in the open source version. Grafana Enterprise enables organizations to complete their observability picture, reaching across logs, metrics, traces, and other applications with access to enterprise data sources like AppDynamics and Splunk, enhanced LDAP, SAML, access control, reporting, usage insights, and much more.
Please note: this listing is for customers who would like to self-manage Grafana Enterprise on AWS. It does not apply to Amazon Managed Grafana or Grafana Cloud.
For more information on Grafana Enterprise, see https://grafana.com/products/enterprise/grafana/ .
To learn more or to discuss volume pricing, please reach out to us at amazongrafana@grafana.com .
Highlights
- Visualize and alert on observability and operational data from enterprise data sources including AppDynamics, Splunk, New Relic, Datadog, SignalFx, Oracle, ServiceNow, Jira, Gitlab, Dynatrace, Snowflake, MongoDB, Wavefront, and more
- Increase adoption and keep Grafana secure with enhanced LDAP, SAML, access control, reporting, security, usage insights, and more
- Access Prometheus, Graphite, and Grafana experts as well as hands-on Grafana Labs support teams
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Base/Support + 60 Users | Includes a license, support, and up to 60 active users | $40,000.00 |
Additional Active Users | Incremental cost per additional active user | $300.00 |
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Helm Chart
- Amazon EKS
- Amazon ECS
- Amazon ECS Anywhere
- Amazon EKS Anywhere
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Release notes are available on the website https://grafana.com/docs/grafana/latest/release-notes/release-notes-11-6-0/
Additional details
Usage instructions
You can apply your Grafana Enterprise license to a new or existing Grafana Enterprise deployment by updating a configuration setting or environment variable. Your Grafana instance must be deployed on AWS, or have network access to AWS. For more information, see https://grafana.com/docs/grafana/latest/enterprise/license/
Resources
Vendor resources
Support
Vendor support
Grafana Enterprise support includes a critical response SLA, unlimited support over private Slack channel, email and phone, and training, workshops, and professional services from experts at Grafana Labs.
Contact amazongrafana@grafana.com to inquire about Grafana Enterprise.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Centralized monitoring has reduced incidents and now improves alerting and troubleshooting speed
What is our primary use case?
My main use case for Grafana is to create and design dashboards based on the metrics provided by different exporters via Prometheus.
We have different exporters, and we are creating different dashboards based on them. We have a set of dashboards related to Kafka, virtual machines, and instances. Inside Kafka, we have a broker dashboard, consumer dashboard, partition dashboard, and other ingestion and consumption rate dashboards. Apart from that, we have a dashboard for consumer lag and consumption by partition.
We are collecting metrics from Prometheus and creating dashboards inside Grafana . Inside Grafana, we have different data sources including Thanos and Prometheus. We are also using Grafana for alert setup. We have set up alerts based on the exceptions we are collecting from Loki, and if any such exception occurs, it will create an incident alert over Squadcast .
What is most valuable?
Grafana offers many features including the ability to create dashboards, add variables, and set up alerts, which also covers notifications via integration with incident management tools or by configuring your email ID to get the notifications.
You can directly configure alerts in Grafana by either creating a dashboard or using the explore icon in Grafana, where you can select Loki and set alerts based on your exceptions.
There are many features including dashboard creation being much easier. You can configure multiple data sources such as Prometheus and Thanos. Apart from that, you can directly link AWS CloudWatch with your Grafana and other tools. For alerting, you can create alerts based on thresholds and exceptions, and in Grafana, there are many plugins you can configure to create data source dashboards. Additionally, there is also a restriction in Grafana that allows you to provide viewer, editor, or admin access based on roles.
We have had very positive outcomes from Grafana because you can directly visualize the metrics based on past and current inputs and take timely actions based on the responses you are getting from the visualization dashboards. Apart from that, the alerts notify you through your incident management tool.
You can check those metrics in the incident management tool by filtering the alert source as Grafana, and it helps in reducing production incidents because you can acknowledge and visualize the metrics from Grafana on time.
What needs improvement?
Currently, I do not think that any improvement is required, but there are multiple use cases.
For how long have I used the solution?
I have been using Grafana for the last four years.
What do I think about the stability of the solution?
Grafana is stable.
What do I think about the scalability of the solution?
Grafana has excellent scalability.
How are customer service and support?
The customer support for Grafana is excellent.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
This is the only solution we are currently using.
Before choosing Grafana, we evaluated other options including DataDog, but it was quite costlier, so we switched to Grafana.
How was the initial setup?
I have seen a return on investment as we actually need fewer employees, and you can take timely actions on the alerts. Apart from that, it reduces MTTR because you receive notifications through the incident management tool, allowing for timely action and better troubleshooting by visualizing metrics and logs inside Grafana. You can optimize these processes by visualizing issues earlier based on the metrics from Grafana.
I have seen a return on investment with fewer employees needed, and you can take timely actions based on alerts. Apart from this, it helps reduce MTTR because you receive notifications through the incident management tool, enabling timely responses and better troubleshooting by visualizing metrics and logs inside Grafana, thus allowing you to tackle issues earlier based on Grafana metrics.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that it is very reasonable and has excellent community support.
What other advice do I have?
You are able to detect issues faster because you can configure alerts based on thresholds in your Grafana and get notifications from your tool like Squadcast , which will reduce MTTR. Apart from that, system visibility is there; you can visualize CPU metrics, memory, disk usage, API latencies, and other ports inside the Grafana dashboard. Based on these metrics, you can troubleshoot your issues very easily.
If you want a scalable solution, better visualization, optimization, centralized monitoring, and improved troubleshooting, then you can choose Grafana without any doubts in your mind. I would rate this product a ten out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Powerful, Flexible Observability with Grafana Labs
For beginners, the initial dashboard setup and alert configuration can also feel a bit complex. Once you start integrating multiple data sources across distributed systems, it can take a while to fully understand how to structure queries, manage permissions, and set up alerting logic correctly.
This has noticeably improved our troubleshooting speed, provides clearer visibility across microservices, and helps our team make faster, data-driven decisions with greater confidence.
Flexible, Clear Dashboards with Powerful Integrations and Alerting
I also really appreciate its integration capabilities. It connects smoothly with Prometheus, Kubernetes, and other data sources without much complexity. Being able to pull metrics from different systems and view everything in one place gives us better visibility into overall system performance.
Alerting is another strong point. We can set up alerts based on thresholds, which helps us respond quickly when something goes wrong. Overall, Grafana makes monitoring more organized, visually clear, and easier to manage in day-to-day operations.
Writing queries—particularly with Prometheus (PromQL)—can also be fairly complex. If a query isn’t written correctly, the dashboard may not show accurate data, and tracking down what went wrong can take extra time and effort.
Another minor concern is that when there are too many dashboards and panels, managing everything can become difficult without good organization. That said, once I get used to the structure and establish a system, it becomes much more manageable.
In our experience, it has made it easier to track application performance, CPU and memory usage, API response times, and overall system health in one place. Rather than jumping between multiple tools, we can view everything on a single dashboard, which saves a lot of time.
It also supports early issue detection. When a metric crosses a threshold, we receive alerts and can respond quickly before it turns into a bigger problem. Overall, this improves system stability and helps reduce downtime.