Metamapper
  • Documentation
  • Discussion
  • Blog
  • Github

›Datastores

Metadata Management

  • Welcome
  • Getting Started
  • Schema Inspection
  • SSH Tunnels
  • Custom Properties
  • Annotations
  • Search

Datastores

  • Overview
  • AWS Athena
  • AWS Glue Data Catalog
  • Azure Synapse
  • Google BigQuery
  • Hive Metastore
  • MySQL
  • Oracle
  • PostgreSQL
  • Redshift
  • Snowflake
  • Microsoft SQL Server

Workspace Management

  • Introduction
  • Access Management
  • Single Sign-On (SSO)
  • SSO Setup: Google
  • SSO Setup: Github
  • SSO Setup: SAML2

Installation (Self-Hosted)

  • Getting Started
  • Configuring Metamapper
  • Extensions
  • Asynchronous Workers
  • Email Configuration
  • File Storage
  • Security
  • Search
  • Healthchecks

AWS Glue Data Catalog

Metamapper supports AWS Glue Data Catalog as a connection source. The AWS Glue Data Catalog contains references to data that is used as sources and targets of your extract, transform, and load (ETL) jobs in AWS Glue. It can also be used as an external metastore for Apache Hive.

This guide details how to setup and troubleshoot Glue Data Catalog in Metamapper.

Prequisites

  • An Amazon Web Services (AWS) account. Sign up for an account at the AWS website.

  • Permissions to create an IAM role . Metamapper needs to be granted certain permissions to access and query Glue Data Catalog.

Create a IAM role

You need to create an IAM role to manage permissions between Metamapper and your Glue Data Catalog.

We do not support IAM users as a connection method. That being said, if you set the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_DEFAULT_REGION environment variables, your compute instance should be able to assume the provided IAM role.

Permissions

Create and attach the following inline policy to your IAM role:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "",
            "Effect": "Allow",
            "Action": [
                "glue:GetTables",
                "glue:GetDatabases"
            ],
            "Resource": "*"
        }
    ]
}

Trust relationships

If you are running Metamapper within the same AWS account on an EC2 instance, you should set the trust relationship to:

{
  "Version": "2008-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your recommendations, open a Github issue, or join the discussion on Discord.

Last updated on 9/9/2020
← AWS AthenaAzure Synapse →
  • Prequisites
  • Create a IAM role
    • Permissions
    • Trust relationships
  • Questions? Feedback?
Metamapper
Documentation
User GuideInstallation Guide
Community
DiscussionGitHub
Copyright © 2020 Scott Cruwys