Terraform AWS Athena将Glue目录用作数据库

时间:2019-03-12 19:08:03

标签: amazon-web-services terraform aws-glue terraform-provider-aws aws-glue-data-catalog

对于如何使用terraform将Athena连接到我的Glue Catalog数据库感到困惑。

我使用

resource "aws_glue_catalog_database" "catalog_database" {
    name = "${var.glue_db_name}"
}

resource "aws_glue_crawler" "datalake_crawler" {
    database_name = "${var.glue_db_name}"
    name          = "${var.crawler_name}"
    role          = "${aws_iam_role.crawler_iam_role.name}"
    description   = "${var.crawler_description}"
    table_prefix  = "${var.table_prefix}"
    schedule      = "${var.schedule}" 

    s3_target {
      path = "s3://${var.data_bucket_name[0]}"
  }
    s3_target {
      path = "s3://${var.data_bucket_name[1]}"
  }
 }

创建一个Glue DB,而搜寻器则爬行一个s3存储桶(这里只有两个),但是我不知道如何将Athena查询服务链接到Glue DB。 In the terraform documentation for Athena,似乎没有办法将Athena连接到Glue目录,而只能连接到S3存储桶。但是,显然Athena can be integrated with Glue

如何构建Athena数据库以使用我的Glue目录作为数据源而不是S3存储桶?

2 个答案:

答案 0 :(得分:1)

我们当前的基本设置是让Glue爬行一个S3存储桶并在Glue DB中创建/更新表,然后可以在Athena中查询它,如下所示:

搜寻器角色和角色策略:

  • IAM角色的accept_role_policy仅需要Glue作为主体
  • IAM角色策略允许对Glue,S3和日志进行操作
  • 胶水的动作和资源可能可以缩小到实际需要的程度(这是正在进行的工作)
  • S3操作仅限于爬虫所需的操作
resource "aws_iam_role" "glue_crawler_role" {
  name = "analytics_glue_crawler_role"

  assume_role_policy = <<EOF
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": "sts:AssumeRole",
      "Principal": {
        "Service": "glue.amazonaws.com"
      },
      "Effect": "Allow",
      "Sid": ""
    }
  ]
}
EOF
}

resource "aws_iam_role_policy" "glue_crawler_role_policy" {
  name = "analytics_glue_crawler_role_policy"
  role = "${aws_iam_role.glue_crawler_role.id}"
  policy = <<EOF
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "glue:*",
      ],
      "Resource": [
        "*"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetBucketLocation",
        "s3:ListBucket",
        "s3:GetBucketAcl",
        "s3:GetObject",
        "s3:PutObject",
        "s3:DeleteObject"
      ],
      "Resource": [
        "arn:aws:s3:::analytics-product-data"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "logs:CreateLogGroup",
        "logs:CreateLogStream",
        "logs:PutLogEvents"
      ],
      "Resource": [
        "arn:aws:logs:*:*:/aws-glue/*"
      ]
    }
  ]
}
EOF
}

S3铲斗,胶水数据库和搜寻器:

resource "aws_s3_bucket" "product_bucket" {
  bucket = "analytics-product-data"
  acl = "private"
}

resource "aws_glue_catalog_database" "analytics_db" {
  name = "inventory-analytics-db"
}

resource "aws_glue_crawler" "product_crawler" {
  database_name = "${aws_glue_catalog_database.analytics_db.name}"
  name = "analytics-product-crawler"
  role = "${aws_iam_role.glue_crawler_role.arn}"

  schedule = "cron(0 0 * * ? *)"

  configuration = "{\"Version\": 1.0, \"CrawlerOutput\": { \"Partitions\": { \"AddOrUpdateBehavior\": \"InheritFromTable\" }, \"Tables\": {\"AddOrUpdateBehavior\": \"MergeNewColumns\" } } }"

  schema_change_policy {
    delete_behavior = "DELETE_FROM_DATABASE"
  }

  s3_target {
    path = "s3://${aws_s3_bucket.product_bucket.bucket}/products"
  }
}

答案 1 :(得分:0)

我的Terraform代码中有很多错误。首先:

  1. aws_athena_database code中的S3存储桶参数是指查询输出的存储桶不是应该从中构建表的数据。
  2. 我已经将aws_glue_crawler设置为写入Glue数据库而不是Athena数据库。确实,正如马丁上面所建议的那样,一旦正确设置,雅典娜就可以在Glue数据库中查看表格。
  3. 我的搜寻器没有附加正确的策略。最初,附加到搜寻器角色的唯一策略是

    resource "aws_iam_role_policy_attachment" "crawler_attach" {
        policy_arn = "arn:aws:iam::aws:policy/service-role/AWSGlueServiceRole"
        role = "${aws_iam_role.crawler_iam_role.name}"
    } 
    

    设置第二个明确允许所有S3访问我要爬网的存储桶的策略并将该策略附加到同一爬网程序角色后,爬网程序成功运行并更新了表。

    < / li>

第二项政策

resource "aws_iam_policy" "crawler_bucket_policy" {
    name = "crawler_bucket_policy"
    path = "/"
    description = "Gives crawler access to buckets"
    policy = <<EOF
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Stmt1553807998309",
      "Action": "*",
      "Effect": "Allow",
      "Resource": "*"
    },
    {
      "Sid": "Stmt1553808056033",
      "Action": "s3:*",
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::bucket0"
    },
    {
      "Sid": "Stmt1553808078743",
      "Action": "s3:*",
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::bucket1"
    },
    {
      "Sid": "Stmt1553808099644",
      "Action": "s3:*",
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::bucket2"
    },
    {
      "Sid": "Stmt1553808114975",
      "Action": "s3:*",
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::bucket3"
    },
    {
      "Sid": "Stmt1553808128211",
      "Action": "s3:*",
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::bucket4"
    }
  ]
}
EOF
}

我相信我可以摆脱在此策略中对存储桶名称进行硬编码的麻烦,但我还不知道该怎么做。