---
title: "Grafana Cloud Link app plugin for Grafana"
description: "Take cloud with you to any grafana instance. Grafana Cloud Link app plugin for Grafana by Grafana Labs. Available in Grafana Cloud and self-managed Grafana."
---

> This is the Markdown version of https://grafana.com/grafana/plugins/grafana-cloud-link-app/

# Grafana Cloud Link

- Developer: Grafana Labs
- Version: 1.0.0
- [Installation](https://grafana.com/grafana/plugins/grafana-cloud-link-app/installation.md)
- [Change log](https://grafana.com/grafana/plugins/grafana-cloud-link-app/changelog.md)

# Cloud lunchbox

Cloud lunchbox is a Grafana plugin that reduces the friction for existing Grafana users to begin to using Grafana Cloud.

## Overview

Cloud lunchbox was developed during two hackathons.

### First hackathon

_Bringing cloud to an on-prem Grafana instance_

During this hackathon, we implemented functionality to allow a user to:

- Sign up for cloud
- Spin up a stack: enabling them to have hosted logs, metrics, and traces, while still using their customized Grafana instance
- Get datasources automatically provisioned that connect to the hosted logs, metrics, and traces
- Get cloud plugins installed

For more info & a demo see the [2021 Hackathon Presentation](https://drive.google.com/file/d/1Q-Y2JA2SFJV3atoMnF3gKGEd7_gmodn8/view?usp=sharing).

### Second hackathon

_Bringing an on-prem Grafana instance to Hosted Grafana_

During this hackathon, we implemented functionality to allow a user to:

- Export their dashboards, datasources, and plugins from their on-prem Grafana instance to Hosted Grafana
- Invite their existing users to join them on their cloud org

For more info & a demo see the [2022 Hackathon Presentation](https://drive.google.com/file/d/1kb8cBK15HpMLs0qJ3KWx1wq8krm96lGp/view?usp=sharing).

## How does this work?

### Importing to on-prem

TODO!

### Exporting to Hosted Grafana

![Ejector Seat](https://user-images.githubusercontent.com/14365078/163624349-d1861db7-daca-4975-9e7a-32d898780c9e.png)

## Other documentation

[Delivery Plan](https://docs.google.com/document/d/1EbgAbvRt8vDDLkf39wapil8FZOFvUbN3T3g59nvN3GI)

[Design Doc](https://docs.google.com/document/d/1fSnCQTmW92SJr-ptv7fRpL4_IyD_jU6exazG4KsvkKA)

## Development

### Run locally

1. Install dependencies

   ```bash
   yarn install
   ```

2. Build plugin in development mode or run in watch mode

   ```bash
   yarn watch
   ```

   And also build the backend:

   ```bash
   mage
   ```

### CLI tools

We use `make` for handy cli tools. Run `make` on it's own for list of commands.

3. Run Grafana In order to test pushing and pulling we have a variety of provisioned datasources, dashboards, and plugins. Datasources are run via docker in a docker-compose.yml file.

   ```bash
   make run
   ```

When you run `make run` this starts a grafana instance as well as containers for

postgresql loki redis tempo prometheus graphite

along with agents to generate data.

To run JUST grafana by itself run

```bash
make grafana
```

### grafana version

If you'd like to run a specific version of grafana add the version variable to your make command

```bash
VERSION=9.1 make run
```

4. Connecting to grafana container If you need to check configuration in the currently running grafana container you can access the shell via

   ```bash
   make connect
   ```

### Cleanup

5. Clean up resources

   ```bash
   make clean
   ```

### Connecting to local grafana-com

There are some situations where developing against a locally running grafana-com makes sense, especially when working with new account creation. In order to get that going, follow the directions in [the grafana-com repo](https://github.com/grafana/grafana-com#development). A couple specific things in the grafana-com setup:

- Add `OAUTH_DEVICE_CODE_ALLOWED_ORG_IDS=[1]` to your `.env` file
- Make sure and run the job-queue
- In the `settings.go` file of this repo, make the GrafanaComUrl equal to `http://host.docker.internal:4000/` (or `http://localhost:4000` if not on a mac)
- Log in to grafana.com and create a new oauth client in the raintank org
- Paste the created client ID into `settings.go`.

The oauth flow and account creation should work fine, but the rest of the import flow probably won't.
