← Explore all skills

PRIVATE CONNECTIVITY / Grafana Labs

Grafana Cloud private connectivity

Pins Grafana's private connectivity skill, which limits AWS PrivateLink to one region unless peering exists and rejects a public DNS answer.

“Set up private network connectivity to Grafana Cloud …”

01 / THE REASONING

Why this made the selection.

  • No selected skills record uses this source path.
  • The file limits AWS PrivateLink to the same region unless VPC peering already exists, and it treats a public DNS answer as the public path.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • skills/grafana-cloud/private-connectivity/SKILL.md
  • README.md
  • LICENSE

Our findings

  • AWS PrivateLink is same-region only. The file says cross-region use requires VPC peering first.
  • After the endpoint exists, private DNS must resolve to a private address. A public answer means Alloy keeps using the public path.
  • Azure endpoint creation is described as hanging at Pending unless subscription IDs are pre-registered with Grafana Support.
  • The Grafana Cloud stack must be hosted on the same cloud provider, and each signal type needs its own private endpoint.
  • The Alloy example reads the API key from GRAFANA_CLOUD_API_KEY instead of placing a key literal in the snippet.
  • The Azure path requires subscription registration with Grafana Support before endpoint creation, and the source identifies missing registration as a pending-state cause.

Not established by this review

  • The resource was not executed and its tools were not called.
  • No VPC endpoint was created and no DNS lookup was run.
  • The AWS and Azure or GCP reference files were not opened.
  • No compliance regime was assessed and no traffic path was captured.
  • Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

claude plugin install grafana-cloud@grafana-skills

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. The README Claude Code section shows claude plugin marketplace add grafana/skills and then claude plugin install grafana-cloud@grafana-skills.
  2. That command installs the grafana-cloud plugin group. This file is skills/grafana-cloud/private-connectivity/SKILL.md.
  3. npx skills add grafana/skills is also in the README and can install more than this file. The only --skill example names frontend-session-rca, not this skill.
  4. This review did not run either install.

Before you start

  • Claude Code if the recorded plugin command is used
  • A skills host if npx skills add grafana/skills is used instead
  • A same-cloud Grafana Cloud stack and cloud credentials only if an endpoint is created, which this review did not do

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-cloud/private-connectivity/SKILL.md

    Supports: same-region PrivateLink limit and public-DNS failure

  2. Repository README ↗Checked

    https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/README.md

    Supports: grafana-cloud plugin install line and Apache-2.0 statement

  3. Repository LICENSE ↗Checked

    https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/LICENSE

    Supports: Apache License Version 2.0 and Copyright 2026 Grafana Labs

  4. https://raw.githubusercontent.com/grafana/skills/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-cloud/private-connectivity/SKILL.md

    Supports: review.findings, bestFor, upstreamDescription

Evidence & Ask