Mastering Grafana Cloud's New Allowlist API
The new Allowlist API exists to simplify how you manage IP addresses for Grafana Cloud. It consolidates the previous collection of per-product lists into a single, structured API. This change addresses the complexity and confusion that often arose from managing multiple lists, allowing for a more efficient and organized approach to IP allowlisting.
The Allowlist API serves current IP addresses as structured JSON over HTTPS. It provides endpoints for global, per region, and per service access. Each entry specifies the traffic direction—ingress or egress—and includes IPv4 CIDR ranges to allow. For example, you might see an entry like this:
{ "metadata": { "schemaVersion": "v1", "region": "prod-eu-west-2" }, "services": { "metrics": { "direction": "ingress-to-grafana", "ipv4": ["198.51.100.10/32", "198.51.100.11/32"] }, "grafana": { "direction": "egress-from-grafana", "ipv4": ["203.0.113.20/32"] } } }
In production, you should know that all legacy per-product formats will remain operational and up to date until January 31, 2027. If you don't currently use IP allowlisting or connect to Grafana Cloud over private connectivity like AWS PrivateLink, you won’t need to make any changes. This allows for a smooth transition without disrupting existing setups.
Key takeaways
- →Utilize the Allowlist API for a structured approach to managing IP addresses.
- →Access IP addresses as JSON over HTTPS for global, regional, and service-specific configurations.
- →Remember that legacy formats will be supported until January 31, 2027.
- →Understand ingress and egress definitions to configure your services correctly.
- →No action is needed if you connect over private connectivity or don't use IP allowlisting.
Why it matters
This new design reduces complexity in managing IP addresses, which is crucial for maintaining secure and efficient connections to Grafana Cloud services. It streamlines operations, saving time and reducing the risk of misconfiguration.
Code examples
1{
2 "metadata": { "schemaVersion": "v1", "region": "prod-eu-west-2" },
3 "services": {
4 "metrics": {
5 "direction": "ingress-to-grafana",
6 "ipv4": ["198.51.100.10/32", "198.51.100.11/32"]
7 },
8 "grafana": {
9 "direction": "egress-from-grafana",
10 "ipv4": ["203.0.113.20/32"]
11 }
12 }
13}When NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsOpenAI & Anthropic-compatible inference API — no GPU provisioning needed. 55+ models, pay-per-token with no minimums. VPC + zero data retention by default.
Try Serverless Inference →Grafana Alert Enrichment: Elevate Your Incident Response
In a world where every second counts, Grafana's alert enrichment feature transforms alerts into actionable insights. By adding contextual information, such as AI-generated explanations and related logs, you can respond faster and more effectively.
Benchmarking AI Agents for Observability Workflows with o11y-bench
In the evolving landscape of observability, o11y-bench emerges as a critical tool for evaluating AI agents. It runs agents against a real Grafana stack, providing a structured way to assess their performance on observability tasks.
Mastering AI Observability in Grafana Cloud
AI Observability is crucial for understanding your AI systems' performance and issues. With OpenTelemetry compatibility, it seamlessly integrates into your existing setups, capturing vital metrics like latency and cost signals. Dive in to learn how to leverage this powerful tool effectively.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.