## Crawl on-premises Looker

URL: https://docs.atlan.com/apps/connectors/business-intelligence/looker/how-tos/crawl-on-premises-looker

> Extract metadata from on-premises Looker to catalog dashboards, looks, explores, and data sources. Discover and govern your BI assets after configuring extractor tool.

:::danger **Deprecated**
This job execution mode was deprecated on June 30, 2026 and is no longer supported or maintained, including bug fixes. Existing workflows may break/be disabled without warning. For all implementations, switch to [Self-deployed runtime](https://docs.atlan.com/llms/platform/self-deployed-runtime/llms.txt).
:::

Extract metadata from your [on-premises Looker](https://docs.atlan.com/llms/connectors/looker/set-up-on-premises-looker-access/llms.txt) instances into Atlan to catalog dashboards, looks, explores, and data sources. After setting up the looker-extractor tool, you can extract metadata using the following steps.

## Run looker-extractor

### Crawl all connections

To crawl all Looker connections using the looker-extractor tool:

1. Log into the server with Docker Compose installed.
2. Change to the directory containing the compose file.
3. Run Docker Compose: `sudo docker-compose up`

### Crawl specific connection

To crawl a specific Looker connection using the looker-extractor tool:

1. Log into the server with Docker Compose installed.
2. Change to the directory containing the compose file.
3. Run Docker Compose: `sudo docker-compose up `

(Replace `` with the name of the connection from the `services` section of the compose file.)

## (Optional) Review generated files

The looker-extractor tool generates many JSON files for each `service`. For example:

- `projects.json`
- `dashboards.json`
- `dashboard_tiles.json`
- `looks.json`
- and many others

You can inspect the metadata and make sure it's acceptable to provide the metadata to Atlan.

## Upload generated files to S3

To provide Atlan access to the extracted metadata, you need to upload the metadata to an S3 bucket.

:::info **Did you know?** 
 It's recommended to upload to the same S3 bucket as Atlan uses to avoid access issues. Reach out to your Data Success Manager to get the details of your Atlan bucket. To create your own bucket, refer to the [Create your own S3 bucket](https://docs.atlan.com/llms/connectors/dbt/set-up-dbt-core/llms.txt) section of the dbt documentation. (The steps are exactly the same.)

:::

To upload the metadata to S3:

1. Make sure all files for a particular database have the same prefix. For example, `metadata/looker/projects.json`, `metadata/looker/dashboards.json`, etc.
2. [Upload the files to the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/upload-objects.html) using your preferred method.

For example, to upload all files using the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html):

```
aws s3 cp output/looker-example s3://my-bucket/metadata/looker-example --recursive
```

## Crawl metadata in Atlan

Once you have extracted metadata on-premises and uploaded the results to S3, you can crawl the metadata into Atlan:

- [How to crawl Looker](https://docs.atlan.com/llms/connectors/looker/crawl-looker/llms.txt)

Be sure you select **Offline** for the _Extraction method_.

---